smithery toolbox
ai.smithery/smithery-toolbox
Toolbox dynamically routes to all MCPs in the Smithery registry based on your agent's need. When a…
— the operator's own registry description reported
Publisher ai.smithery · first seen 2026-08-12 · endpoint https://server.smithery.ai/@smithery/toolbox/mcp
Dependency rating derived
block — dead / unreachable · kind unknown · V n/a
Cluster dead-listing · distinctiveness —. Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.
🔏 Signed receipt rr_a979bf09b980fed3a0b423ec · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.
● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →
History observed
Every probe we made, oldest → newest (2 shown, 2026-08-12 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.
changelog (1 events)
| date | type | what changed |
|---|---|---|
| 2026-08-12 | outcome | first probe: http_error |
What kind of tools these are derived
Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from the operator's own registry description — REPORTED, not observed (tools were not visible to the probe). What checking applies to each kind (the full methodology →):
| nature | tools | meaning | what checking applies |
|---|---|---|---|
| unclassified | 1 | not classifiable from its text | Tier-1 only until its tools describe themselves |
Tools last seen observed
Truth checks observed
Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.
Drift observed
No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.
Looking for an alternative?
This server doesn't answer, but these live, allow-verdict servers describe themselves similarly — similar by what they say they do — never verified drop-in replacements; check each one before depending on it.
| server | verdict | shared terms |
|---|---|---|
| io.github.lonniev/cypher-mcp Monetized graph answers via named Cypher queries — Tollbooth DPYC operator | allow | all, dynamically, mcps, routes |
| io.github.conquext/neuron AI-powered WhatsApp chatbot platform with 196 tools for bots, campaigns, and contacts. | allow | all, dynamically, mcps |
| io.github.statico-alt/spacemolt MMO game for AI agents: mine, trade, craft, explore, and battle in a galaxy of ~500 systems | allow | all, dynamically, routes |
| io.github.lonniev/excalibur-mcp FastMCP server for posting formatted content to X (Twitter) — Tollbooth-monetized, DPYC-native | allow | all, dynamically, mcps |
| io.github.ivaavimusic/singularity MCP for Singularity Layer - discover listings, manage assets, run payment flows, and use agents | allow | all, mcps, routes |
raw probe records
| probed (UTC) | outcome | http | ms | protocol |
|---|---|---|---|---|
| 2026-08-14T19:57:41Z | http_error | 404 | 228 | |
| 2026-08-12T05:32:58Z | http_error | 404 | 224 |
Watch or embed this verdict
Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:
[](https://robinsaige.com/s/ai.smithery/smithery-toolbox)
Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.