lowdown-proxy
io.github.PetShopBros/lowdown-proxyVersion 0.1.23Dated facts on MCP servers: daily checks, Registry and card declarations, packages, payment terms.
Status
Responds396 msAnswered our handshake without sign-in.- Last checked
- Nov 14, 2026, 14:41 UTC
- Latency
- 396 ms
- Remotes responding
- 1 of 1
- Sign-in
- No sign-in
- Hosting
- Hosted outside the EU (detected)
- Registry data as of
- Nov 14, 2026, 21:12 UTC
Data from the official MCP Registry, checked by run.zero. How we check
Connect
Streamable HTTP
https://lowdown-proxy.vercel.app/mcpResponds396 msNo sign-in
Claude Code
claude mcp add --transport http lowdown-proxy https://lowdown-proxy.vercel.app/mcpClaude Desktop and claude.ai
Settings > Connectors > Add custom connector
Name: lowdown-proxy
Remote MCP server URL: https://lowdown-proxy.vercel.app/mcpCursor
{
"mcpServers": {
"lowdown-proxy": {
"url": "https://lowdown-proxy.vercel.app/mcp"
}
}
}VS Code
code --add-mcp '{"name":"lowdown-proxy","type":"http","url":"https://lowdown-proxy.vercel.app/mcp"}'Streamable HTTP
npm: lowdown-proxy 0.1.23Package only
npm (npx)
claude mcp add lowdown-proxy -- npx -y lowdown-proxy@0.1.23Built your own server? run.zero hosts MCP servers on European infrastructure.
Tools
2 tools
Read-only | Idempotent | Open world | ||
|---|---|---|---|---|
find_serversLowdown(로우다운) lists public MCP servers by observed facts, when you do not have a server name yet. Use does to find servers by what they do (words in the Registry name or tool names, e.g. 'postgres'). Filter by the latest daily check (e.g. state 'answered' = answered initialize and tools/list without credentials), days answered in the last 30, how long the tool list has been unchanged, tool count, Registry status and package state; sort by one key. No score or ranking: order is only the chosen sort key. Each result carries a lookup URL; call get_lowdown with its name for the full record. Tool lists are recorded from 2026-10-20, so a long stable_days returns nothing yet. | No | Yes | Yes | No |
get_lowdownLowdown(로우다운) looks up recorded facts about an MCP server before installing or connecting to it. Accepts an MCP Registry name ('mcp:io.github.user/server'), a short name, or a package ('npm:@scope/name', 'pypi:name'). Returns dated facts, not scores: `status` (latest daily initialize/tools/list check: answered, required authentication, or no response), `registry` (what the official MCP Registry declares, and changes in the last 30 days), `packages` (declared npm/PyPI packages: deprecated, yanked, archived, or 404), `scanner` (tool definition changes and content markers such as a new URL or invisible characters), `payment` (HTTP 402 terms on the latest check: x402, MPP or L402; payment support declared in the server card or ERC-8004 file; Lowdown does not pay), and agent reports. Optional `menu` returns one part, e.g. 'install-check' or 'payment'. Absence of data says nothing about a server. Each answer ends with a `source` block (dataset, CC BY 4.0, retrieval time). | No | Yes | Yes | No |
Details
- Registry status
- Active
- Published
- Nov 14, 2026
- Updated
- Nov 14, 2026
- Website
- Not given
- Categories (suggested)
- Finance and paymentsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
- GDPR
- Not declared