MCP.Market

Quicknode MCP server

online · 100% uptime
by quicknode·io.github.quicknode/mcp·v1.0.1·5 stars
No reviews yet

Manage your blockchain infrastructure across 80+ chains with your agents.

A85/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A85/100

full report

Adoption
Growing

5 stars

Reviews

Write one

Nobody has reviewed Quicknode yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Quicknode tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 47ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityauth enforced (bearer)9/15
  • Maintenancelast push 20 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Quicknode compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
85/100
higher than 70% of 48,255 servers
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
321 ms
faster than 45% of 30,031 servers
GitHub stars
5
more than 83% of 28,688 servers

Install Quicknode in Claude Code, Cursor or VS Code

claude mcp add --transport http mcp https://mcp.quicknode.com/mcp
Add to Cursor

What the publisher says

From the Quicknode repository's README, as published. We do not edit it. Read it on GitHub

Quicknode Agent Plugins

Agent plugins from Quicknode for building Web3 apps with AI agents.

Available plugins

Install

For Claude Code, add this marketplace and install the build-web3 plugin:

/plugin marketplace add quicknode/agent-plugins

For Codex, see the Codex install guide. Codex discovers this repository's plugin through .agents/plugins/marketplace.json and uses plugins/build-web3/.codex-plugin/plugin.json to load the bundled skill and MCP server.

For ChatGPT, use the existing listing on its marketplace.

Content rules

Plugin skills and references in this repo should stay stable, useful, and self-contained:

  • Stable concepts, product categories, capability names, and decision guidance belong in this repo so the plugin works without a network round-trip.
  • Perishable facts — plan tiers, pricing, rate-limit numbers, RPC method tables, schemas — are allowed when the repo needs to be self-sufficient for a product, but every such table must carry a dated snapshot note (e.g. "As of 2026-02-02.") and a link to the live docs (https://www.quicknode.com/docs/) so a reader knows it can drift and where to check.
  • Keep dated content current using plugins/build-web3/skills/build-web3/PRODUCT_CATALOG.md's sync runbook — it's the maintenance source of truth for which product references exist, where they live, and how to refresh them.

License

MIT. See LICENSE.md.

Nothing above is checked by us. What we check is on the safety report.

Quicknode: common questions

Is Quicknode MCP server safe?
Yes, by our scan: it is graded A (85/100). Read the Quicknode safety report
How do I install Quicknode?
It runs remotely at mcp.quicknode.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Quicknode need an API key?
Yes. The endpoint refuses requests without credentials; the publisher's docs say how to get them.
Is Quicknode maintained?
The last commit was 61 days ago (2026-09-04). The latest release is v1.0.1.
Is Quicknode up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Quicknode compare with other MCP servers?
safety score 85/100 (higher than 70% of 48,255 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 321 ms (faster than 45% of 30,031 servers). Full comparison.