Asynthetic
NPM · ASYNTHETIC · 3 COMPONENTS · SCANNED AUG 3
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 →
Supply Chain Security88
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (105 of 106), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (105 of 106), so this covers what we could see, not the whole tree. 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 28 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability70
- 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · asynthetic
claude mcp add asyntheticai-asynthetic -- npx -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": {
"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.
- 2 Aug 26 +43
- Provenance: unverified → fail ▼ security
- Known CVEs: unverified → partial ▲ security
- Install scripts: unverified → pass ▲ security
- Malware scan: unverified → pass ▲ security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- License: unverified → fail ▼ functional
- Maintenance: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Dependency health: unverified → partial ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Licence: BUSL-1.1 functional
- 1 Aug 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 −18
- Malware scan: pass → unverified ▼ security
- 28 Jul 26 +20
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: unverified functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- First check of Schema quality: fail functional
- 27 Jul 26 24
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 105 packages
105 packages in the resolved dependency tree · 104 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.