Skip to content
External endpointresponds

Chainstack

Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.

Endpoint URL
https://mcp.chainstack.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
302 ms
Response record
1 of 1 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.chainstack/chainstack

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Chainstack
Version
1.10.10
Capability keys
experimental, prompts, resources, tools, extensions
Tool names
get_organization, get_deployment_options, list_projects, create_project, list_nodes, get_node, create_node, get_project, update_project, delete_project, update_node, delete_node, search_docs, get_doc_page, get_platform_status, contact_chainstack, request_testnet_funds, get_chainstack_pricing
Instructions excerpt

Chainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team. Key behaviors: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - When the user asks about a protocol's features or RPC methods, SEARCH DOCS first — Chainstack has per-protocol guides covering configuration, supported methods, and node setup. - Some Chainstack features are not available through the API but are self-serve in the console: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on (flat-fee RPS tiers). If the user asks about these, point them to https://console.chainstack.com. - If the user needs testnet funds for development, use request_testnet_funds. The faucet tops the address up to the per-network cap (it doesn't send a fixed amount). - If the user wants custom node confi

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 302ms