# Asynthetic (remote · asynthetic.up.railway.app)

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

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `asynthetic.up.railway.app`: 66/100 (this document), [markdown](https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic.md), [page](https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic)
- remote · `asynthetic.up.railway.app`: 60/100, [markdown](https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic-2.md), [page](https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic-2)
- npm · `asynthetic`: 62/100, [markdown](https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic-3.md), [page](https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic-3)

## Channel facts

- Endpoint: `https://asynthetic.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http asyntheticai-asynthetic https://asynthetic.up.railway.app/mcp
```

### Codex

```toml
[mcp_servers.asyntheticai-asynthetic]
url = "https://asynthetic.up.railway.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "asyntheticai-asynthetic": {
      "type": "remote",
      "url": "https://asynthetic.up.railway.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add asyntheticai-asynthetic --url https://asynthetic.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  asyntheticai-asynthetic:
    url: "https://asynthetic.up.railway.app/mcp"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +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.

### 2026-08-01 (score 65, +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.

### 2026-07-31 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 64, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +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.

### 2026-07-28 (score 63, +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.

### 2026-07-27 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (5)

### `get_migration` (~219 tokens)

Get migration map

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.

Input parameters:

- `ecosystem` (string): Package ecosystem (default "npm")
- `from_version` (string, required): Version or SemVer range currently in use, e.g. "1.29.0", "^14.2.0", "1.x"
- `package` (string, required): Package name as published, e.g. "@modelcontextprotocol/sdk"
- `to_version` (string, required): Version or SemVer range upgrading to, e.g. "2.0.0", "^15.0.0", "2.x"

Output parameters:

- `available_maps` (array)
- `available_maps_truncated` (boolean)
- `coverage_hint` (string)
- `found` (boolean): 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)
- `resolved_via` (string): "exact_string" | "semver_range" | "major_version"
- `source_count` (number)
- `verification_level` (string): "high" | "medium" | "low"
- `warning` (string)

### `get_breaking_changes` (~158 tokens)

Get breaking changes in a version

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.

Input parameters:

- `ecosystem` (string): Package ecosystem (default "npm")
- `package` (string, required): Package name as published, e.g. "@modelcontextprotocol/sdk"
- `version` (string, required): The version (or SemVer range) whose breaking changes you want, e.g. "2.0.0", "^15.0.0"

Output parameters:

- `available_maps` (array)
- `available_maps_truncated` (boolean)
- `coverage_hint` (string)
- `found` (boolean)
- `message` (string)
- `requested` (object)
- `results` (array)

### `list_available_maps` (~88 tokens)

List available migration 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.

Input parameters:

- `ecosystem` (string): Filter by ecosystem, e.g. "npm"
- `package` (string): Filter by exact package name (case-insensitive)

Output parameters:

- `count` (number)
- `maps` (array)

### `check_peer_compatibility` (~187 tokens)

Check peer compatibility between two package versions

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.

Input parameters:

- `ecosystem` (string): Package ecosystem (default "npm")
- `package_a` (string, required): First package name, e.g. "next"
- `package_b` (string, required): Second package name, e.g. "react"
- `version_a` (string, required): Version (or SemVer range) of package_a, e.g. "15.0.0"
- `version_b` (string, required): Version (or SemVer range) of package_b, e.g. "18.2.0"

Output parameters:

- `checks` (array)
- `compatible`: true | false | "unknown" ("unknown" = absence of data, not incompatibility)
- `reason` (string)
- `requested` (object)
- `source_maps_used` (array)

### `check_compatibility` (~156 tokens)

Check cross-package compatibility (not yet implemented)

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.

Input parameters:

- `ecosystem` (string): Package ecosystem (default "npm")
- `package_a` (string, required): First package name (planned project-aware check), e.g. "next"
- `package_b` (string, required): Second package name, e.g. "react"
- `version_a` (string, required): Version of package_a, e.g. "15.0.0"
- `version_b` (string, required): Version of package_b, e.g. "19.0.0"

Output parameters:

- `implemented` (boolean): Always false — this tool is a reserved stub
- `message` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 64
- 2026-07-30: 64
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 62
- 2026-07-26: 62

## Links

- Remote endpoint: https://asynthetic.up.railway.app/mcp
- Repository: https://github.com/asyntheticai/asynthetic
- Changelog RSS feed: https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic/changelog.json
- HTML version of this page: https://verifymcp.io/servers/asyntheticai-asynthetic/asynthetic