Daily scanner tracks gap between MCP registry declarations and actual server responses

art2meta · reddit · 2026-10-13

The author of lowdown-proxy added a daily GitHub Actions scanner probing 2,000 MCP registry entries that declare streamable-http remotes, recording the gap between what the registry declares and what actually responds—snapshots, not uptime.

Findings

Recent changes: auto-retries for transient failures, per-entry gap reasons, npx lowdown-proxy zero-arg startup, registry API paging fallback, a lowdown-mcp-lookup skill on clawhub, and CSV mirroring to Hugging Face. Data CC BY 4.0, code MIT.

Limitations: no stdio-only coverage, single network location, and no confirmed external agent usage of the lookup API yet. The author declined paid directory listings and asks the community which history (reachability, schema changes, agent-reported outcomes) would actually help server selection.

Original post →

More from coding & agent

coding & agent channel →