Snap Router
PYPI · SNAP-ROUTER-MCP
Task-to-tool discovery over the merged x402 Bazaar + MCP Registry catalog
Available components
Last scanned (1 day ago)
Scores higher than 66% of PyPI servers
Category Search and Retrieval
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 build step with no custom scripting around it. View diagnostics → Pass
- 0 of 8 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 60 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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.
- 4 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 30 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.97 functional
- 28 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 24 Oct 26 0
- Stability: 0.97 → pass security
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 4 Nov 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 |
| Reason | No attestation published |
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 8 packages
| Packages resolved | 8 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
snap_router Snap Router — task to the right tool ~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'.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | the task, in plain language |
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | – | – |
| picks | array | yes | – |
| task | string | yes | – |
| works_well_with | array | – | – |
No examples provided.
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
claude mcp add trigeochiral-snap-router -- uvx snap-router-mcp
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 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 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 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 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.