Sato Hub
MCP

Chainstack MCP

Official remote Streamable HTTP MCP: Chainstack docs search, platform status, live pricing, and node deployment.

  • Sato Score64
  • ChainsMultichain
ActiveSelf-Reported

Chainstack MCP is a closed-source MCP server by Chainstack, with no code activity tracked. Sato Score 64/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 Chainstack MCP →

No code activity tracked

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

Affiliate link — Sato Hub may earn a referral if you sign up. It does not change this listing's ranking or its Sato Score.

Next step

Watch Chainstack 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.chainstack.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

Chainstack runs a remote, Streamable HTTP MCP server requiring no local install. Public tools (no auth) cover documentation search for RPC methods and deployment guides, platform status/incident tracking, and live pricing lookups. Authenticated tools (API key) add project management and blockchain node deployment/configuration across multiple chains, plus testnet faucet requests. Works with Claude Code, Cursor, Codex, and other MCP clients.

Sato Score

64/100· Medium

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

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

Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).

Evidence — listed vs checked · what the words mean

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

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.chainstack.comas of 2026-10-15
Verification statusSelf-Reported — not independently reviewedself-reporteddocs.chainstack.comas of 2026-10-15
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reporteddocs.chainstack.comas of 2026-09-14
MCP endpoint answersanswered — 23 tools listedobservedmcp.chainstack.com2026-10-15
Daily check record89 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Works withClaude Code, Cursor, Codex, Windsurf, Gemini CLI, GitHub Copilot, Antigravity, …confidence 0.85self-reporteddocs.chainstack.comas of 2026-07-14
Sato Score64/100 (Medium)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 — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: Hosted MCP endpoint (no local install); optional skill-file mode

mkdir -p ~/.claude/skills/chainstack
curl -o ~/.claude/skills/chainstack/SKILL.md https://mcp.chainstack.com/skill
{"mcpServers": {"chainstack": {"url": "https://mcp.chainstack.com/mcp", "transport": "streamable-http", "headers": {"Authorization": "Bearer YOUR_API_KEY"}}}}

You supply: CHAINSTACK_API_KEY optional (most tools work without credentials; deployment/project management needs a key from console.chainstack.com/user/settings/api-keys)

Add to CursorAdd to VS Code
claude mcp add --transport http satohub-chainstack-mcp https://mcp.chainstack.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-09-14. What a deploy spec is →

Tool inventory — 23 tools, probed live 2026-10-15

  • get_organization — Get organization name and ID.
  • get_deployment_options — List blockchain/cloud/network combinations for node deployment. Call before create_node to get valid blockchain and cloud IDs.
  • list_projects — List all projects. Projects are containers for nodes.
  • create_project — Create a new project.
  • list_nodes — List nodes with status and connection endpoints.
  • get_node — Get a node's full details including endpoints and cloud info.
  • create_node — Deploy a new blockchain node. Call get_deployment_options first for valid IDs. Trader nodes are region-bound (e.g., London, Ashburn, Singapore). Always confirm the region with the user before deployi
  • get_project — Get project details.
  • update_project — Update a project's name or description.
  • delete_project — Delete a project (irreversible).
  • update_node — Rename a node.
  • delete_node — Delete a node (irreversible).
  • list_node_access_rules — List a node's access rules (IP and Origin allowlists, Global nodes only). With no active rules, the node accepts requests from any IP and origin. If correctly configured rules still return 403, that'
  • create_node_access_rule — Add an IP or Origin allowlist rule to a Global node. New rules are deactivated and do nothing until activated. Active IP rules limit which client IPs can call the node; active origin rules limit whic
  • update_node_access_rule — Change an access rule's value, or activate or deactivate it. A rule's type can't change; delete it and create a new one. Before activating, confirm with the user that the IP rules cover every IP that
  • delete_node_access_rule — Delete an access rule from a node (irreversible). Deleting an active rule changes who can reach the node; the result says what's enforced afterwards. With no active rules left, the node accepts reque
  • set_node_access_rules_status — Activate or deactivate every access rule on a node at once. Activating enforces every rule within about 10 seconds: active IP rules limit which IPs can call the node, active origin rules limit which
  • search_docs — Search Chainstack docs — blockchain RPC methods, node infrastructure, Web3 APIs, deployment guides, and code examples.
  • get_doc_page — Get the full content of a Chainstack documentation page. Use after search_docs to fetch the complete page when a snippet isn't enough.
  • get_platform_status — Check platform status, active incidents, and maintenances.
  • contact_chainstack — Submit a message to Chainstack's sales and support team. Use when the user wants to ask about pricing, get a custom quote, request a plan upgrade, request node customizations (Enterprise), report a p
  • request_testnet_funds — Top up a testnet address from Chainstack's faucet. The faucet does not send a fixed amount — it tops the address up to the per-network maximum (e.g. 0.5 ETH for sepolia). If the address already sits
  • get_chainstack_pricing — Fetch Chainstack's public pricing and return a normalized snapshot. Use this to answer pricing questions before quoting the user: plan fit, overage math, per-chain dedicated-node costs, and add-on pr
