Sato Hub
MCP

QuickNode MCP

Official remote MCP for managing QuickNode blockchain endpoints, rate limits, security, and billing via natural language.

  • Sato Score35
  • ChainsMultichain
ActiveSelf-Reported

QuickNode MCP is a closed-source MCP server by QuickNode, with no code activity tracked. Sato Score 35/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install QuickNode MCP →

No code activity tracked

Listed from quicknode.com on 2026-07-12. Install: not attempted. Evidence →

Next step

Watch QuickNode MCP

One email if what we observe changes — its endpoint stops answering, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on https://mcp.quicknode.com/mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

QuickNode's official remote MCP server at mcp.quicknode.com/mcp lets an AI agent manage blockchain RPC infrastructure: create/list/delete endpoints, configure rate limits and IP allowlists, monitor usage and billing, and query supported chains. Authentication is OAuth 2.1 with role-based access (Admin for read/write, Viewer for read-only); API keys can be passed as bearer tokens for non-interactive environments. It's an infrastructure-management surface, not a data-query MCP.

Sato Score

35/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
8/35
Code transparency
0/20
Interface verifiability
8/10
Docs & demo
6/10
Listing transparency & provenance
11/15
Independent verification
2/10

Evidence — listed vs checked · what the words mean

Listed from quicknode.com on 2026-07-12. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reportedquicknode.comas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reportedquicknode.comas of 2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted by Sato Hubself-reportedquicknode.comas of 2026-07-20
MCP endpoint answersanswered, but declined an anonymous probeobservedmcp.quicknode.com2026-10-15
Daily check record0 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
ERC-8004 registrationdeclared address not found in the registryobserved—2026-09-19
Deploys asHosted API (remote MCP over OAuth), API key (CI/CD, non-interactive)confidence 0.90self-reportedquicknode.comas of 2026-07-14
Works withChatGPT, Codex, Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zedconfidence 0.90self-reportedquicknode.comas of 2026-07-14
Sato Score35/100 (Low)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — as documented by the project, not run by us

Runtime: Hosted MCP endpoint (no local install)

claude mcp add --transport http quicknode https://mcp.quicknode.com/mcp
claude mcp add quicknode --transport http https://mcp.quicknode.com/mcp --header "Authorization: Bearer YOUR_API_KEY"
{"mcpServers": {"quicknode": {"url": "https://mcp.quicknode.com/mcp"}}}

You supply: QuickNode account; OAuth 2.1 browser login on first connection, or API key as Authorization: Bearer header (Dashboard > Account > API Keys)

Add to CursorAdd to VS Code
claude mcp add --transport http satohub-quicknode-mcp https://mcp.quicknode.com/mcp

A remote server: your client connects to the project's endpoint. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-07-20. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

0%of 45 checks since 2026-09-01 succeeded
Currently unreachable from our probe for 23 days
Succeeded
2
Failed
89
Their error
22
Unattributed
67

State changed on 2026-07-19 (responding → unclear), 2026-09-01 (unclear → failing), 2026-09-23 (failing → unreachable from our probe).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
0%
7-day rolling; unattributable days are gaps · 13/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
35
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
MCP Server, Infrastructure
Open source
No
Deploys as
Hosted API (remote MCP over OAuth), API key (CI/CD, non-interactive)
Works with
ChatGPT, Codex, Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#rpc#endpoint-management#oauth#hosted-mcp#devops
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to QuickNode MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Jul 20, 2026
    Edited: mcp endpoint url
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Edited: mcp endpoint url
  4. Jul 19, 2026
    Sato Score tier: Medium → Low
    Score 44 → 32.
  5. Jul 18, 2026
    Sato Hub began tracking this listing
  6. Jul 14, 2026
    Auto-enriched: deployment options, supported integrations
  7. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about QuickNode MCP

Is QuickNode MCP open source?
No. QuickNode MCP is closed source as of 2026-10-15.
Which chains does QuickNode MCP support?
QuickNode MCP lists support for Multichain as of 2026-10-15.
Is QuickNode MCP still maintained?
Sato Hub tracks no commit or release for QuickNode MCP; it cannot say whether it is maintained.
How do I install or run QuickNode MCP?
Hosted MCP endpoint (no local install). Install: claude mcp add --transport http quicknode https://mcp.quicknode.com/mcp && claude mcp add quicknode --transport http https://mcp.quicknode.com/mcp --header "Authorization: Bearer YOUR_API_KEY". Entry: {"mcpServers": {"quicknode": {"url": "https://mcp.quicknode.com/mcp"}}}. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (https://mcp.quicknode.com/mcp (Streamable HTTP)).
Is QuickNode MCP verified on Sato Hub?
No independent verification is on record for QuickNode MCP; its verification status is "Self-Reported" and its Sato Score is 35 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "QuickNode MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/quicknode-mcp

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.