KyttoMCP 1.0.7

The first release built from the public source. MCP Doctor can now pin a
package that a server starts without an exact version, clients with a known
tool limit show how close you are to it, and Kytto no longer sends any
telemetry.

Added

• The source code is public. Both apps — macos/ (Swift) and windows/
  (.NET) — are now open source under the MIT License, in this repository. You
  can read exactly what Kytto does with your config files, check every network
  request it makes, and build it yourself instead of trusting an unsigned binary.
• MCP Doctor flags unpinned package versions. A server launched as
  npx some-package, some-package@latest, uvx some-package or similar starts
  whatever release is newest each time a client launches it, with your API keys
  in its environment. Doctor now warns about these, and after you check the
  latest release it offers to pin that exact version. The preview shows the
  argument before and after in every client, and the change goes through the
  usual backup and atomic write. Kytto contacts the package registry only when
  you press Check latest release.
• Tool-count limit per client. VS Code refuses a chat request with more than
  128 tools. The client screen and the matrix header now show how many tools
  the servers switched on there offer against that limit, warn when you are
  near or over it, and suggest switching servers off, using a smaller profile
  or hiding tools through the Gateway. Servers not yet health-checked are
  listed, and the count is shown as a minimum.

Fixed

• "Check latest" failed for packages with a long release history. Kytto
  downloaded an npm package's full metadata, which for many packages exceeds
  the size limit Kytto enforces, and reported "The package registry response
  was unexpectedly large." It now asks npm for the latest release only.

Removed

• Anonymous diagnostics. The optional Share anonymous diagnostics setting,
  off by default since it was introduced, is gone from both apps. Kytto now sends
  no telemetry of any kind; the only request it makes on its own is the update
  check. If you run 1.0.6.3 or earlier with the setting on, the website has
  stopped storing what it sends, so nothing is kept either way.

Compatibility

doctor.applyFix accepts a new action, pinPackageVersion, and now reports
held copies of switched-off servers it updated (parkedUpdated,
parkedFailures). Clients gain a toolBudget field. Nothing was removed. The
backup, permission and restore protections from 1.0.6.1 are retained.

Distribution notes

The macOS build is universal and runs on Apple Silicon and Intel Macs. It is
ad-hoc signed rather than notarized, and the Windows installer is not
Authenticode-signed. Verify the SHA-256 checksum before bypassing Gatekeeper or
SmartScreen.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.7.dmg	4.6 MB	a6df1c891665c1371499fc5c52b1de1431ae2e1c87c86e3362411492f69d20cb
Windows x64	Kytto-Setup-win-x64-1.0.7.exe	78.4 MB	542ba475c207be303206df47d1087f93bcdee6a6f7964849c607ed77ba73cba3

Install

• macOS: Open the DMG and drag KyttoMCP into Applications. Control-click
  the app and choose Open on first launch if Gatekeeper warns you.
• Windows: Run the setup file. At the SmartScreen prompt choose
  More info and then Run anyway.

KyttoMCP 1.0.6.3

A fix release. Three panels could not be scrolled, so anything below the bottom edge of the window was unreachable; Settings also gained a way in that does not go through the menu bar.

Fixed

• Scrolling in MCP Doctor, Live Activity and Profiles. These three panels clipped their content instead of scrolling it, and no gesture or key reached what was cut off. They now scroll like the MCP Library and Skills panels always did.

Added

• Settings in the sidebar footer. Settings was reachable only from the app menu and ⌘,. It is now a row in the sidebar footer, below the diagnostics count. The row opens the Settings window and never takes selection in the sidebar.

Compatibility

One IPC command was added, settings.open. Nothing was removed or changed. The backup, permission and restore protections from 1.0.6.1 are retained.

Distribution notes

The macOS build is universal and runs on Apple Silicon and Intel Macs. It is ad-hoc signed rather than notarized, and the Windows installer is not Authenticode-signed. Verify the SHA-256 checksum before bypassing Gatekeeper or SmartScreen.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.6.3.dmg	4.3 MB	825c194ae505160d841eaa50cce993ebacf41dbee4b334ba554a790c9a16744e
Windows x64	Kytto-Setup-win-x64-1.0.6.3.exe	78.5 MB	d1efbf351fa00cf010588a790f9650542137177e44fda2ad9750b6d479f71bb9

