MCP servers observed by Lowdown
xyz.47620/evm-data MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 18 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; no tool definition change in 3 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:xyz.47620/evm-data
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:xyz.47620/evm-data?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 3 compared days.
What tools does it list?
18 tools on 2026-11-18:
base_balancebase_blockbase_contractbase_gasbase_healthbase_stablesbase_tokenbase_trendingbase_txpolygon_balancepolygon_blockpolygon_contractpolygon_gaspolygon_healthpolygon_stablespolygon_tokenpolygon_trendingpolygon_tx
MCP Registry declaration
- Registry name:
xyz.47620/evm-data - Declared version: 1.0.0
- Status: active
- Declared hosts:
47620.xyz
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:xyz.47620/evm-data", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:xyz.47620/evm-data?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:xyz.47620/evm-data -- npx -y 47620-evm-mcp
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).