Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/chainstacklabs/mcp-server/chainstacknpx skills add chainstacklabs/mcp-server --skill chainstackgit clone --depth 1 https://github.com/chainstacklabs/mcp-serverWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00066 | $0.03697 |
| Opus 5 | $0.00033 | $0.01849 |
| Sonnet 5 | $0.00013 | $0.00739 |
| Haiku 4.5 | $0.00007 | $0.00370 |
Grade A, and why
chainstack scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Work with the Chainstack MCP server to manage blockchain nodes and projects. Use when deploying nodes, migrating to Chainstack from another RPC provider such as QuickNode or Alchemy, checking platform status How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chainstack MCP Server
Endpoint: https://mcp.chainstack.com/mcp
Access tiers
The server has two tiers of access from the same endpoint.
No API key required (just connect to the URL, no auth header needed):
search_docs— search Chainstack documentationget_doc_page— get full content of a documentation pageget_platform_status— check platform status, incidents, maintenancescontact_chainstack— submit a message to Chainstack's team (sales, support, general)get_chainstack_pricing— live pricing snapshot (plan tiers, feature matrix, add-ons, dedicated-node catalog)
API key required (pass Bearer <chainstack-api-key>):
- All platform tools:
get_organization,list_projects,create_project,get_project,update_project,delete_project,list_nodes,get_node,create_node,update_node,delete_node,get_deployment_options request_testnet_funds— top up a testnet address from Chainstack's faucet
Get an API key at https://console.chainstack.com/user/settings/api-keys
Node tiers
Chainstack has two node tiers. Picking the right one is critical when deploying.
Global Nodes (cloud CC-0016, provider chainstack_global):
- Load-balanced across regions, routes to nearest location
- Deploys instantly
- Available on all plans including free
- Best for: getting started, general RPC access
Trader Nodes (clouds CC-0020 through CC-0028, provider chainstack_managed):
- Region-bound, dedicated resources
- Deploys in 3-6 minutes
- Paid plans only
- Full and archive modes available
- Best for: low-latency trading, MEV, heavy indexing
The node_tier field in tool responses shows "Global" or "Trader" for clarity.
Workflows
Deploy a node
This is a multi-step flow. Always follow this order:
- Get deployment options: Call
get_deployment_optionsto see available blockchain/cloud/network combinations. Note theblockchainandcloudIDs you need. - Confirm location with the user: Trader nodes are region-bound (e.g., London, Ashburn, Singapore). Always show the user the available regions and ask which one before deploying. Region affects latency and cannot be changed after deployment.
- Get or create a project: Call
list_projectsto find an existing project, orcreate_projectto make a new one. Note the projectid(format:PR-123-456-789). - Create the node: Call
create_nodewithname,project,blockchain, andcloudfrom the previous steps.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 273 lines · 66 tokens per session scan A cc209ec969ab
chainstack is a skill published in the GitHub repository chainstacklabs/mcp-server (4 stars, last pushed 19d ago), licensed MIT. It adds 66 tokens to every session and 3,697 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
rustchain-mcp
This skill allows Claude Code to interact with the RustChain blockchain, monitor the network, and hunt for bounties.
klever-dev
End-to-end Klever blockchain development — smart contracts (Rust/WASM), transaction building (@klever/connect, klever-go-sdk), deployment via ksc + koperator, and on-chain interaction via MCP tools. Use when the task involves KLV, KDA tokens, klv1 addresses, Klever smart contracts, or Klever node/API interaction.
solana-mcp-skill
This skill teaches AI agents how to interact with the Solana blockchain using the Solana MCP Server.
mesa-upgrade
Operator runbook for the Mina Mesa hardfork upgrade rehearsal on the mesa-mut network, driven by the mina-mcp-server getupgradestatus tool. Use when working against --network mesa-mut, when a user asks "what phase is the Mesa upgrade in", "can I still transact on mesa-mut", "when does the hardfork happen", or when you…
clockchain-verified-alarm
Use when an agent must act at a verified future time and prove it — or timestamp/verify any event — via Clockchain. Covers the zero-creds hosted-MCP alarm flow and the full client-side SDK alarm, plus the operational invariants that prevent early fires and false anchors.
opik-diagnose
Surface the Opik traces worth a developer's attention, ranked by signal — errors, failed tool calls, latency, regressions, and low online-eval scores — plus Diagnostics issues. Reads live/production traces via the SDK (searchtraces and agentinsights) and works with no MCP; uses the MCP issue entity when connected.…