Install

• macOS: Open the DMG and drag KyttoMCP into Applications. Control-click the app and choose Open on first launch if Gatekeeper warns you.
• Windows: Run the setup file. At the SmartScreen prompt choose More info and then Run anyway.

Full changelog: https://github.com/heyitsjakub/KyttoMCP/blob/main/CHANGELOG.md

KyttoMCP 1.0.6.2

KyttoMCP 1.0.6.2 — 2026-09-19

A visual and onboarding release across the macOS and Windows builds. It makes
the first-run hand-off easier to understand before any configuration is changed,
and gives the matrix shell a clearer sense of movement as you navigate.

Changed

• Modernized first-run onboarding. Kytto now presents the detected local
  workspace with client icons, server/client metrics and read-only custom-source
  counts before you enter the matrix.
• Clearer safety boundary. Onboarding explicitly says that the screen only
  reads configuration and that edits create a backup first; the discovery list
  shows each client state and path without implying that anything was written.
• Direction-aware panel navigation. Moving between the matrix, client details
  and utility panels now animates in the direction of the selected panel.
• More spacious responsive UI. The updated shell, discovery list and matrix
  styling give the interface more room while preserving the existing responsive
  layout.

Compatibility

No IPC command, event, request field or response field was added or removed. The
release retains the backup, permission and restore protections from 1.0.6.1.

Distribution notes

The macOS build is universal and runs on Apple Silicon and Intel Macs. It is
ad-hoc signed rather than notarized, and the Windows installer is not
Authenticode-signed. Verify the SHA-256 checksum before bypassing Gatekeeper or
SmartScreen.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.6.2.dmg	4.5 MB	e0f398c590beaba2a9de9caf4a94304c258eee119c9708ce9ebc4554fa3ebdfd
Windows x64	Kytto-Setup-win-x64-1.0.6.2.exe	78.5 MB	b64b972d92db2bb59e6ae502383159bc4874b50973853a89fc1aae2e2806e1e2

Install

• macOS: Open the DMG and drag KyttoMCP into Applications. Control-click
  the app and choose Open on first launch if Gatekeeper warns you.
• Windows: Run the setup file. At the SmartScreen prompt choose
  More info and then Run anyway.

---

KyttoMCP 1.0.6.1

KyttoMCP 1.0.6.1 hardens configuration backups, following up #11.

Backups and parked server definitions hold the same API keys as the configuration files they were copied from, but until now they were created readable by other local accounts on the same computer. This release locks them to your own user and limits restoring a backup to the files Kytto actually manages for that client.

Both findings are low severity. Reading the backups took a second account on the same computer, and redirecting a restore took write access to your own backups folder already.

If you are on 1.0.5.3 or later for macOS, the in-app updater can install this release.

What was fixed

Backups are readable only by you. Backup folders are now created owner-only, and every backup copy and the sidecar that records where it came from are readable and writable by your account alone. Kytto's own data folder is tightened the same way.

Parked server definitions are owner-only. When a client that has no "disabled" flag switches a server off, Kytto keeps its definition — env block included — in parked-servers.json. That file is now owner-only too.

Existing backups are fixed on first launch. Backups made by earlier versions are tightened once when the app starts. Nothing is created or deleted, symbolic links are not followed, and later launches change nothing.

No readable moment during a write. The atomic writer now creates its temporary file owner-only from the start and applies the final permissions afterwards. Previously the configuration bytes were briefly readable under the temporary name.

Restore writes only to files Kytto manages. Revert and Undo now write a backup back only to that client's own files: its server configuration (at the current path override or the default location), the Claude Code deny list, and Claude Desktop's extension settings. The destination always comes from Kytto's client registry, never from the path recorded next to the backup, so an edited sidecar can no longer aim a restore at another file. Any other target is refused with a clear message and nothing is written.

Behaviour changes

• A backup taken from a configuration path you have since changed in Settings can no longer be restored. The message explains why, and the backup stays in the backups folder.
• A configuration file marked read-only (0444) can now be written by Kytto and keeps its permissions. Previously the write failed as a side effect of the old implementation.

