Asynthetic
REMOTE · ASYNTHETIC.UP.RAILWAY.APP · 3 COMPONENTS · SCANNED SEP 22
Ground truth for AI coding agents: what breaks between library versions and how to fix it
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the Asynthetic MCP server?
Asynthetic is a hosted endpoint at https://asynthetic.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · asynthetic.up.railway.app
claude mcp add --transport http asyntheticai-asynthetic 'https://asynthetic.up.railway.app/mcp'
{
"mcpServers": {
"asyntheticai-asynthetic": {
"url": "https://asynthetic.up.railway.app/mcp"
}
}
} {
"servers": {
"asyntheticai-asynthetic": {
"type": "http",
"url": "https://asynthetic.up.railway.app/mcp"
}
}
} [mcp_servers.asyntheticai-asynthetic] url = "https://asynthetic.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"asyntheticai-asynthetic": {
"type": "remote",
"url": "https://asynthetic.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add asyntheticai-asynthetic --url 'https://asynthetic.up.railway.app/mcp' --transport streamable-http
mcp_servers:
asyntheticai-asynthetic:
url: "https://asynthetic.up.railway.app/mcp" {
"McpServers": {
"asyntheticai-asynthetic": {
"Transport": "http",
"Url": "https://asynthetic.up.railway.app/mcp"
}
}
} assistant mcp add asyntheticai-asynthetic -t streamable-http -u 'https://asynthetic.up.railway.app/mcp'
{
"mcpServers": {
"asyntheticai-asynthetic": {
"type": "http",
"url": "https://asynthetic.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Aug 26 0
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.27 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the tool list to see what that exposes. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Probed https://asynthetic.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE1,O=Let's Encrypt,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 6da79bb561da3efeb0e751ca21abd3999fe |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of asynthetic.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 404 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://asynthetic.up.railway.app/mcp | HTTP error | 404 | |
| http (plaintext) | http://asynthetic.up.railway.app/mcp | HTTPS enforced | 301 | https://asynthetic.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_compatibility Check cross-package compatibility (not yet implemented) ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default "npm") |
| package_a | string | yes | First package name (planned project-aware check), e.g. "next" |
| package_b | string | yes | Second package name, e.g. "react" |
| version_a | string | yes | Version of package_a, e.g. "15.0.0" |
| version_b | string | yes | Version of package_b, e.g. "19.0.0" |
| Name | Type | Req | Description |
|---|---|---|---|
| implemented | boolean | yes | Always false — this tool is a reserved stub |
| message | string | yes | – |
No examples provided.
check_peer_compatibility Check peer compatibility between two package versions ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default "npm") |
| package_a | string | yes | First package name, e.g. "next" |
| package_b | string | yes | Second package name, e.g. "react" |
| version_a | string | yes | Version (or SemVer range) of package_a, e.g. "15.0.0" |
| version_b | string | yes | Version (or SemVer range) of package_b, e.g. "18.2.0" |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| compatible | – | yes | true | false | "unknown" ("unknown" = absence of data, not incompatibility) |
| reason | string | yes | – |
| requested | object | yes | – |
| source_maps_used | array | yes | – |
No examples provided.
get_breaking_changes Get breaking changes in a version ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default "npm") |
| package | string | yes | Package name as published, e.g. "@modelcontextprotocol/sdk" |
| version | string | yes | The version (or SemVer range) whose breaking changes you want, e.g. "2.0.0", "^15.0.0" |
| Name | Type | Req | Description |
|---|---|---|---|
| available_maps | array | – | – |
| available_maps_truncated | boolean | – | – |
| coverage_hint | string | – | – |
| found | boolean | yes | – |
| message | string | – | – |
| requested | object | yes | – |
| results | array | – | – |
No examples provided.
get_migration Get migration map ~219
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Package ecosystem (default "npm") |
| from_version | string | yes | Version or SemVer range currently in use, e.g. "1.29.0", "^14.2.0", "1.x" |
| package | string | yes | Package name as published, e.g. "@modelcontextprotocol/sdk" |
| to_version | string | yes | Version or SemVer range upgrading to, e.g. "2.0.0", "^15.0.0", "2.x" |
| Name | Type | Req | Description |
|---|---|---|---|
| available_maps | array | – | – |
| available_maps_truncated | boolean | – | – |
| coverage_hint | string | – | – |
| found | boolean | yes | Whether a verified map covers the requested upgrade |
| match_note | string | – | – |
| match_type | string | – | "exact" | "semver-range" | "major-version" |
| message | string | – | Anti-hallucination guidance (present when not found) |
| migration | object | – | The full migration map (present when found) |
| requested | object | yes | – |
| resolved_via | string | – | "exact_string" | "semver_range" | "major_version" |
| source_count | number | – | – |
| verification_level | string | – | "high" | "medium" | "low" |
| warning | string | – | – |
No examples provided.
list_available_maps List available migration maps ~88
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ecosystem | string | – | Filter by ecosystem, e.g. "npm" |
| package | string | – | Filter by exact package name (case-insensitive) |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | – |
| maps | array | yes | – |
No examples provided.
What is the Asynthetic MCP server?
Asynthetic is an MCP server listed in the public MCP registry as io.github.asyntheticai/asynthetic. Ground truth for AI coding agents: what breaks between library versions and how to fix it. This page covers its hosted endpoint (https://asynthetic.up.railway.app/mcp).
Is the Asynthetic MCP server safe to use?
Asynthetic scores 23 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Asynthetic MCP server expose?
Asynthetic exposes 5 tools: get_migration, get_breaking_changes, list_available_maps, check_peer_compatibility, check_compatibility. Their descriptions and schemas cost roughly 808 tokens of context every time the server is loaded.
Does the Asynthetic MCP server require authentication?
No. We connected to Asynthetic without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Asynthetic MCP server still maintained?
Asynthetic is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.