Deploy and manage blockchain nodes across 70+ protocols, search docs, request testnet funds.
Call this server's tools from your browser. Nothing to install.
Chainstack API key as a Bearer token. Optional — search_docs, get_doc_page, get_platform_status, get_chainstack_pricing and contact_chainstack work without it. Required for the platform tools (projects, nodes, organization, deployment options) and request_testnet_funds.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
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/. ## Before calling this tool CRITICAL — follow these steps EVERY time: 1. Draft the message based on your conversation context. 2. Show the user the EXACT message, email, and name you will send. 3. If the user has a Chainstack API key configured, tell them their org name and ID will be included so the team can find their account and reply faster. 4. Ask: "Shall I send this to Chainstack? Please confirm there's no sensitive information you'd like removed." 5. Only call this tool after the user explicitly confirms. NEVER include in the message: - API keys, tokens, passwords, private keys, wallet seeds, mnemonics - RPC endpoint URLs (Chainstack or any other provider) - Wallet addresses, transaction hashes, on-chain account details, or anything else the user hasn't explicitly approved sharing ## Writing an effective message Include what you know: what they're building and at what scale, current plan and usage, what they need, what they've tried, and specific numbers. Bad: "I have a question about pricing." Good: "Pro plan user running 200M RU/month across Base and Ethereum, evaluating Business plan for archive access and higher RPS. Looking for annual pricing or a trial." Not for incidents or urgent outages — point users to https://support.chainstack.com/hc/en-us/requests/new and https://status.chainstack.com. Not for feature requests — point users to https://ideas.chainstack.com (product) or https://github.com/chainstacklabs/mcp-server/issues/new (MCP server). Works with or without an API key; with one, the org info is attached.
User's name (full name is fine, will be split on first space). Required. Ask the user if you don't have it on hand.
User's contact email. Required. Ask the user if you don't already have it.
The full message to send. Compose from conversation context — what the user is building, their plan and usage, what they need — so the Chainstack team can respond with a tailored answer instead of a generic one.
Routing hint. One of: - sales — pricing, quotes, plan upgrades, custom terms. - support — errors, bugs, how-to, "something isn't working". - general — everything else. Case-insensitive. Unknown values fall back to "general". Default: "general".
The server marks this tool as destructive. Running it may delete or overwrite data on the server or in any account you connected with your headers.
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/. ## Before calling this tool CRITICAL — follow these steps EVERY time: 1. Draft the message based on your conversation context. 2. Show the user the EXACT message, email, and name you will send. 3. If the user has a Chainstack API key configured, tell them their org name and ID will be included so the team can find their account and reply faster. 4. Ask: "Shall I send this to Chainstack? Please confirm there's no sensitive information you'd like removed." 5. Only call this tool after the user explicitly confirms. NEVER include in the message: - API keys, tokens, passwords, private keys, wallet seeds, mnemonics - RPC endpoint URLs (Chainstack or any other provider) - Wallet addresses, transaction hashes, on-chain account details, or anything else the user hasn't explicitly approved sharing ## Writing an effective message Include what you know: what they're building and at what scale, current plan and usage, what they need, what they've tried, and specific numbers. Bad: "I have a question about pricing." Good: "Pro plan user running 200M RU/month across Base and Ethereum, evaluating Business plan for archive access and higher RPS. Looking for annual pricing or a trial." Not for incidents or urgent outages — point users to https://support.chainstack.com/hc/en-us/requests/new and https://status.chainstack.com. Not for feature requests — point users to https://ideas.chainstack.com (product) or https://github.com/chainstacklabs/mcp-server/issues/new (MCP server). Works with or without an API key; with one, the org info is attached.
| Argument | Type | Description |
|---|---|---|
| name* | string | User's name (full name is fine, will be split on first space). Required. Ask the user if you don't have it on hand. |
| email* | string | User's contact email. Required. Ask the user if you don't already have it. |
| message* | string | The full message to send. Compose from conversation context — what the user is building, their plan and usage, what they need — so the Chainstack team can respond with a tailored answer instead of a generic one. |
| category | string | Routing hint. One of: - sales — pricing, quotes, plan upgrades, custom terms. - support — errors, bugs, how-to, "something isn't working". - general — everything else. Case-insensitive. Unknown values fall back to "general". Default: "general". |
{
"type": "object",
"required": [
"message",
"email",
"name"
],
"properties": {
"name": {
"type": "string",
"description": "User's name (full name is fine, will be split on first space).\nRequired. Ask the user if you don't have it on hand."
},
"email": {
"type": "string",
"description": "User's contact email. Required. Ask the user if you don't\nalready have it."
},
"message": {
"type": "string",
"description": "The full message to send. Compose from\nconversation context — what the user is building, their plan\nand usage, what they need — so the Chainstack team can respond\nwith a tailored answer instead of a generic one."
},
"category": {
"type": "string",
"default": "general",
"description": "Routing hint. One of:\n- sales — pricing, quotes, plan upgrades, custom terms.\n- support — errors, bugs, how-to, \"something isn't working\".\n- general — everything else.\nCase-insensitive. Unknown values fall back to \"general\".\nDefault: \"general\"."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| name* | string | Node name. |
| cloud* | string | Cloud ID from get_deployment_options (e.g., CC-0016 for Global; Trader IDs vary by region). |
| project* | string | Project ID from list_projects (e.g., PR-123-456-789). |
| blockchain* | string | Blockchain ID from get_deployment_options (e.g., BC-000-000-008). |
{
"type": "object",
"required": [
"name",
"project",
"blockchain",
"cloud"
],
"properties": {
"name": {
"type": "string",
"description": "Node name."
},
"cloud": {
"type": "string",
"description": "Cloud ID from get_deployment_options (e.g., CC-0016 for Global; Trader IDs vary by region)."
},
"project": {
"type": "string",
"description": "Project ID from list_projects (e.g., PR-123-456-789)."
},
"blockchain": {
"type": "string",
"description": "Blockchain ID from get_deployment_options (e.g., BC-000-000-008)."
}
},
"additionalProperties": false
}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 HTTP 403 within about 10 seconds. Rules don't affect the Chainstack API, so they can always be changed or deactivated with these tools. Before activating, confirm with the user that the IP rules cover every IP that calls the node (servers, CI, their own machine); you can't check this. Origin rules are for browser-only access: once one is active, every request without an Origin header (servers, scripts, curl) is blocked, even from an allowed IP. If an identical rule exists, it is returned instead of a duplicate.
| Argument | Type | Description |
|---|---|---|
| value* | string | For ip, one IPv4 or IPv6 address (no CIDR ranges). For origin, a host name without scheme or path: example.com, *.example.com (the domain and its subdomains), or * (any origin). Up to 65 characters. |
| node_id* | string | Node ID (e.g., ND-123-456-789). |
| activate | boolean | Also activate the rule. Only after the user confirms the allowlist. |
| rule_type* | string | ip or origin. |
{
"type": "object",
"required": [
"node_id",
"rule_type",
"value"
],
"properties": {
"value": {
"type": "string",
"description": "For ip, one IPv4 or IPv6 address (no CIDR ranges). For origin,\na host name without scheme or path: example.com, *.example.com\n(the domain and its subdomains), or * (any origin). Up to 65\ncharacters."
},
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
},
"activate": {
"type": "boolean",
"default": false,
"description": "Also activate the rule. Only after the user confirms the\nallowlist."
},
"rule_type": {
"enum": [
"ip",
"origin"
],
"type": "string",
"description": "ip or origin."
}
},
"additionalProperties": false
}Create a new project.
| Argument | Type | Description |
|---|---|---|
| name* | string | Project name. |
| description | string | Optional description. |
{
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"description": "Project name."
},
"description": {
"type": "string",
"default": "",
"description": "Optional description."
}
},
"additionalProperties": false
}Delete a node (irreversible).
| Argument | Type | Description |
|---|---|---|
| node_id* | string | Node ID (e.g., ND-123-456-789). |
{
"type": "object",
"required": [
"node_id"
],
"properties": {
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| node_id* | string | Node ID (e.g., ND-123-456-789). |
| rule_id* | string | Rule ID from list_node_access_rules (e.g., NAR-123-456-789). |
{
"type": "object",
"required": [
"node_id",
"rule_id"
],
"properties": {
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
},
"rule_id": {
"type": "string",
"description": "Rule ID from list_node_access_rules (e.g., NAR-123-456-789)."
}
},
"additionalProperties": false
}Delete a project (irreversible).
| Argument | Type | Description |
|---|---|---|
| project_id* | string | Project ID (e.g., PR-123-456-789). |
{
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string",
"description": "Project ID (e.g., PR-123-456-789)."
}
},
"additionalProperties": false
}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 base rates). This tool returns the menu, not the bill — the calling agent does the arithmetic. All prices are list prices in USD; disclaimers are surfaced in the `disclaimers` field. Per-method RU billing rules are NOT in these sources. Plan-level rates (Full Node = 1 RU, Archive Node = 2 RU) are in the markdown, but some EVM archive-state methods (eth_getBalance, eth_call, eth_getProof, eth_getStorageAt, eth_getCode, eth_getTransactionCount, eth_callMany, eth_createAccessList) and all debug_* / trace_* methods are billed at 2 RU on a full node when called against old blocks. For method-level detail, call `search_docs` with "request units" or `get_doc_page("docs/request-units")`. No API key required — sources are fully public. Each call fetches both sources fresh (no caching), so a stale result isn't possible. Returns: A dict with fields: - `pricing_markdown`: raw markdown from chainstack.com/pricing.md. Read this for plan tiers, feature matrix, add-on pricing, support levels, PAYG details, and provider comparisons. - `dedicated_catalog`: user-orderable per-chain dedicated-node SKUs with flavor, regions (as infra slugs like "sgp1"), hourly and monthly prices in USD. - `region_legend`: slug → city name for every region slug in `dedicated_catalog`; use it for display. - `disclaimers`: list-price caveats (Enterprise "from" pricing, etc.). - `sources`, `warnings`: per-source status; warnings are set when a source failed and the result is best-effort. - `fetched_at`: UTC timestamp of this call.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}List blockchain/cloud/network combinations for node deployment. Call before create_node to get valid blockchain and cloud IDs.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}Get the full content of a Chainstack documentation page. Use after search_docs to fetch the complete page when a snippet isn't enough.
| Argument | Type | Description |
|---|---|---|
| page* | string | Page path from search results — pass the `page` field from a search_docs result (e.g., "docs/ethereum-trader-nodes"). The leading slash, the `.mdx` extension, and the docs.chainstack.com URL prefix are all optional and stripped if present. |
{
"type": "object",
"required": [
"page"
],
"properties": {
"page": {
"type": "string",
"description": "Page path from search results — pass the `page` field from\n a search_docs result (e.g., \"docs/ethereum-trader-nodes\").\n The leading slash, the `.mdx` extension, and the\n docs.chainstack.com URL prefix are all optional and stripped\n if present."
}
},
"additionalProperties": false
}Get a node's full details including endpoints and cloud info.
| Argument | Type | Description |
|---|---|---|
| node_id* | string | Node ID (e.g., ND-123-456-789). |
{
"type": "object",
"required": [
"node_id"
],
"properties": {
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
}
},
"additionalProperties": false
}Get organization name and ID.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}Check platform status, active incidents, and maintenances.
| Argument | Type | Description |
|---|---|---|
| network | string | Optional filter (e.g., "ethereum"). Without it, returns overall status and incidents only. |
{
"type": "object",
"properties": {
"network": {
"type": "string",
"default": "",
"description": "Optional filter (e.g., \"ethereum\"). Without it, returns\n overall status and incidents only."
}
},
"additionalProperties": false
}Get project details.
| Argument | Type | Description |
|---|---|---|
| project_id* | string | Project ID (e.g., PR-123-456-789). |
{
"type": "object",
"required": [
"project_id"
],
"properties": {
"project_id": {
"type": "string",
"description": "Project ID (e.g., PR-123-456-789)."
}
},
"additionalProperties": false
}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.
| Argument | Type | Description |
|---|---|---|
| status | any | Only return activated or deactivated rules. |
| node_id* | string | Node ID (e.g., ND-123-456-789). |
| rule_type | any | Only return ip or origin rules. |
{
"type": "object",
"required": [
"node_id"
],
"properties": {
"status": {
"anyOf": [
{
"enum": [
"activated",
"deactivated"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Only return activated or deactivated rules."
},
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
},
"rule_type": {
"anyOf": [
{
"enum": [
"ip",
"origin"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "Only return ip or origin rules."
}
},
"additionalProperties": false
}List nodes with status and connection endpoints.
| Argument | Type | Description |
|---|---|---|
| project_id | string | Optional project ID to filter by (e.g., PR-123-456-789). If omitted, returns all nodes in the organization. |
{
"type": "object",
"properties": {
"project_id": {
"type": "string",
"default": "",
"description": "Optional project ID to filter by (e.g., PR-123-456-789).\n If omitted, returns all nodes in the organization."
}
},
"additionalProperties": false
}List all projects. Projects are containers for nodes.
No arguments.
{
"type": "object",
"properties": {},
"additionalProperties": false
}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 as "top up" not "give", and surface the returned `amountSent` so they see the actual delta. One top-up per network every 24 hours: a repeat call for the same network is refused (429) if the same organization or the same address got funds there in the last 24 hours, and the error says when the next top-up is available. Other networks have separate cooldowns. A success is final even if the balance hasn't updated yet; track the returned `transaction` instead of calling again.
| Argument | Type | Description |
|---|---|---|
| address* | string | Destination address. EVM hex address for EVM networks, a TON address for `ton`, or a base58 Solana public key for `solana`. Validated server-side — format errors surface as 400. |
| network* | string | Testnet to fund. Must be one of the canonical ids in `enum`. Common aliases (ethereum-sepolia, base-sepolia, solana-devnet, ...) are accepted and normalized to the canonical id. |
{
"type": "object",
"required": [
"network",
"address"
],
"properties": {
"address": {
"type": "string",
"description": "Destination address. EVM hex address for EVM networks,\na TON address for `ton`, or a base58 Solana public key for\n`solana`. Validated server-side — format errors surface as 400."
},
"network": {
"enum": [
"sepolia",
"hoodi",
"base",
"amoy",
"bnb-testnet",
"zksync-testnet",
"robinhood",
"hyperevm",
"plasma",
"monad",
"ton",
"solana"
],
"type": "string",
"examples": [
"sepolia",
"base",
"solana"
],
"description": "Testnet to fund. Must be one of the canonical ids in `enum`. Common aliases (ethereum-sepolia, base-sepolia, solana-devnet, ...) are accepted and normalized to the canonical id."
}
},
"additionalProperties": false
}Search Chainstack docs — blockchain RPC methods, node infrastructure, Web3 APIs, deployment guides, and code examples.
| Argument | Type | Description |
|---|---|---|
| query* | string | Search query (e.g., "deploy ethereum node", "eth_call"). |
{
"type": "object",
"required": [
"query"
],
"properties": {
"query": {
"type": "string",
"description": "Search query (e.g., \"deploy ethereum node\", \"eth_call\")."
}
},
"additionalProperties": false
}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 with the user that the IP rules cover every IP that calls the node (servers, CI, their own machine); you can't check this. Origin rules block every request without an Origin header (servers, scripts, curl), even from an allowed IP. Deactivating opens the node to any IP and origin.
| Argument | Type | Description |
|---|---|---|
| status* | string | activated or deactivated. |
| node_id* | string | Node ID (e.g., ND-123-456-789). |
{
"type": "object",
"required": [
"node_id",
"status"
],
"properties": {
"status": {
"enum": [
"activated",
"deactivated"
],
"type": "string",
"description": "activated or deactivated."
},
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
}
},
"additionalProperties": false
}Rename a node.
| Argument | Type | Description |
|---|---|---|
| name* | string | New name. |
| node_id* | string | Node ID (e.g., ND-123-456-789). |
{
"type": "object",
"required": [
"node_id",
"name"
],
"properties": {
"name": {
"type": "string",
"description": "New name."
},
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
}
},
"additionalProperties": false
}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 (servers, scripts, curl), even from allowed IPs. Changing or deactivating a rule can block clients that only it allowed.
| Argument | Type | Description |
|---|---|---|
| value | any | New value, in the format the rule's type needs (see create_node_access_rule). |
| status | any | activated or deactivated. |
| node_id* | string | Node ID (e.g., ND-123-456-789). |
| rule_id* | string | Rule ID from list_node_access_rules (e.g., NAR-123-456-789). |
{
"type": "object",
"required": [
"node_id",
"rule_id"
],
"properties": {
"value": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "New value, in the format the rule's type needs (see\ncreate_node_access_rule)."
},
"status": {
"anyOf": [
{
"enum": [
"activated",
"deactivated"
],
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "activated or deactivated."
},
"node_id": {
"type": "string",
"description": "Node ID (e.g., ND-123-456-789)."
},
"rule_id": {
"type": "string",
"description": "Rule ID from list_node_access_rules (e.g., NAR-123-456-789)."
}
},
"additionalProperties": false
}Update a project's name or description.
| Argument | Type | Description |
|---|---|---|
| name | any | New name. |
| project_id* | string | Project ID (e.g., PR-123-456-789). |
| description | any | New description. |
{
"type": "object",
"required": [
"project_id"
],
"properties": {
"name": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "New name."
},
"project_id": {
"type": "string",
"description": "Project ID (e.g., PR-123-456-789)."
},
"description": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"default": null,
"description": "New description."
}
},
"additionalProperties": false
}