Compatibility

No IPC command, event, request field or response field was added or removed. backups.restore can now fail with the existing error code backup, and when it does it writes nothing.

The Windows build carries the same hardening, ported natively. Windows has no Unix permission bits, so Kytto's data folder, backups and parked definitions get a private access list instead: your account, SYSTEM and Administrators, and no one else.

Install

macOS — open the DMG, drag KyttoMCP into Applications, then Control-click the app and choose Open. Or, from 1.0.5.3, let the in-app updater do it.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.6.1.dmg	4.5 MB	774c6af6b8eab9fd068ea647ff5e8ab33a5b44f06da92782351f517ba3286e99
Windows x64	Kytto-Setup-win-x64-1.0.6.1.exe	78.5 MB	077f74e7a2a668af1d8af6945177bb9759026fd6dd4fb8b38ae84a21aff86568

The macOS build is universal and runs on Apple Silicon and Intel Macs alike.

This beta is not yet notarized or Authenticode-signed. Only open builds downloaded from this release or kytto.jakubhecht.sk, and verify the checksum before opening them.

KyttoMCP 1.0.6

KyttoMCP 1.0.6 is a reliability release. There is no new feature to look at — every fix here is about the app telling you the truth about what it just did, and about undoing a change it cannot finish instead of leaving half of it behind.

If you are on 1.0.5.3 for macOS, this is the first release the in-app updater can install for you. Anything older still has to be replaced by hand.

What was fixed

Creating a client's first MCP file was reported as "no change". When a client had no configuration file yet, the first write was judged by whether there had been anything to back up — and a file that does not exist cannot be backed up, so Kytto concluded it had written nothing. Add, Edit and Remove now list that client as changed, and the restart notice appears only after a write that really happened, so clicking the same action twice no longer invents a second restart. Undo on that first write still removes the server from the client, which is the only correct way back when there is no earlier file to restore.

Enabling a server in Claude Code could change one file and not the other. Claude Code keeps the server definition in .claude.json and its deny list in .claude/settings.json, and the toggle wrote them one after another. If the second write failed, the first stayed. Both writes are now a single operation: on failure the first file is restored byte for byte, or removed if Kytto had just created it. The rollback re-checks the file's digest immediately beforehand, so it can never overwrite a newer change made outside Kytto.

The macOS updater announced success before it knew. Installing an update asks macOS to launch the new bundle, and the installer treated the request being sent as the install being done — deleting the old app and the rollback copy while the new one might still fail to start. It now waits for macOS to confirm the new bundle is actually running, and a failed relaunch goes down the existing rollback path and brings the previous version back.

A damaged profiles.json was treated as an empty profile list, and then overwritten. A missing file still means first use and is created normally, but a file that exists and cannot be read or parsed is no longer read as "no profiles". Create, Update, Delete and rename maintenance now refuse with a visible error and leave the original bytes untouched, and all of them go through one transactional read-modify-write path so two profile operations cannot race.

Launch at login could show a setting the system disagreed with. The macOS login item is now registered or unregistered before the preference is saved. If the system refuses, the settings file is left exactly as it was; if saving the settings then fails, Kytto puts the login item back — and reports both problems if it cannot.

A successful change could be reported as a failure. After a write, the app reloads the Backups, Profiles and Secrets lists. One of those reloads failing used to surface as though the change itself had failed, inviting you to repeat a write that had already succeeded. The reloads are now best-effort: you get a warning that the list could not be refreshed, together with an explicit confirmation that the change went through. The Add server form no longer reappears empty and typeless after such a failure.

Errors that vanished instead of being shown. The Secrets and Activity panels, and the Adopt, Forget, Restrict permissions, restart acknowledge/dismiss and finish-onboarding actions, now display the error they got back rather than dropping it as an unhandled rejection.

Compatibility

No IPC command, event, payload field or response field was added, removed or renamed. updates.install is unchanged on the wire — only the native implementation behind it now waits for the real relaunch result.

The Windows build carries the same fixes, ported natively. The relaunch fix is macOS-only: the Windows updater hands the download to your browser rather than installing it in-process, so it has no relaunch to get wrong.

Install

