https://mcp.tokenguard.net/mcp ↗
Use this MCP server when your agent needs to verify token safety before executing a trade or assess wallet risk before interacting with an unknown address. Covers Solana/Pump.fun (474ms p50), Base, Ethereum, and Arbitrum. No API keys — pay per query in USDC on Base via x402. Tools: check_pump_token (Pump.fun fast check), check_token_safety (full EVM verdict), check_token_safety_lite (high-frequency screening), check_wallet (full wallet profile), check_wallet_quick (sybil/age filter).
TokenGuard is a remote MCP server published at mcp.tokenguard.net. It has been probed 7 times since 9/10/2026. It answered in 7 of them (100.0%), a near-uninterrupted record. Median response time is 834 ms, a delay an agent will notice. It offers a narrow, focused set of 6 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.
check_token_safety — Truncated description ends mid-sentencecheck_token_safety_lite — Similar functionality to check_token_safety with unclear differentiationcheck_pump_token — Truncated description ends mid-sentencecheck_wallet — Truncated description ends mid-sentencecheck_wallet_quick — Truncated description ends mid-sentenceRisk: medium
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
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/riamsantky-baseguard-walletguard)<a href="https://mcpmetrics.io/servers/riamsantky-baseguard-walletguard"><img src="https://mcpmetrics.io/badge/riamsantky/baseguard-walletguard/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 11:20:19 | Legacy | 400 | 868 | 200 | 864 | 2025-11-25 |
| 2026-09-11 09:28:19 | Legacy | 400 | 748 | 200 | 834 | 2025-11-25 |
| 2026-09-11 07:35:54 | Legacy | 400 | 843 | 200 | 842 | 2025-11-25 |
| 2026-09-11 05:44:28 | Legacy | 400 | 771 | 200 | 769 | 2025-11-25 |
| 2026-09-11 03:50:39 | Legacy | 400 | 933 | 200 | 932 | 2025-11-25 |
| 2026-09-11 01:59:45 | Legacy | 400 | 618 | 200 | 616 | 2025-11-25 |
| 2026-09-10 21:16:35 | Auth-gated | 401 | 334 | 401 | 328 | — |
Each block is one measurement round. Green: working response. Amber: responded but the server was returning errors (5xx). Red: no response at all.
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.