Toolbooth eliminates API key friction for AI agents. Instead of managing dozens of API keys, signups, and billing accounts, your agent connects to one MCP endpoint and pays USDC micropayments per tool call via the x402 protocol on Solana mainnet. 22 tools across two categories: Solana Intelligence — on-chain data powered by Helius: • token_price ($0.0005) — real-time USD price for any SPL token • wallet_profile ($0.005) — full wallet breakdown with USD values • token_risk_score ($0.005) — 0-100 risk score from holder analysis • transaction_parse ($0.002) — human-readable transaction parsing • whale_alert ($0.01) — detect large wallet movements • dex_liquidity ($0.002) — pool depth and TVL ratings • token_holders ($0.005) — holder distribution and concentration • wallet_pnl ($0.05) — realized/unrealized PnL from swap history • copy_trade_signals ($0.01) — active positions and trading patterns Agent Concierge — we hold the API keys: • web_search ($0.01)
ToolBooth is a remote MCP server published at toolbooth.io. It has been probed 5 times since 9/10/2026. It answered in 5 of them (100.0%), a near-uninterrupted record. Median response time is 985 ms, a delay an agent will notice. It exposes a broad tool surface of 58 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
dependency_risk_score — Incomplete description truncates critical information about hallucination checks.crypto_sentiment — Description cuts off mid-sentence, leaving sources and methodology unclear.token_price — Parameter 'mint address' is clear, but no mention of optional parameters or validation rules.Risk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/toolbooth-sol402)<a href="https://mcpmetrics.io/servers/toolbooth-sol402"><img src="https://mcpmetrics.io/badge/toolbooth/sol402/era.svg" alt="mcpmetrics"></a>You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.
Sign up free to see| Run | Era | Modern | ms | Legacy | ms | Versions |
|---|---|---|---|---|---|---|
| 2026-09-11 16:59:56 | Legacy | 400 | 1009 | 200 | 718 | 2025-11-25 |
| 2026-09-11 15:07:20 | Legacy | 400 | 1278 | 200 | 974 | 2025-11-25 |
| 2026-09-11 13:13:33 | Legacy | 400 | 1343 | 200 | 1354 | 2025-11-25 |
| 2026-09-11 11:20:19 | Legacy | 400 | 913 | 200 | 985 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 341 | 401 | 384 | — |
Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.
The two probe legs separately: modern server/discover and legacy initialize.