# Snap Router (pypi · snap-router-mcp)

Task-to-tool discovery over the merged x402 Bazaar + MCP Registry catalog

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

## Components

- pypi · `snap-router-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/trigeochiral-snap-router/snap-router-mcp.md), [page](https://verifymcp.io/servers/trigeochiral-snap-router/snap-router-mcp)

## Channel facts

- Registry: `pypi`
- Package: `snap-router-mcp`
- Version: `1.0.0`
- 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-09-20.

- **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 setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - 0 of 9 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 15 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 186 tokens (~186/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 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.
- **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 Snap Router MCP server?

Snap Router runs locally as a PyPI package, launched with uvx snap-router-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 trigeochiral-snap-router -- uvx snap-router-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "trigeochiral-snap-router": {
      "command": "uvx",
      "args": [
        "snap-router-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "trigeochiral-snap-router": {
      "command": "uvx",
      "args": [
        "snap-router-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add trigeochiral-snap-router -- uvx snap-router-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add trigeochiral-snap-router --command uvx --arg snap-router-mcp
```

### Hermes

```yaml
mcp_servers:
  trigeochiral-snap-router:
    command: "uvx"
    args: ["snap-router-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "trigeochiral-snap-router": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "snap-router-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add trigeochiral-snap-router -t stdio -c uvx -a snap-router-mcp
```

### Other

```json
{
  "mcpServers": {
    "trigeochiral-snap-router": {
      "command": "uvx",
      "args": [
        "snap-router-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-09-20 (score 64, +1)

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

### 2026-09-18 (score 63, +1)

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

### 2026-09-15 (score 62, −14)

- [security regression] Malware scan: pass → unverified

### 2026-09-14 (score 76, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-09-13 (score 61, +1)

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

### 2026-09-11 (score 60, +4)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-04 (score 56)

First indexed and scored.

## MCP tools (1)

### `snap_router` (~186 tokens)

Snap Router — task to the right tool

Tool/service DISCOVERY, not execution. Input: an agent task in plain words. Output: a ranked shortlist of x402 services and MCP tools from the merged x402 Bazaar + MCP Registry catalog (16k+ entries) that can do it, each with price and a 'works well with' hint. One vector pass, ~200ms, no LLM call, hybrid keyword-fill so nothing is missed. Call this FIRST, before loading candidate tools into context, whenever you do not already know which tool serves a task. Example task: 'check a Base token for a honeypot before trading'.

Input parameters:

- `k` (integer): how many results to return
- `max_price_usdc` (number): drop results priced above this
- `registries` (array): restrict to these catalogs (default: both)
- `task` (string, required): the task, in plain language

Output parameters:

- `engine` (string)
- `picks` (array)
- `task` (string)
- `works_well_with` (array)

## Diagnostics

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

## Score history

- 2026-09-20: 64
- 2026-09-19: 63
- 2026-09-18: 63
- 2026-09-17: 62
- 2026-09-16: 62
- 2026-09-15: 62
- 2026-09-14: 76
- 2026-09-13: 61
- 2026-09-12: 60
- 2026-09-11: 60
- 2026-09-10: 56
- 2026-09-09: 56
- 2026-09-08: 56
- 2026-09-07: 56
- 2026-09-06: 56
- 2026-09-05: 56
- 2026-09-04: 56

## Common questions

### What is the Snap Router MCP server?

Snap Router is an MCP server listed in the public MCP registry as io.github.trigeochiral/snap-router. Task-to-tool discovery over the merged x402 Bazaar + MCP Registry catalog. This page covers its PyPI package (snap-router-mcp).

### Is the Snap Router MCP server safe to use?

Snap Router scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 Snap Router MCP server expose?

Snap Router exposes 1 tool: snap_router. Their descriptions and schemas cost roughly 186 tokens of context every time the server is loaded.

### Is the Snap Router MCP server still maintained?

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

Snap Router 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/snap-router-mcp/
- Socket report: https://socket.dev/pypi/package/snap-router-mcp
- Repository: https://github.com/trigeochiral/snap-router-mcp
- Website: https://trigeochiral.com/
- Changelog RSS feed: https://verifymcp.io/servers/trigeochiral-snap-router/snap-router-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/trigeochiral-snap-router/snap-router-mcp.json
- HTML version of this page: https://verifymcp.io/servers/trigeochiral-snap-router/snap-router-mcp