# RouteVerdict (pypi · route-verdict-mcp)

MCP server for RouteVerdict — x402 endpoint trust checks ($0.05 USDC on Base)

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- pypi · `route-verdict-mcp`: 69/100 (this document), [markdown](https://verifymcp.io/servers/quincygb-route-verdict-mcp/route-verdict-mcp.md), [page](https://verifymcp.io/servers/quincygb-route-verdict-mcp/route-verdict-mcp)

## Channel facts

- Registry: `pypi`
- Package: `route-verdict-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-04.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 0 of 46 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to QuincyGB/route-verdict-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 151 tokens (~151/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the RouteVerdict MCP server?

RouteVerdict runs locally as a PyPI package, launched with uvx route-verdict-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add quincygb-route-verdict-mcp -- uvx route-verdict-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "quincygb-route-verdict-mcp": {
      "command": "uvx",
      "args": [
        "route-verdict-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "quincygb-route-verdict-mcp": {
      "command": "uvx",
      "args": [
        "route-verdict-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add quincygb-route-verdict-mcp -- uvx route-verdict-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "quincygb-route-verdict-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "route-verdict-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add quincygb-route-verdict-mcp --command uvx --arg route-verdict-mcp
```

### Hermes

```yaml
mcp_servers:
  quincygb-route-verdict-mcp:
    command: "uvx"
    args: ["route-verdict-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "quincygb-route-verdict-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "route-verdict-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add quincygb-route-verdict-mcp -t stdio -c uvx -a route-verdict-mcp
```

### Other

```json
{
  "mcpServers": {
    "quincygb-route-verdict-mcp": {
      "command": "uvx",
      "args": [
        "route-verdict-mcp"
      ]
    }
  }
}
```

## 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-11-04 (score 69, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-03 (score 84, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 68, +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-10-30 (score 67, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-28 (score 66, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-27 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 80, +46)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.10
- [functional improvement] MCP protocol: unverified → pass

## MCP tools (1)

### `route_check` (~151 tokens)

Audit an x402 endpoint's trust and liveness before paying or relying on it.

Calls RouteVerdict (POST /v1/check, $0.05 USDC on Base via x402).
Returns a verdict (TRUSTED / CAUTION / AVOID) with a 0-100 trust
score, an itemized deduction list, a live 402 probe of the target
(the target is never paid), its published terms, discovery-schema
quality, catalog presence in the CDP Bazaar and PayAI indexes, and
a diff against the last check of the same URL.

Args:
    resource_url: Full URL of the x402 resource to audit.

Input parameters:

- `resource_url` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/quincygb-route-verdict-mcp/route-verdict-mcp#diagnostics

## Score history

- 2026-11-04: 69
- 2026-11-03: 84
- 2026-11-02: 68
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 67
- 2026-10-29: 82
- 2026-10-28: 66
- 2026-10-27: 81
- 2026-10-26: 80
- 2026-10-25: 34
- 2026-10-24: 79
- 2026-10-23: 64

## Common questions

### What is the RouteVerdict MCP server?

RouteVerdict is an MCP server listed in the public MCP registry as io.github.QuincyGB/route-verdict-mcp. MCP server for RouteVerdict, x402 endpoint trust checks ($0.05 USDC on Base). This page covers its PyPI package (route-verdict-mcp).

### Is the RouteVerdict MCP server safe to use?

RouteVerdict scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 RouteVerdict MCP server expose?

RouteVerdict exposes 1 tool: route_check. Their descriptions and schemas cost roughly 151 tokens of context every time the server is loaded.

### Is the RouteVerdict MCP server still maintained?

RouteVerdict is still listed as active in the MCP registry. We last reached this channel on 4 November 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 RouteVerdict MCP server under?

RouteVerdict declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/route-verdict-mcp/
- Socket report: https://socket.dev/pypi/package/route-verdict-mcp
- Repository: https://github.com/QuincyGB/route-verdict-mcp
- Changelog RSS feed: https://verifymcp.io/servers/quincygb-route-verdict-mcp/route-verdict-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/quincygb-route-verdict-mcp/route-verdict-mcp.json
- HTML version of this page: https://verifymcp.io/servers/quincygb-route-verdict-mcp/route-verdict-mcp