Model Context Protocol (MCP) server for freee API integration
Nothing to run from here
OpenChainBench is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
6
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Live, neutral benchmarks for public RPC latency, oracles, bridges, perp DEX, and prediction markets.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http openchainbench-mcp https://openchainbench.com/api/mcp/mcp
# 2 — ask your agent for something these tools do
# list_benchmarks, search_benchmarks, get_benchmark and 3 more
OpenChainBench costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FLAll 1 server
Flotapponnier1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http openchainbench-mcp https://openchainbench.com/api/mcp/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 f
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | no | Only this category: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA or NFT APIs. |
| limit | integer | no | How many rows to return, 1 to 50. Default 25. |
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" }) • "Alc
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The user's question or keywords, verbatim. Provider and chain names work well. |
| category | string | no | Optional category filter: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA, NFT APIs. |
| limit | integer | no | How many matches, 1 to 25. Default 8. |
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-h
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Benchmark slug from list_benchmarks. e.g. 'aggregator-head-lag', 'bridge-quote-latency', 'l1-finality'. |
| chain | string | no | Optional chain filter, e.g. 'base', 'solana', 'bnb'. Only honored when the bench declares chain dimensions. |
| region | string | no | Optional region filter, e.g. 'us-east', 'eu-west', 'ap-southeast'. Only honored when the bench declares region dimensions. |
| tier | string | no | Optional access cohort on chain RPC benchmarks: 'public' (default, free no-key endpoints) or 'keyed' (private, API-key providers). Only honored when the bench declares tier dimensions. |
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 m
| Parameter | Type | Required | Notes |
|---|---|---|---|
| benchmark | string | yes | Benchmark slug, e.g. 'solana-rpc' or 'bridge-fee'. Get it from search_benchmarks. |
| providers | array | yes | Two to ten provider names or slugs, as the user said them, e.g. ['Alchemy', 'QuickNode']. |
| chain | string | no | Optional chain slice when the bench declares chains. Ignored on a bench that is already one chain, like solana-rpc. |
| region | string | no | Optional region slice when the bench declares regions. |
| tier | string | no | Access cohort on chain RPC benchmarks: 'public' (default, free no-key endpoints) or 'keyed' (API-key providers such as Alchemy, QuickNode, Chainstack, GetBlock). Named providers usually live on the ke |
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 tha
| Parameter | Type | Required | Notes |
|---|---|---|---|
| use_case | string | yes | What the user is building or doing, in their words. e.g. 'solana trading bot', 'indexer', 'price feed for a wallet'. |
| chain | string | no | Chain they are building on, e.g. 'solana', 'base', 'arbitrum'. Narrows the benchmarks considerably. |
| region | string | no | Optional region, e.g. 'eu-west', when latency from a location matters. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| benchmark | string | no | Optional benchmark slug filter: return only the answers built on that bench. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install OpenChainBench or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish OpenChainBench can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.