macOS — open the DMG, drag KyttoMCP into Applications, then Control-click the app and choose Open. Or, from 1.0.5.3, let the in-app updater do it.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.6.dmg	4.5 MB	d0332dd74e76932a55f9408a263748993275a0580081daa5cddafb9ee79e1f5e
Windows x64	Kytto-Setup-win-x64-1.0.6.exe	78.5 MB	1d6a056c863910a061bc5514f66e3b8813cf21454205fe7099740ec7d2069ecc

The macOS build is universal and runs on Apple Silicon and Intel Macs alike.

This beta is not yet notarized or Authenticode-signed. Only open builds downloaded from this release or kytto.jakubhecht.sk, and verify the checksum before opening them.

KyttoMCP 1.0.5.3

KyttoMCP 1.0.5.3 repairs the in-app updater on macOS.

There is nothing new to see in this version. What it fixes is the update mechanism itself, so the effect only shows up the next time an update is offered. Install it now and the version after this one will arrive without a manual download.

What was wrong

Clicking Download and verify always ended in "The update server did not return a valid response" — on every version that has shipped the updater, for everyone.

The download is routed through kytto.jakubhecht.sk/download.php, which deliberately redirects to the GitHub release asset. The code then checked the URL at the end of that redirect chain against Kytto's own domain — a condition a GitHub asset URL can never satisfy. The check was sound in intent and applied to the wrong URL.

Each redirect hop is now validated as it happens, against an allow-list of this site, GitHub, and GitHub's release-asset host; the download stops the moment a hop leaves them. The SHA-256 from the verified manifest is still checked against the bytes as they arrive, exactly as before — that, not the hostname, is what guarantees you got the file the checksum describes.

Nobody hit this earlier because 1.0.5, the release that introduced the full download-and-install flow, did not launch at all.

Install

Because the broken updater lives inside the app, this release has to be installed by hand, like every one before it. That is the last time: from 1.0.5.3 onward the updater can fetch its own updates.

macOS — open the DMG, drag KyttoMCP into Applications, then Control-click the app and choose Open.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

The Windows app is unaffected by this defect: its updater opens the download in your browser instead of fetching it in code, so there is no redirect chain for it to get wrong. It is rebuilt here only to keep both platforms on one version number.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.5.3.dmg	4.4 MB	106cb906edfdc7ff1fd3c5b57eebc35b45c1291a0e87b0a1c920ae6e3ca87a99
Windows x64	Kytto-Setup-win-x64-1.0.5.3.exe	78.5 MB	249d40273329111291c91193394aaa7011fb2e644451447df8a55ce4d5b90229

The macOS build is universal and runs on Apple Silicon and Intel Macs alike.

This beta is not yet notarized or Authenticode-signed. Only open builds downloaded from this release or kytto.jakubhecht.sk, and verify the checksum before opening them.

KyttoMCP 1.0.5.2

KyttoMCP 1.0.5.2 is a cross-platform beta update. Every change in it came from one tester's notes on 1.0.5.1.

The one that matters

A remote server waiting for you to sign in is no longer reported as broken. A server that opens a browser and waits for OAuth consent used to hit Kytto's timeout and be recorded as failed — which meant every OAuth-backed remote server showed red in the matrix, and the matrix's whole job is to reflect reality.

Those servers now show in blue as waiting for authorization, carry the sign-in URL the server itself printed, and offer an Open sign-in page action. The state is read from the server's own output, never inferred from a URL that merely looks like OAuth, and provenance treats it as unchecked rather than unhealthy.

Also new

• The sidebar can be resized — drag its edge, or focus the handle and use the arrow keys. The width is remembered.
• Claude Code project rows identify themselves by the part of the path that differs — Claude Code · …/kytto instead of several identical truncated paths. The leaf grows leftwards only when two projects would otherwise read the same; the full path stays in the tooltip.

Fixed

• Skills whose front matter uses a YAML block scalar (description: >-, and the >, |, |- forms) showed the marker instead of the description. The parser now handles block scalars, plain continuation lines and nested mappings, and no longer gives up on a leading blank line or byte-order mark.
• Skill cards printed their scope twice: Shared agent · global · Shared agents · global.
• A long configuration path in a server's Clients list could render one character per line down the side of the panel.
• Health failures now store the reason rather than the finished sentence, so wording fixes reach results recorded earlier. Records written before this release keep the text they were saved with.