Answers a handshake
yes · 2026-10-15
Answers a call
the server answered get_organization with an error (Error calling tool 'get_organization': No API key provided. Fetch https://mcp.chainstack.com/ (GET) for connection config with API key setup. The user needs a C)

Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.

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

98.9%of 91 checks since 2026-07-17 succeeded
Currently responding for 13 days
Succeeded
90
Failed
1
Their error
0
Unattributed
1

State changed on 2026-10-02 (responding → unreachable from our probe), 2026-10-03 (unreachable from our probe → responding).

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. Every one of them passed, so the rate covers them too.

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

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
23
from the server's own tools/list · 29/30 days
Sato Score
64
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.

Tool inventory history — 23 now, peak 23, since 2026-07-19

  • 2026-10-12 18 → 23 +5 (create_node_access_rule, delete_node_access_rule, list_node_access_rules, set_node_access_rules_status…)
  • 2026-09-23 0 → 18 +18 (contact_chainstack, create_node, create_project, delete_node…)

Recorded from our own daily tools/list handshake. A shrinking toolset is a real signal for an agent choosing a server; a gap in the series means the probe did not succeed that day, not that the tools disappeared.

Details

Chains
Multichain
Agent types
MCP Server, Infrastructure
Open source
No
Pricing
Tiered platform plans; see console.chainstack.com
Works with
Claude Code, Cursor, Codex, Windsurf, Gemini CLI, GitHub Copilot, Antigravity, Claude.ai +1
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#node-deployment#docs-search#hosted-mcp#devops
See something inaccurate or outdated?Submit a correction →

Listing History

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

  1. Oct 3, 2026
    Sato Score tier: Low → Medium
    Score 38 → 64.
  2. Oct 2, 2026
    Sato Score tier: Medium → Low
    Score 65 → 38.
  3. Sep 19, 2026
    Edited: referral url
  4. Jul 20, 2026
    Edited: mcp endpoint url
  5. Jul 20, 2026
    Edited: deploy spec
  6. Jul 19, 2026
    Edited: mcp endpoint url
  7. Jul 18, 2026
    Sato Hub began tracking this listing
  8. Jul 14, 2026
    Auto-enriched: supported integrations
  9. Jul 13, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Chainstack MCP

Is Chainstack MCP open source?
No. Chainstack MCP is closed source as of 2026-10-15.
Which chains does Chainstack MCP support?
Chainstack MCP lists support for Multichain as of 2026-10-15.
Is Chainstack MCP still maintained?
Sato Hub tracks no commit or release for Chainstack MCP; it cannot say whether it is maintained.
How do I install or run Chainstack MCP?
Hosted MCP endpoint (no local install); optional skill-file mode. Install: mkdir -p ~/.claude/skills/chainstack && curl -o ~/.claude/skills/chainstack/SKILL.md https://mcp.chainstack.com/skill. Entry: {"mcpServers": {"chainstack": {"url": "https://mcp.chainstack.com/mcp", "transport": "streamable-http", "headers": {"Authorization": "Bearer YOUR_API_KEY"}}}}. 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.chainstack.com/mcp (Streamable HTTP)).
Is Chainstack MCP verified on Sato Hub?
Sato Hub holds one earned check for Chainstack MCP: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 64 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Chainstack MCP — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/chainstack-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.