Skip to main content
Glama

Server Details

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

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
Repository
chainstacklabs/mcp-server
GitHub Stars
5
Server Listing
Chainstack MCP Server
ChatGPT
–
Claude
–

TDQS

A3.5/5.0

Scored across 23 tools

Disambiguation4/5

Most tools map to distinct resources and actions, with clear separation between node, project, access-rule, docs, pricing, status, and support tools. Some subtle overlap exists between individual access-rule activation and bulk status changes, and between pricing and docs lookup, but descriptions largely resolve these.

Naming Consistency5/5

All tool names follow a consistent snake_case verb_noun pattern, such as create_node, list_projects, get_doc_page, and update_node_access_rule. No mixed casing or erratic verb styles appear.

Tool Count4/5

The 23 tools cover a broad but coherent platform surface including node/project management, access rules, docs, pricing, status, support, and faucet operations. It is slightly above the typical 15-tool range, but each functional group earns its place without obvious redundancy.

Completeness4/5

Core CRUD coverage is present for projects, nodes, and access rules, along with docs, pricing, status, organization, support, and faucet tools. Minor gaps exist around node lifecycle operations beyond rename, usage/metrics, and billing details, but agents can work around them.

Available Tools

23 tools
contact_chainstackContact ChainstackA
Destructive
Inspect

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.

Inputs: name (required), email (required), message (required), category. Returns: submitted, lead_source, alternative_channels, estimated_response_time

create_nodeCreate nodeAInspect

Deploy a new blockchain node. Call get_deployment_options first for valid IDs.

Use a Global option (node_tier "Global") from get_deployment_options.

Inputs: name (required), cloud (required), project (required), blockchain (required). Returns: id, name, cloud, region, +10 more

create_node_access_ruleCreate node access ruleA
Destructive
Inspect

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.

Inputs: value (required), node_id (required), rule_type (required), activate. Returns: rule, created, message, warnings

create_projectCreate projectCInspect

Create a new project.

Inputs: name (required), description. Returns: id, name, type, creator, +3 more

delete_nodeDelete nodeB
DestructiveIdempotent
Inspect

Delete a node (irreversible).

Inputs: node_id (required). Returns: result

delete_node_access_ruleDelete node access ruleA
DestructiveIdempotent
Inspect

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.

Inputs: node_id (required), rule_id (required). Returns: result

delete_projectDelete projectB
DestructiveIdempotent
Inspect

Delete a project (irreversible).

Inputs: project_id (required). Returns: result

get_chainstack_pricingGet Chainstack pricingA
Read-onlyIdempotent
Inspect

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.

Inputs: no named parameters. Returns: sources, warnings, fetched_at, disclaimers, +3 more

get_deployment_optionsGet deployment optionsA
Read-onlyIdempotent
Inspect

List blockchain/cloud/network combinations for node deployment.

Call before create_node to get valid blockchain and cloud IDs.

Inputs: no named parameters. Returns: result

get_doc_pageGet docs pageA
Read-onlyIdempotent
Inspect

Get the full content of a Chainstack documentation page.

Use after search_docs to fetch the complete page when a snippet isn't enough.

Inputs: page (required). Returns: result

get_nodeGet nodeA
Read-onlyIdempotent
Inspect

Get a node's full details including endpoints and cloud info.

Inputs: node_id (required). Returns: id, name, cloud, region, +10 more

get_organizationGet organizationA
Read-onlyIdempotent
Inspect

Get organization name and ID.

Inputs: no named parameters. Returns: id, name

get_platform_statusGet platform statusB
Read-onlyIdempotent
Inspect

Check platform status, active incidents, and maintenances.

Inputs: network. Returns: status, incidents, components, maintenances

get_projectGet projectC
Read-onlyIdempotent
Inspect

Get project details.

Inputs: project_id (required). Returns: id, name, type, creator, +3 more

list_node_access_rulesList node access rulesA
Read-onlyIdempotent
Inspect

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.

Inputs: node_id (required), status, rule_type. Returns: rules, message

list_nodesList nodesA
Read-onlyIdempotent
Inspect

List nodes with status and connection endpoints.

Inputs: project_id. Returns: result

list_projectsList projectsA
Read-onlyIdempotent
Inspect

List all projects. Projects are containers for nodes.

Inputs: no named parameters. Returns: result

request_testnet_fundsRequest testnet fundsA
Destructive
Inspect

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.

Inputs: address (required), network (required). Returns: note, network, amountSent, transaction

search_docsSearch Chainstack docsB
Read-onlyIdempotent
Inspect

Search Chainstack docs — blockchain RPC methods, node infrastructure, Web3 APIs, deployment guides, and code examples.

Inputs: query (required). Returns: result

set_node_access_rules_statusActivate or deactivate all node access rulesA
DestructiveIdempotent
Inspect

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.

Inputs: status (required), node_id (required). Returns: rules, message

update_nodeRename nodeC
DestructiveIdempotent
Inspect

Rename a node.

Inputs: name (required), node_id (required). Returns: id, name, cloud, region, +10 more

update_node_access_ruleUpdate node access ruleA
DestructiveIdempotent
Inspect

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.

Inputs: node_id (required), rule_id (required), value, status. Returns: rule, created, message, warnings

update_projectUpdate projectB
DestructiveIdempotent
Inspect

Update a project's name or description.

Inputs: project_id (required), name, description. Returns: id, name, type, creator, +3 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables querying blockchains across EVM, Solana, Bitcoin/UTXO, and Cosmos through a unified interface, with tools for resolving addresses, checking balances, fetching transactions and blocks, reading contracts, decoding calldata, and building unsigned transfers.
      4 npm
      3
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Read-only access to the live NOVAI blockchain (an AI-native L1) over public JSON-RPC. Query blocks, transactions, AI entities, on-chain signals, oracle anchors, and memory objects. No keys, no write paths.
      12
      69 npm
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables querying blockchain data across multiple EVM chains via RouteMesh, offering built-in RPC tools for blocks, transactions, logs, balances, and gas estimation, plus customer management tools for API keys and usage.
      11
      2
      ISC
    • A
      license
      A
      quality
      C
      maintenance
      Blockchain JSON-RPC on 23 EVM chains for AI agents — Ethereum, Base, Arbitrum, plus young chains like Robinhood Chain, Plasma and Ink. Free reads with no key; heavy methods (eth_getLogs, trace, debug) via a free API key or x402 USDC pay-per-call.
      12
      118 npm
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.