mcpbeat

Asynthetic MCP Server

io.github.asyntheticai/asynthetic
not responding

Asynthetic is listed as active in the registry but did not answer our last check. 39 installs a week from npm. It exposes 5 tools. Last commit 5 Jul 2026.

Ground truth for AI coding agents: what breaks between library versions and how to fix it

Installs per day peak 214 · avg 22 · -47% w/w
a month agotoday
Uptime history 39 hours of history · worst hour 0%
39 hours agonow
10.4%
Uptime 24h
19 of 182 checks
5
Tools
read from the server
343 ms
Response time
average over 24h
39
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add asynthetic --transport http https://asynthetic.up.railway.app/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "asynthetic": {
      "url": "https://asynthetic.up.railway.app/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.asynthetic]
url = "https://asynthetic.up.railway.app/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "asynthetic": {
      "url": "https://asynthetic.up.railway.app/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "asynthetic": {
      "url": "https://asynthetic.up.railway.app/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

available
list_available_maps
Lists every migration map in the store: package, ecosystem, from_version, to_version, status (draft/verified/stale), last_verified. Optional filters: ecosystem, package. Use this to discover coverage before calling get_migration.
breaking
get_breaking_changes
Returns the breaking changes introduced when upgrading TO the given version of a package (matched by major version against curated migration maps), with source citations and last_verified dates. Accepts concrete versions or SemVer ranges ("15", "^15.0.0", "15.x"); resolution is disclosed via match_type/resolved_via. If found=false, no verified data exists — do not guess.
compatibility
check_compatibility
PLANNED: project-aware compatibility analysis. Currently returns implemented=false and no data. Do not infer compatibility (or incompatibility) from this response. For a static SemVer check between two known package versions, use check_peer_compatibility instead.
migration
get_migration
Returns the verified migration map for upgrading a package between two versions: ordered breaking changes with before/after code, deprecations, source-citation URLs, and a last_verified date. Accepts concrete versions or SemVer ranges (e.g. "^14.2.0", "~14.1.0", "15.x"); non-exact lookups resolve to the covering map and disclose how via match_type/resolved_via/match_note. If found=false, no verified data exists — do not guess.
peer
check_peer_compatibility
Static SemVer check of two known package versions against curated compatible_with peer data from migration maps. Purely declarative — no filesystem access or project inspection (that is the scope of the separate, unimplemented check_compatibility). Returns compatible: true | false | "unknown". Treat "unknown" as absence of curated data, never as evidence of incompatibility.

Endpoints

URLTransportStateLatencyChecked
https://asynthetic.up.railway.app/mcp streamable-http answering 369 ms 6 min ago
https://asynthetic.up.railway.app/sse sse answering 339 ms 7 min ago

Asynthetic — questions

Answers built from our own checks of this server.

What can Asynthetic do?
It exposes 5 tools, read directly from the server on our last check. Among them: check_compatibility, check_peer_compatibility, get_breaking_changes, get_migration, list_available_maps. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Asynthetic working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 19 of 182 checks got a reply (10.4%), average response time 343 ms. The bar chart above shows every period we have measured.
The registry lists Asynthetic as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Asynthetic?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Asynthetic need an API key?
No. Asynthetic completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Asynthetic?
It answers our handshake in 343 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use Asynthetic?
The npm package asynthetic was installed 39 times in the last week. Week over week that is -47%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Asynthetic open source?
Yes — it is published under the NOASSERTION licence, written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.