# Chainstack > Chainstack, an MCP server by chainstack.com, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. - Canonical: https://www.anchorterminal.com/tools/chainstack - Markdown: https://www.anchorterminal.com/tools/chainstack.md (~1,650 tokens) - Slim: https://www.anchorterminal.com/tools/chainstack.min.md (~1,580 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/chainstack.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-04 # Chainstack > Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/ - Kind: MCP server, by chainstack.com (https://docs.chainstack.com/docs/chainstack-mcp-server) - Category: Cloud & infrastructure (https://www.anchorterminal.com/categories/infrastructure.md) - Listed because: It's published in the registry under chainstack.com, a namespace the registry only gives to whoever proves they control that domain. - What the official MCP registry says: Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds. ## Facts - MCP registry: `com.chainstack/chainstack` 1.10.10 - Endpoint: https://mcp.chainstack.com/mcp (streamable HTTP) - Source: https://github.com/chainstacklabs/mcp-server - Website: https://docs.chainstack.com/docs/chainstack-mcp-server - GitHub stars: 4 - Registry entry updated: 2026-08-11 ## Tools - Tools it lists (18, about 5,854 tokens of context, `tools/list` without credentials over MCP 2025-11-25, checked 2026-10-03 22:15 UTC): - `get_organization` (read-only): Get organization name and ID. - `get_deployment_options` (read-only): List blockchain/cloud/network combinations for node deployment. Call before create_node to get valid blockchain and cloud IDs. - `list_projects` (read-only): List all projects. Projects are containers for nodes. - `create_project` (writes): Create a new project. Args: name: Project name. description: Optional description. - `list_nodes` (read-only): List nodes with status and connection endpoints. Args: project_id: Optional project ID to filter by (e.g., PR-123-456-789). If omitted, returns all nodes in… - `get_node` (read-only): Get a node's full details including endpoints and cloud info. Args: node_id: Node ID (e.g., ND-123-456-789). - `create_node` (writes): 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… - `get_project` (read-only): Get project details. Args: project_id: Project ID (e.g., PR-123-456-789). - `update_project` (writes): Update a project's name or description. Args: project_id: Project ID (e.g., PR-123-456-789). name: New name. description: New description. - `delete_project` (writes): Delete a project (irreversible). Args: project_id: Project ID (e.g., PR-123-456-789). - `update_node` (writes): Rename a node. Args: node_id: Node ID (e.g., ND-123-456-789). name: New name. - `delete_node` (writes): Delete a node (irreversible). Args: node_id: Node ID (e.g., ND-123-456-789). - `search_docs` (read-only): Search Chainstack docs — blockchain RPC methods, node infrastructure, Web3 APIs, deployment guides, and code examples. Args: query: Search query (e.g., "deploy… - `get_doc_page` (read-only): Get the full content of a Chainstack documentation page. Use after search_docs to fetch the complete page when a snippet isn't enough. Args: page: Page path… - `get_platform_status` (read-only): Check platform status, active incidents, and maintenances. Args: network: Optional filter (e.g., "ethereum"). Without it, returns overall status and incidents… - `contact_chainstack` (writes): 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… - `request_testnet_funds` (writes): 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… - `get_chainstack_pricing` (read-only): Fetch Chainstack's public pricing and return a normalized snapshot. Use this to answer pricing questions before quoting the user: plan fit, overage math,… - How its tools read to an agent (0 errors, 2 warnings, 14 notes, about 5,854 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score): - warn TC07 contact_chainstack: the description is about 856 tokens - warn TC07 get_chainstack_pricing: the description is about 702 tokens - note TC11 contact_chainstack: parameters are documented in the description but not in the schema: category, email, message, name - note TC11 create_node: parameters are documented in the description but not in the schema: blockchain, cloud, name, project - note TC11 create_project: parameters are documented in the description but not in the schema: description, name - note TC11 delete_node: a parameter is documented in the description but not in the schema: node_id - note TC11 delete_project: a parameter is documented in the description but not in the schema: project_id - note TC11 get_doc_page: a parameter is documented in the description but not in the schema: page - note TC11 get_node: a parameter is documented in the description but not in the schema: node_id - note TC11 get_platform_status: a parameter is documented in the description but not in the schema: network - note TC11 get_project: a parameter is documented in the description but not in the schema: project_id - note TC11 list_nodes: a parameter is documented in the description but not in the schema: project_id - note TC11 request_testnet_funds: a parameter is documented in the description but not in the schema: address - note TC11 search_docs: a parameter is documented in the description but not in the schema: query - note TC11 update_node: parameters are documented in the description but not in the schema: name, node_id - note TC11 update_project: parameters are documented in the description but not in the schema: description, name, project_id - JSON: https://www.anchorterminal.com/api/v1/tools/chainstack.json - Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming