Every ~15 minutes we run a handshake against about 2,043 public MCP servers. The results are on a live board at https://toolweather.pages.dev, and they're a useful reality check for anyone building agents.
The numbers
- ~74% legacy-only (706 of 952 classified servers): not ready for the 2026-07-28 spec. Only ~26% are dual-era or modern.
- ~47% healthy/open, ~51% behind auth.
- 128 ms median handshake, 14,938 tools tracked.
Why it matters
If your client only speaks the new protocol, most servers will fail quietly. And agents that call tools or pay merchants they've never seen need a cheap "should I?" check first.
What we built (free, no signup)
All of this runs on free Cloudflare Workers + D1, exposed as MCP:
- Toolweather: health/protocol/latency for any listed MCP server. https://toolweather.toolweather.workers.dev
- Upstream: upgrade/dependency checks.
- SpendGate: approve / ask a human / block before an agent spends. https://spendgate.toolweather.workers.dev
-
PayCheck: trust verdict (trusted / unknown / suspicious / block) for a merchant, URL or 0x wallet. https://paycheck.toolweather.workers.dev —
POST /v1/checkwith{"target": "example.com"}.
SpendGate uses a local allowlist for well-known merchants (no network call), and asks PayCheck about everything else. Workers on the same account talk through a service binding, because a workers.dev self-fetch fails. If the lookup fails, it falls back to local classification.
One MCP connection to the Toolweather bundle gets you all of it. Paid usage beyond free quota is via x402 (USDC on Base).
For server authors
Free live badge for your README:
[](https://toolweather.pages.dev/)
Also on Glama: https://glama.ai/mcp/servers/toolweather/paycheck
Feedback on the methodology welcome.
Top comments (0)