Chainstack

Reliability

Status and outage history · Atom feed · Watch with other listings

How to connect

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "chainstack": {
      "type": "http",
      "url": "https://mcp.chainstack.com/mcp"
    }
  }
}

23 tools

• 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 deploying — region cannot be changed after deployment.

• 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's a support case: offer contact_chainstack.

• 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 which Origin headers it accepts. With both kinds active, a request must pass both…

• 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 calls the node. Activating the first origin rule blocks every request without…

• 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 requests from any IP and origin.

• 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 Origin headers it accepts, and a request must pass both kinds. Others get HTTP…

• 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 problem, or reach Chainstack for any reason. Posts to the same contact form as…

• 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 above the cap, the call fails with an insufficient-balance error. Describe the…

• 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 pricing (Unlimited Node flat-fee tiers, Yellowstone gRPC streams, Warp…

Security scan

Recent checks