Asynthetic
REMOTE · ASYNTHETIC.UP.RAILWAY.APP · 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 against the live server, and we only credit what we can confirm. How we 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 call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
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 Management27
- Stability observed for 8 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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · asynthetic.up.railway.app
claude mcp add --transport http asyntheticai-asynthetic 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": {
"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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 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
- 29 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Jul 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 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 62
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 · 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 |
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 | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://asynthetic.up.railway.app/mcp | Verified | 200 | |
| 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.
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.