Chainstack

Reviewed 1d ago.

• tools: 18 tools scanned
• metadata: scanned

No findings.

Tools (18)

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

• 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/. ## 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, priv

• 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 as "top up" not "give", and surface the returned `amountSent` so they see the actual delta.

• 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 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), u