Chainstack MCP server
23 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Chainstack's own remote MCP server gives an agent Chainstack's documentation, platform status and pricing with no key, and, with an API key, the projects, blockchain nodes and node access rules of the account. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 23 tools
| Tool | Counted as |
|---|---|
request_testnet_funds | Moves money |
contact_chainstack | Deletes |
create_node_access_rule | Deletes |
delete_node | Deletes |
delete_node_access_rule | Deletes |
delete_project | Deletes |
set_node_access_rules_status | Deletes |
update_node | Deletes |
update_node_access_rule | Deletes |
update_project | Deletes |
create_node | Changes things |
create_project | Changes things |
get_chainstack_pricing | Said to only read |
get_deployment_options | Said to only read |
get_doc_page | Said to only read |
get_node | Said to only read |
get_organization | Said to only read |
get_platform_status | Said to only read |
get_project | Said to only read |
list_node_access_rules | Said to only read |
list_nodes | Said to only read |
list_projects | Said to only read |
search_docs | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://mcp.chainstack.com/mcp.
Recent changes
26 Oct 2026, 10:13 UTC, after a check on 25 Oct 2026, 09:13 UTC
Description rewritten on create_node. Inputs or outputs changed on create_node, get_doc_page.
23 Oct 2026, 09:53 UTC, after a check on 22 Oct 2026, 09:45 UTC
Title changed on contact_chainstack, create_node, create_node_access_rule, create_project, delete_node and 15 more. The server's own labels changed on contact_chainstack, create_node, create_node_access_rule, create_project, delete_node and 15 more. 23 tools changed in all.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Chainstack's tools change.
One email when Chainstack's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- With an API key, an agent can create, rename and delete projects and nodes, and change, switch off and delete the access rules on a node. Chainstack's MCP server documentation
- Every tool appears in the tool list without a key. Those that need one return an authentication error until a key is set. Chainstack's MCP server documentation
- Its contact_chainstack tool sends a message to Chainstack sales and support, and it works with no key. Chainstack's MCP server documentation
How to limit it
With Chainstack's own settings, as its documentation describes them. Stackduke has not tested them.
- Leave the API key out when the agent only needs documentation, status and pricing, which Chainstack says work without one. Chainstack's MCP server documentation
- Chainstack marks writes and deletes, contact messages and testnet fund requests as needing approval in compatible clients, so we recommend keeping those prompts on. Chainstack's changelog, 12 May 2026
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.