Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Snap Router

PYPI · SNAP-ROUTER-MCP · SCANNED SEP 20

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

Available components

+3 this week 64 Trust /100
Trust breakdown (7 categories)

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 → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 0 of 9 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 186 tokens (~186/item across 1 items; 1 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.

pypi · snap-router-mcp

# add to Claude Code
claude mcp add trigeochiral-snap-router -- uvx snap-router-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "trigeochiral-snap-router": {
      "command": "uvx",
      "args": [
        "snap-router-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "trigeochiral-snap-router": {
      "command": "uvx",
      "args": [
        "snap-router-mcp"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add trigeochiral-snap-router --command uvx --arg snap-router-mcp
# ~/.hermes/config.yaml
mcp_servers:
  trigeochiral-snap-router:
    command: "uvx"
    args: ["snap-router-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "trigeochiral-snap-router": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "snap-router-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add trigeochiral-snap-router -t stdio -c uvx -a snap-router-mcp
// mcp.json
{
  "mcpServers": {
    "trigeochiral-snap-router": {
      "command": "uvx",
      "args": [
        "snap-router-mcp"
      ]
    }
  }
}
Changelog

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.

  • 20 Sept 26 +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.

  • 18 Sept 26 +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.

  • 15 Sept 26 −14
    • Malware scan: pass → unverified security
  • 14 Sept 26 +15
    • Malware scan: unverified → pass security
  • 13 Sept 26 +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.

  • 11 Sept 26 +4
    • Stability: unverified → 0.23 functional
  • 4 Sept 26 56

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Analysed pypi/snap-router-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 9 packages
Packages resolved 9
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~186 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
snap_router ~186

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'.

NameTypeReqDescription
kintegerhow many results to return
max_price_usdcnumberdrop results priced above this
registriesarrayrestrict to these catalogs (default: both)
taskstringyesthe task, in plain language
NameTypeReqDescription
enginestring
picksarrayyes
taskstringyes
works_well_witharray

No examples provided.

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.