Install

macOS — open the DMG, drag KyttoMCP into Applications, then Control-click the app and choose Open.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.5.2.dmg	4.4 MB	d544479a4523bb988c5377fe5cd6ea8ef7f5e2c5c573e9321dbcfde6d9d07bd5
Windows x64	Kytto-Setup-win-x64-1.0.5.2.exe	78.5 MB	dbcdf3270e3acdc12fc1465f325007f70919cbb0bd12411e6296da3b2fa6b479

The macOS build is universal and runs on Apple Silicon and Intel Macs alike.

This beta is not yet notarized or Authenticode-signed. Only open builds downloaded from this release or kytto.jakubhecht.sk, and verify the checksum before opening them.

KyttoMCP 1.0.5.1

KyttoMCP 1.0.5.1 is an emergency fix. 1.0.5 does not launch on macOS and has been withdrawn. If you are on 1.0.5, install this build over it. There are no functional changes: this is 1.0.5 with a corrected signature.

What was wrong

The macOS app crashed the moment it was opened, with:

Library not loaded: @rpath/KyttoCore.framework/Versions/A/KyttoCore
... not valid for use in process: mapping process and mapped file
(non-platform) have different Team IDs

The release build enabled the hardened runtime. That enforces library validation, which requires the app and the framework bundled inside it to share a Team ID — and an ad-hoc signature has no Team ID at all, so the check could never pass. macOS refused to load the framework and the process died before a single line of app code ran.

The hardened runtime is now off on the ad-hoc build path, where it can only break things, and the release script launches the built app and confirms it is still running before it will produce a disk image. That check is what was missing.

The Windows installer is unaffected. It is republished here unchanged, with the same checksum it had in 1.0.5.

Everything from 1.0.5

All of it is here — a local MCP library, strict JSON import, server provenance, the read-only skills inventory, Claude Code project and workspace discovery, and the in-app updater. See the 1.0.5 notes for the full list.

Install

macOS — open the DMG, drag KyttoMCP into Applications, then Control-click the app and choose Open. If a broken 1.0.5 is already in Applications, replace it; the in-app updater cannot rescue you, because it lives inside the app that will not start.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

Downloads

Platform	File	Size	SHA-256
macOS (universal)	KyttoMCP-1.0.5.1.dmg	4.3 MB	7bc266509754a9974b5efdaa1566495aa643cae80d4f396ef34aea175dcf2603
Windows x64	Kytto-Setup-win-x64-1.0.5.exe	78.4 MB	851be7f910e6d40d541d9a17e35df099f75059cfad130100602fe6163c36eae9

The macOS build is universal and runs on Apple Silicon and Intel Macs alike.

This beta is not yet notarized or Authenticode-signed. Only open builds downloaded from this release or kytto.jakubhecht.sk, and verify the checksum before opening them.

KyttoMCP 1.0.5

Caution

Withdrawn. The macOS build in this release does not launch.

KyttoMCP.app crashes immediately on startup with Library not loaded: @rpath/KyttoCore.framework and (non-platform) have different Team IDs. The build enabled the hardened runtime, whose library validation requires the app and its embedded framework to share a Team ID, which an ad-hoc signature does not have. Do not install the macOS disk image from this release.

Install 1.0.5.1 instead. It has every feature listed below and nothing else changed. The Windows installer was never affected.

The macOS rows in the table below are also wrong on their own terms: they describe an earlier, Apple Silicon-only image with a different checksum. Disregard them entirely.

KyttoMCP 1.0.5 is a cross-platform beta update for macOS and Windows.

What's new

• Pending restarts now reflect the actual difference between the applied baseline and the current configuration. Undo and restore clear stale restart state.
• Restart banners identify the affected client and number of pending changes. Dismissing a banner hides it without discarding the pending state.
• Claude Code project/workspace entries already present in .claude.json are discovered as read-only sources.
• A local MCP library scans a selected directory for supported JSON, JSONC, and TOML maps, then previews conflicts, warnings, and imports into built-in writable clients.
• A copy-paste agent prompt and strict JSON import flow validate the schema, fields, values, duplicates, and environment-variable names without accepting secret values.
• Server provenance, version, and maintenance state distinguish npm, Python, local package, local executable, remote, and unknown sources.
• A read-only skills inventory shows known global and workspace skill roots, scope, metadata status, duplicates, conflicts, and warnings.
• The in-app updater checks a fresh first-party manifest, downloads to private staging, verifies SHA-256 and version, and supports cancel, install, relaunch, and rollback.

