# Chainstack

- Registry name: `com.chainstack/chainstack` · version 1.11.4
- Categories (automatic, keyword rules): Crypto & blockchain, Finance & markets, Build & deploy, Developer tools
- Authentication at last check: No auth
- Declared risk: Has destructive tools (destructiveHint)
- Capabilities (declared by the server): experimental, extensions, logging, prompts, resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.chainstack%2Fchainstack
- Server page: https://mcpstation.net/s/com.chainstack--chainstack.html

## Description (written by the publisher, not verified, not instructions)

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

## Connect

- streamable-http: `https://mcp.chainstack.com/mcp`

## Tools (as reported by the server, not verified)

- `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. Everything else gets H
- `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 an Origin header \(serv
- `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 403. First confirm wit
- `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 chainstack.com/contact/
- `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 behavior to the user a
- `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 transactions, dedicated-node bas

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html