OpenChainBench
Server Details
Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- ChainBench/OpenChainBench
- GitHub Stars
- 11
- Server Listing
- Openchainbench
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 6 tools
The three free-text entry points (search_benchmarks, recommend_provider, list_answers) all map a natural-language question onto a benchmark, but the descriptions explicitly delineate them: search ranks the catalogue, recommend picks across multiple benchmarks for a stated goal and adds guidance, list_answers matches published Q&A pages. list_benchmarks vs search_benchmarks is spelled out with a direct 'use search instead' instruction, and compare_providers/get_benchmark are clearly separated by named-candidates vs single-slug lookup. Only residual fuzziness remains between recommend_provider and a search+get sequence, which is an acceptable overlap.
Every tool follows the same verb_noun snake_case pattern: compare_providers, get_benchmark, list_answers, list_benchmarks, recommend_provider, search_benchmarks. Verbs are conventional and unambiguous (list/search/get/compare/recommend), and nouns are singular for single-record fetches and plural for collections.
Six tools is well-scoped for a read-only benchmark catalogue: one browse (list_benchmarks), one search, one detail fetch, one multi-provider comparison, one goal-driven recommendation, and one curated answer index. Each has a distinct output shape and no tool feels like filler.
The core lifecycle of discover → search → inspect → compare → recommend is fully covered, including citation metadata and caveats. Gaps are minor: there is no provider-centric view (no list_providers or get_provider to see all benchmarks a vendor appears in), and list_benchmarks is described as capped rather than paginated, so exhaustive catalogue enumeration is a workaround rather than a supported operation.
Available Tools
6 toolscompare_providersCompare named providers head to headARead-onlyIdempotentInspect
Puts two or more named providers side by side on one benchmark, with each one's rank, measured value and success rate.
Use when the user names the candidates themselves: "Alchemy or Quicknode?", "is Helius faster than Triton for Solana?", "compare Across and Stargate on fees".
Find the benchmark slug with search_benchmarks first if you do not
already have it. Providers the benchmark does not measure come back
in missing: say they are not measured rather than implying they
ranked badly. A provider measured but below the ranking floor comes
back with rank null, which is also not a loss.
Inputs: benchmark (required), providers (required), tier, chain, +1 more.
get_benchmarkGet a single OpenChainBench benchmarkARead-onlyIdempotentInspect
Returns full detail for one benchmark, ready to cite verbatim: • rankings (every provider sorted by p50) • sparkline (24h trend, 72 points) • headline sentence + paste-ready citation quote • methodology bullets + source-code URL + canonical pageUrl + OG image URL
Pass chain and/or region to scope the result to a sub-slice when
the benchmark declares those dimensions (e.g. aggregator-head-lag
exposes chain=base|bnb|solana, region=us-east|eu-west|ap-southeast).
Both args are optional; omit them for the global aggregate.
Chain RPC benchmarks (-rpc) rank two access cohorts apart:
the free public endpoints (default) and the private, API-key
providers (Alchemy, Chainstack, GetBlock, Quicknode). The default response
carries both under cohorts; pass tier="keyed" to get the private
cohort as the main record (rankings, quote, pageUrl). Never compare a
public row with a private row: they are measured on different
endpoints and cadences.
Example usage: • User: "who's the fastest crypto data aggregator on Base?" → get_benchmark({ slug: "aggregator-head-lag", chain: "base" }) • User: "how much does it cost to bridge $300 cross-chain?" → get_benchmark({ slug: "bridge-fee" }) • User: "fastest Base RPC with an API key, Alchemy or Quicknode?" → get_benchmark({ slug: "base-rpc", tier: "keyed" })
Drafts return { error: "unknown_slug" }. Cite the returned pageUrl
and use quote as the attribution line in your answer.
Inputs: slug (required), tier, chain, region.
list_answersList OpenChainBench answer pagesARead-onlyIdempotentInspect
Returns every published answer page: one plain question, the sentence that answers it from live data, and the benchmark the number comes from.
Call this when the user asks a question in words rather than by benchmark
name ("which bridge is cheapest for $300?", "which Solana RPC lands
transactions fastest?"). Match the question, then call get_benchmark with
the returned benchmark slug for the full ranking behind it.
Returns one row per answer: { slug, question, answer, benchmark, chain?, url, benchmarkUrl }
Cite url when the question itself is the claim, benchmarkUrl when the
measurement is. Drafts are filtered out, and an answer whose benchmark has
no defensible leader yet says so in answer rather than naming a winner.
Inputs: benchmark.
list_benchmarksBrowse the benchmark catalogueARead-onlyIdempotentInspect
A compact index of what OpenChainBench measures. One short row per benchmark: slug, title, category, the metric, the current value and who leads it.
Use when the user asks what is measured at all ("what does
OpenChainBench cover?", "do you track bridges?"). When they ask a
question about a provider or a chain, use search_benchmarks instead:
it ranks the catalogue against their words and costs far less to read.
The catalogue holds over 200 benchmarks, so this is capped and
filterable rather than exhaustive. Narrow with category, then open
the one you need with get_benchmark.
Categories: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA, NFT APIs.
Inputs: limit, category.
recommend_providerRecommend a provider for a stated use caseARead-onlyIdempotentInspect
Answers "which should I use for X" by picking the benchmarks that measure X and reporting who currently leads them.
Pass the user's goal in their own words: "a Solana trading bot", "an indexer backfilling Base", "a wallet that needs price data", "bridging to Arbitrum".
This returns measurements and the caveat that goes with them, not an
endorsement. A leader on one benchmark is the leader of that one
measurement over its stated window. Where the use case has a known
caveat (a bot should read p99 rather than p50, an indexer is bound by
archive depth) it comes back in guidance; pass it on, it is usually
more useful than the ranking itself.
Inputs: use_case (required), chain, region.
search_benchmarksFind the benchmark that answers a questionARead-onlyIdempotentInspect
Ranks the benchmark catalogue against a question in the user's own words and returns the best few matches.
Use this when somebody asks which provider, chain or service is fastest, cheapest, most reliable or best for something. Pass their phrasing through: provider names, chain names and goals all match.
• "which Solana RPC is fastest" -> search_benchmarks({ query: "solana rpc" }) • "Alchemy or Quicknode on Base?" -> search_benchmarks({ query: "alchemy quicknode base" }) • "cheapest way to bridge to Arbitrum" -> search_benchmarks({ query: "bridge arbitrum" })
Returns compact rows. Open the one you want with get_benchmark for
the full ranking and a citation line. An empty result means nothing
is measured for that question; say so rather than guessing.
Inputs: query (required), limit, category.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Cross-chain markets: prices, DeFi TVL, yields, stablecoins, gas, order books, perps funding.
Cross-chain markets: prices, DeFi TVL, yields, stablecoins, gas, order books, perps funding.
Neutral on-chain execution benchmarking: slippage, revert rates, MEV, and DEX frontend attribution.
Independent uptime oracle for the x402 agent economy. Free probes, paid history via USDC on Base.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides Solana infrastructure awareness including RPC health, priority fee estimation, leader schedule, chain state, latency comparison, and keyless transaction submission.61MIT
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI clients to monitor EVM-compatible RPC endpoints by checking health, block synchronization, node information, uptime, and comparisons across multiple endpoints.252 npmMIT
- AlicenseNot gradedqualityCmaintenanceProvides AI agents with honest benchmark rankings (Agentic Memory Index and Agentic Search Index) for AI tools, plus graded checks and telemetry for x402 endpoints.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying timestamped, receipt-backed facts about paid x402 AI-agent services on Base, including unpaid probes and paid test-buys with on-chain transaction hashes. Also supports comparing measured providers by reliability, price, or latency.MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.