Changed and fixed

• Health-check timeout messages preserve the configured duration and no longer show misleading zero-second errors.
• Read-only sources and their scope stay distinct from writable client configurations throughout the UI.
• Existing backup, external-change detection, digest guards, and atomic-write safeguards remain in the write path.

Security and privacy

• Configurations and secrets remain in native/local storage; secret values are not sent to the web UI, DTOs, logs, or updater requests.
• Discovery, scanning, inventory, and provenance checks do not execute discovered files or commands.
• The macOS build is not notarized. The Windows installer is not Authenticode-signed. Verify the SHA-256 checksum before bypassing Gatekeeper or SmartScreen.

Install

macOS — open the DMG, drag KyttoMCP into Applications, then Control-click the app and choose Open.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

Downloads

Platform	File	Size	SHA-256
macOS (Apple Silicon)	KyttoMCP-1.0.5.dmg	4.1 MB	ad9d5dcbc0646697c965ef9d0bd493e6249d59650a48b2ff424e6c3c7f288369
Windows x64	Kytto-Setup-win-x64-1.0.5.exe	78.4 MB	851be7f910e6d40d541d9a17e35df099f75059cfad130100602fe6163c36eae9

From this release the macOS build is Apple Silicon only, M1 and later. Intel Macs are not supported; earlier releases on this page still carry a universal build.

This beta is not yet notarized or Authenticode-signed. Only open builds downloaded from this release or kytto.jakubhecht.sk, and verify the checksum before opening them.

KyttoMCP 1.0.4.1

KyttoMCP 1.0.4.1 is a small cross-platform beta update.

What’s new

• Added an automatic updater that checks for a newer KyttoMCP release.

• Added a manual Check for updates action so you can start the check yourself.

No other new features are included in this release.

Install

macOS — open the DMG, drag KyttoMCP to Applications, then Control-click the app and choose Open.

Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway.

This beta is not yet signed with paid Apple and Microsoft developer certificates, so both systems may show a caution screen. Only open a build downloaded from this release or from kytto.jakubhecht.sk, and verify the checksum below.

Checksums

File | Size | SHA-256 -- | -- | -- KyttoMCP-1.0.4.1.dmg | 5.3 MB | 578beaa8fcccfc9fbdb5828cc2713faa9b885b36bae49e7c89f6934838c883a4 Kytto-Setup-win-x64-1.0.4.1.exe | 78.4 MB | e551166f130d712a96bf194b609cd5ceffbfb266792a8ab316e09fca477c2fd7

Full changelog: CHANGELOG.md

KyttoMCP 1.0.4.1 is a small cross-platform beta update. What’s new Added an automatic updater that checks for a newer KyttoMCP release.
 Added a manual Check for updates action so you can start the check yourself.
 No other new features are included in this release. Install macOS — open the DMG, drag KyttoMCP to Applications, then Control-click the app and choose Open. Windows — run the setup file. At the SmartScreen prompt choose More info → Run anyway. This beta is not yet signed with paid Apple and Microsoft developer certificates, so both systems may show a caution screen. Only open a build downloaded from this release or from [kytto.jakubhecht.sk](https://kytto.jakubhecht.sk/), and verify the checksum below. Checksums File Size SHA-256 KyttoMCP-1.0.4.1.dmg 5.3 MB 578beaa8fcccfc9fbdb5828cc2713faa9b885b36bae49e7c89f6934838c883a4 Kytto-Setup-win-x64-1.0.4.1.exe 78.4 MB e551166f130d712a96bf194b609cd5ceffbfb266792a8ab316e09fca477c2fd7 Full changelog: [CHANGELOG.md](https://github.com/heyitsjakub/KyttoMCP/blob/main/CHANGELOG.md)