_ registry / mcp http-sse

Chainstack

https://mcp.chainstack.com

Registry code: 495669e250d4f6a9

api record

Chainstack MCP server — deploy and manage blockchain nodes, search protocol docs and RPC references, check platform status, get pricing, request testnet funds, and contact the Chainstack team.

Key behaviors:

endpoint
https://mcp.chainstack.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
unknown
uptime
—
latency
—

last good check

priced tools
0

of 18 tools

_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 18 tools
18 never probed 0 of 18 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_deployment_options unknown never probed

    List blockchain/cloud/network combinations for node deployment. Call before create_node to get valid blockchain and cloud IDs.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • list_projects unknown never probed

    List all projects. Projects are containers for nodes.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • create_project unknown never probed

    Create a new project. Args: name: Project name. description: Optional description.

    mcp-tool

    {
  "type": "object",
  "required": [
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "description": {
      "type": "string",
      "default": ""
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • list_nodes unknown never probed

    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 the organization.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "project_id": {
      "type": "string",
      "default": ""
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • get_node unknown never probed

    Get a node's full details including endpoints and cloud info. Args: node_id: Node ID (e.g., ND-123-456-789).

    mcp-tool

    {
  "type": "object",
  "required": [
    "node_id"
  ],
  "properties": {
    "node_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • create_node unknown never probed

    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. Args: name: Node name. project: Project ID from list_projects (e.g., PR-123-456-789). blockchain: Blockchain ID from get_deployment_options (e.g., BC-000-000-008). cloud: Cloud ID from get_deployment_options (e.g., CC-0016 for Global, CC-0020 for London).

    mcp-tool

    {
  "type": "object",
  "required": [
    "name",
    "project",
    "blockchain",
    "cloud"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "cloud": {
      "type": "string"
    },
    "project": {
      "type": "string"
    },
    "blockchain": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • get_project unknown never probed

    Get project details. Args: project_id: Project ID (e.g., PR-123-456-789).

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "project_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • update_project unknown never probed

    Update a project's name or description. Args: project_id: Project ID (e.g., PR-123-456-789). name: New name. description: New description.

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    },
    "project_id": {
      "type": "string"
    },
    "description": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null
    }
  },
  "additionalProperties": false
}
    arguments 34 lines
  • delete_project unknown never probed

    Delete a project (irreversible). Args: project_id: Project ID (e.g., PR-123-456-789).

    mcp-tool

    {
  "type": "object",
  "required": [
    "project_id"
  ],
  "properties": {
    "project_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • update_node unknown never probed

    Rename a node. Args: node_id: Node ID (e.g., ND-123-456-789). name: New name.

    mcp-tool

    {
  "type": "object",
  "required": [
    "node_id",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "node_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 16 lines
  • delete_node unknown never probed

    Delete a node (irreversible). Args: node_id: Node ID (e.g., ND-123-456-789).

    mcp-tool

    {
  "type": "object",
  "required": [
    "node_id"
  ],
  "properties": {
    "node_id": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • search_docs unknown never probed

    Search Chainstack docs — blockchain RPC methods, node infrastructure, Web3 APIs, deployment guides, and code examples. Args: query: Search query (e.g., "deploy ethereum node", "eth_call").

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "query": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_doc_page unknown never probed

    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 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "page"
  ],
  "properties": {
    "page": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 12 lines
  • get_platform_status unknown never probed

    Check platform status, active incidents, and maintenances. Args: network: Optional filter (e.g., "ethereum"). Without it, returns overall status and incidents only.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "network": {
      "type": "string",
      "default": ""
    }
  },
  "additionalProperties": false
}
    arguments 10 lines
  • contact_chainstack unknown never probed

    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: "I'll also include your Chainstack account info (org name and ID) so the team can pull up your account immediately — this means significantly faster handling and a more tailored response." 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, or on-chain account details the user hasn't approved sharing - Any information the user hasn't explicitly approved sharing If the user shared sensitive data during the conversation, do NOT include it unless they specifically approve it in the review step. ## Writing an effective message A great message gets the user a faster, more tailored response. Include what you already know from the conversation: - What they're building and at what scale - Current plan and usage (e.g., "Pro plan, ~80M RU/month on Base") - What they need (upgrade, custom pricing, migration help, etc.) - What they've tried or what's not working - Specific numbers when available 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." The difference between a generic reply and a tailored proposal is the context you include. Not for incidents or urgent outages — point users to https://support.chainstack.com/hc/en-us/requests/new to file a support ticket, and https://status.chainstack.com for live status. For feature requests, do NOT use this tool — point users to https://ideas.chainstack.com (product) or https://github.com/chainstacklabs/mcp-server/issues/new (MCP server). Works with or without a Chainstack API key. With a key, the submission includes the user's Chainstack org info for faster account identification and handling. Args: message: 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: 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". email: User's contact email. Required. Ask the user if you don't already have it. name: 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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "message",
    "email",
    "name"
  ],
  "properties": {
    "name": {
      "type": "string"
    },
    "email": {
      "type": "string"
    },
    "message": {
      "type": "string"
    },
    "category": {
      "type": "string",
      "default": "general"
    }
  },
  "additionalProperties": false
}
    arguments 24 lines
  • request_testnet_funds unknown never probed

    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. Supported networks and their native assets: - sepolia, hoodi — Ethereum testnets (ETH) - base — Base Sepolia (ETH) - amoy — Polygon Amoy (POL) - bnb-testnet — BNB Smart Chain testnet (BNB) - zksync-testnet — zkSync Sepolia (ETH) - robinhood — Robinhood Chain testnet (ETH) - hyperevm — HyperEVM testnet (HYPE) - plasma — Plasma testnet (XPL) - monad — Monad testnet (MON) - ton — TON testnet (TON) - solana — Solana devnet (SOL) Per-address cooldown applies after each successful drip. On cooldown the faucet returns a `nextFaucetAvailable` timestamp (ISO 8601) that this tool surfaces in the error message. Requires a Chainstack API key. The key is also the rate-limiting identity — the faucet tracks usage per organization. Get a key at https://console.chainstack.com/user/settings/api-keys and add it as `Authorization: Bearer <key>` in the MCP client config. Never ask the user to paste their API key in chat. Args: network: Canonical testnet id (the schema `enum` advertises the set). Case-insensitive; common aliases are normalized to the canonical id. address: 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. Returns: On success: `{network, amountSent, transaction}`. `amountSent` is a string in the network's native unit (not wei/lamports).

    mcp-tool

    {
  "type": "object",
  "required": [
    "network",
    "address"
  ],
  "properties": {
    "address": {
      "type": "string"
    },
    "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
}
    arguments 36 lines
  • get_chainstack_pricing unknown never probed

    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. Design: we pass pricing.md through as raw markdown. Marketing owns that file and its structure changes freely; parsing it server-side would couple us to heading text and table column names we don't control. The LLM reads markdown natively, so handing the raw text to the agent keeps us correct regardless of how the page is restructured. pricing_current.json is parsed into `dedicated_catalog` because it has a stable engineering-owned schema, and the catalog benefits from filtering (to user-orderable SKUs only), unit conversion (cents → USD, milli-cores → cores), and region humanization (via `region_legend`). 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. Already filtered to the ~87 orderable SKUs and unit-converted. - `region_legend`: slug → human city name map covering every region slug that appears in `dedicated_catalog`. Use `region_legend[slug]` to translate for display; `regions` keeps the slug as the canonical identifier. - `disclaimers`: list-price caveats (Enterprise "from" pricing, etc.). - `sources`: URL + ok/error per source; the JSON source carries its own `updated_at`. - `warnings`: populated when a source is unreachable or the JSON parser failed. The tool still returns best-effort results. - `fetched_at`: UTC timestamp of this call.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • get_organization unknown never probed

    Get organization name and ID.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/495669e250d4f6a9/badge.svg)](https://brick.blue/agent/495669e250d4f6a9)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.