Nodeflare
https://mcp.nodeflare.app/mcp ↗
Description
Read on-chain data across 23 EVM chains — Ethereum, Base, Arbitrum, Optimism, BNB, plus young chains like Robinhood, Plasma and Ink — from an independent provider running its own nodes. Tools for balances, tokens, transactions, event logs and gas, with flexible chain input (slug, name, or chain ID). Free anonymous tier, no API key. Guided recipes included as MCP prompts.
What our measurements say
Nodeflare is a remote MCP server published at mcp.nodeflare.app. It has been probed 6 times since 9/10/2026. It answered in 6 of them (100.0%), a near-uninterrupted record. Median response time is 735 ms, a delay an agent will notice. It exposes a broad tool surface of 19 tools. On the protocol side it still runs 2025-11-25 and has not moved to the newer spec.
Agent readability score
Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.
Agent readability score
Strengths
- Tool names are generally descriptive and indicate their purpose clearly.
- Some tools include important constraints (e.g., API key requirements, chain limitations).
- Multichain capabilities (e.g., get_multichain_balances) are well-documented.
Weaknesses
- Descriptions occasionally omit specific use cases or context for when tools should be used.
- Parameter definitions in some tools (e.g., 'discover:true') are ambiguous or lack context.
- Error handling and edge cases (e.g., invalid inputs) are not consistently documented across tools.
get_multichain_balances— Description is truncated mid-sentence, making it unclear how token discovery works.get_token_allowances— Description cuts off mid-sentence, obscuring details about revoked approvals.simulate_transaction— Parameter explanation ('debug_traceCall asset-change tracing') is vague and lacks clarity.get_token_price— Limited chain support is mentioned in the description but not explicitly in parameters.
Verdict
Event narrative
Risk: medium
- 2026-09-10T21:16:35.016Z — era changed from auth-gated to legacy · indicates a shift in server configuration or access control
- 2026-09-11T05:44:28.819Z — complianceScore increased from null to 100 · suggests improved system adherence to compliance standards
Advice
Schema compliance
tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.
- tools/list schema valid
- inputSchema is valid JSON Schema
- Smoke test not run this round
- Cold-start: cold 40ms → warm 40ms (penalty 0ms)
Availability history
Event log
Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.
- Server build: — → 0.7.0
- Supported versions: — → 2025-11-25
- Era changed: Auth-gated → Legacy
- Added to watch — era: Auth-gated
Get your badge
Add this badge to your README — it updates automatically as measurements change.
[](https://mcpmetrics.io/servers/info-f7wb-nodeflare)<a href="https://mcpmetrics.io/servers/info-f7wb-nodeflare"><img src="https://mcpmetrics.io/badge/info-f7wb/nodeflare/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