Asynthetic
NPM · ASYNTHETIC · 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 from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 106 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (BUSL-1.1) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 78 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 808 tokens (~161/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Asynthetic MCP server?
Asynthetic runs locally as an npm package, launched with npx -y asynthetic. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · asynthetic
claude mcp add asyntheticai-asynthetic -- npx -y asynthetic
{
"mcpServers": {
"asyntheticai-asynthetic": {
"command": "npx",
"args": [
"-y",
"asynthetic"
]
}
}
} {
"servers": {
"asyntheticai-asynthetic": {
"command": "npx",
"args": [
"-y",
"asynthetic"
]
}
}
} codex mcp add asyntheticai-asynthetic -- npx -y asynthetic
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"asyntheticai-asynthetic": {
"type": "local",
"command": [
"npx",
"-y",
"asynthetic"
],
"enabled": true
}
}
} openclaw mcp add asyntheticai-asynthetic --command npx --arg -y --arg asynthetic
mcp_servers:
asyntheticai-asynthetic:
command: "npx"
args: ["-y", "asynthetic"] {
"McpServers": {
"asyntheticai-asynthetic": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"asynthetic"
]
}
}
} assistant mcp add asyntheticai-asynthetic -t stdio -c npx -a -y asynthetic
{
"mcpServers": {
"asyntheticai-asynthetic": {
"command": "npx",
"args": [
"-y",
"asynthetic"
]
}
}
} 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.
- 22 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 21 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
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 · Analysed npm/asynthetic@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 106 packages
| Packages resolved | 106 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 npm package (asynthetic).
Is the Asynthetic MCP server safe to use?
Asynthetic scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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.
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.
What licence is the Asynthetic MCP server under?
Asynthetic declares the BUSL-1.1 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.