mcp server
OpenChainBench
Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets.
Description as published by the maintainer. Source
- version 1.0.0
- active
- evaluation
active — Most recent push to the repository was 2026-08-08. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
3 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
get_benchmark(slug, chain, region)- 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. 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" }) Drafts return { error: "unknown_slug" }. Cite the returned `pageUrl` and use `quote` as the attribution line in your answer. Required: slug.
list_benchmarks- Returns a flat index of every published OpenChainBench benchmark with its current headline value, leader, category, units, and citation URL. Call this first when the user asks a discovery question like "what benchmarks does OpenChainBench have?" or "compare crypto aggregators". Then use `get_benchmark` for the specific slug(s) the answer needs. Returns one line per bench: { slug, title, category, metric, unit, value, leader, headline, url, asOf } Drafts are filtered out: only live benchmarks appear.
query_prom(query, steps, windowSec)- Direct PromQL passthrough for advanced questions that don't map cleanly to `list_benchmarks` / `get_benchmark`, e.g. "what was Mobula's p50 head-lag yesterday at 14:00 UTC" or "plot bridge fees over the last hour". Prefer the higher-level tools first; reach for this when you need: • a custom time window (instant query at a specific point, or range) • a derived metric (rates, ratios, deltas) • a histogram bucket aggregation across chains/regions Allowed metric namespaces (one prefix per OCB bench family): head_lag_seconds (aggregator latency) bridge_quote_latency_ms*, bridge_cost*, bridge_fees*, bridge_fix_fee*, bridge_gas*, bridge_output*, bridge_estimated_time*, bridge_quote_success l1_finality_*, l2_block_time_* metadata_coverage_*, metadata_api_latency_*, network_coverage_*, networks_supported, wallet_labels_* perp_fees_*, perp_funding_*, perp_venue_*, perp_execution_*, ocb_buyback_*, ocb_oracle_*, ocb_validator_*, ocb_chain_* gas_error_*, gas_predicted_*, gas_realized_*, gas_oracle_* peg_* (stablecoin peg, both variants) solana_landing_* (TX landing observational + active) rpc_latency_*, rpc_call_total, rpc_health, rpc_archive_depth_supported relay_*, per_swap_margin_usd (bridge revenue) Queries referencing other metrics (operational/internal ones like `up`, `scrape_*`, `process_*`, `go_*`, `wallet_balance_*` or any label- enumeration shape) are refused with `{error, reason}`. Example: instant p50 over 1h for Mobula head-lag on Base: query_prom({ query: "quantile_over_time(0.5, head_lag_seconds{aggregator=\"mobula\",chain=\"base\"}[1h]) * 1000" }) Example: 7-day sparkline of average bridge fees: query_prom({ query: "avg_over_time(bridge_fees_percent[1d])", windowSec: 604800, steps: 168 }) Returns: `{ query, value }` for instant queries, `{ query, windowSec, series }` for range. Required: query.
Last successful function declaration observed on . Source: https://openchainbench.com/api/mcp/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://openchainbench.com/api/mcp/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| GitHub stars | 5 | Number of GitHub accounts that bookmarked this repository since it was created. It is a bookmark count, not installs, not active users and not quality. | cumulative, all time | GitHub | |
| Last commit | 2026-08-08 | Date of the most recent push to any branch. This is the strongest cheap indicator of whether the project is still maintained. | point in time | GitHub | |
| Open issues | 8 | Open issues plus open pull requests, as GitHub counts them together. A high number can mean an active project or an abandoned one. | as of fetch | GitHub | |
| Latest published version | 1.0.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-14 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| License | MIT | Licence GitHub detected in the repository. Detection can be wrong; the LICENSE file is authoritative. | as of fetch | GitHub | |
| First listed in the MCP Registry | 2026-07-14 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| repository status | active | The repository exists on GitHub and is not archived. This says nothing about how recently it was worked on. | as of fetch | GitHub | |
| mcp tools declared | 3 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | openchainbench.com | |
| mcp endpoint status | ok | The server listed 3 functions when asked. | as of probe | openchainbench.com |
Where to get it
Related, by what their authors tagged them
-
ai.explorium/mcp-explorium
— last commit 2026-03-03, shares data
Access live company and contact data from Explorium's AgentSource B2B platform.
-
datoon
— last commit 2026-08-03, shares data
Smart structured-data to TOON gateway: converts to TOON only when it saves LLM tokens.
-
Australian Economic Data (ABS, RBA & APRA)
— last commit 2026-08-05, shares data
Australian economic data from the ABS, RBA, and APRA: CPI, GDP, cash rate, labour, and more.
-
Carbon Arc
— last commit 2026-06-07, shares data
The infrastructure for the AI economy: primitives for inference, agents, and decisions.
-
Scrapling MCP Server
— last commit 2026-08-06, shares data
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
-
FXMacroData
— last commit 2026-07-15, shares data
Macroeconomic and FX time-series data for AI agents: indicators, calendars, COT, forex, commodities.
-
DABLOCK AI Visibility Index
— last commit 2026-08-06, shares benchmark, crypto
Measured share of answer for 24 crypto and Web3 brands. An open dataset, not an audit of your site.
-
DABYTE AI Visibility Index
— last commit 2026-08-06, shares benchmark, crypto
Measured share of answer for 20 SaaS brands. An open dataset, not an audit of your site.
-
dev.llmlatency/llm-latency-tracker
— last commit 2026-07-23, shares benchmark
Measured latency & uptime for AI inference APIs, by region. Exposes a get_ai_api_latency tool.
-
dev.safeprompt/mcp
— last commit 2026-08-03, shares benchmark
Detect prompt injection, jailbreaks, and code injection in untrusted text before it reaches an LLM.
These share tags the maintainers applied themselves, such as data, benchmark, crypto. Common tags like "mcp" or "ai" are ignored for this: agreeing with six hundred other projects is not a similarity.
This is not a recommendation and not a test result. It is a map of what the authors said their work is about.
How the author describes it
Topics the maintainer set on GitHub: api, benchmark, crypto, data, open-source, reproductible.
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json