Chainstack
Servidor MCP de Chainstack
Despliega y gestiona nodos blockchain en más de 70 protocolos, busca en la documentación de Chainstack, consulta estado y precios, y solicita fondos de testnet.
Conectar con Chainstack
Chainstack requiere una clave de API. Conéctate con su propia URL y tu clave:
Envía tu clave en la cabecera Authorization. mcp.tc nunca ve ni guarda claves. Dónde conseguir una clave
Compartir este servidor
El enlace abre esta página, con la URL y los pasos de configuración.
mcp.tc/i/chainstackDescripción
Conecta un asistente con la plataforma Chainstack. Puedes listar proyectos y nodos, crearlos y eliminarlos, consultar las opciones válidas de blockchain y de despliegue en la nube, buscar en la documentación de protocolos y RPC, comprobar el estado de la plataforma, leer los precios en vivo, solicitar fondos del faucet de testnet y enviar un mensaje al equipo de Chainstack.
Funciona como un endpoint Streamable HTTP alojado en https://mcp.chainstack.com/mcp. Las herramientas de búsqueda en la documentación, obtención de páginas, estado de la plataforma, precios y contacto funcionan sin clave. Las herramientas de nodos, proyectos y faucet necesitan una clave de API de Chainstack enviada como cabecera Authorization Bearer.
Qué puedes hacer
- Desplegar, renombrar y eliminar nodos blockchain
- Crear, actualizar y eliminar proyectos que contienen nodos
- Listar las opciones válidas de blockchain, nube y región antes de desplegar
- Buscar en la documentación de Chainstack y obtener páginas completas
- Comprobar el estado de la plataforma, incidentes y mantenimientos
- Obtener los precios en vivo de planes, complementos y nodos dedicados
- Recargar direcciones de testnet desde el faucet de Chainstack
- Enviar un mensaje a ventas y soporte de Chainstack
Herramientas 23
get_organizationSolo lecturaObtener el nombre y el ID de la organización.
get_deployment_optionsSolo lecturaListar las combinaciones de blockchain, nube y red válidas para el despliegue de nodos.
list_projectsSolo lecturaListar todos los proyectos, que son contenedores de nodos.
create_projectEscrituraCrear un nuevo proyecto con un nombre y una descripción opcional.
list_nodesSolo lecturaListar nodos con su estado y endpoints, filtrados opcionalmente por proyecto.
get_nodeSolo lecturaObtener todos los detalles de un nodo, incluidos endpoints e información de la nube.
create_nodeEscrituraDesplegar un nuevo nodo blockchain en un proyecto, en la blockchain y la nube elegidas.
get_projectSolo lecturaObtener los detalles de un proyecto.
update_projectPuede borrarActualizar el nombre o la descripción de un proyecto.
delete_projectPuede borrarEliminar un proyecto (irreversible).
update_nodePuede borrarRenombrar un nodo.
delete_nodePuede borrarEliminar un nodo (irreversible).
Mostrar 11 herramientas más
list_node_access_rulesSolo lecturaList node access rules
create_node_access_rulePuede borrarCreate node access rule
update_node_access_rulePuede borrarUpdate node access rule
delete_node_access_rulePuede borrarDelete node access rule
set_node_access_rules_statusPuede borrarActivate or deactivate all node access rules
search_docsSolo lecturaBuscar en la documentación de Chainstack métodos RPC, configuración de nodos y ejemplos de código.
get_doc_pageSolo lecturaObtener el contenido completo de una página de la documentación de Chainstack.
get_platform_statusSolo lecturaComprobar el estado de la plataforma, los incidentes activos y los mantenimientos.
contact_chainstackPuede borrarEnviar un mensaje al equipo de ventas y soporte de Chainstack tras la confirmación del usuario.
request_testnet_fundsPuede borrarRecargar una dirección de testnet desde el faucet de Chainstack hasta el límite por red.
get_chainstack_pricingSolo lecturaDevolver una instantánea en vivo de los niveles de plan, complementos y precios de nodos dedicados.
Leídas del servidor en funcionamiento el 17 nov 2026. Solo lectura, Escritura y Puede borrar son indicaciones que declara el servidor; tu cliente decide si te pregunta antes de ejecutar una herramienta.
Prompts de ejemplo
Despliega un nodo de Ethereum en mi proyecto predeterminado
Busca en la documentación de Chainstack los parámetros compatibles de eth_call
¿Hay algún incidente activo en la plataforma Chainstack?
Recarga mi dirección de Sepolia con ETH de testnet
Configuración
Todos los clientes se conectan a mcp.chainstack.com. Elige el tuyo; la página recuerda tu elección.
Claude Code
- Ejecútalo en un terminal, en la carpeta de tu proyecto:
claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"- Sustituye el marcador por tu clave antes de ejecutarlo, y después compruébalo con
/mcpdentro de Claude Code.
Añade --scope user para que esté disponible en todos los proyectos, no solo en este.
Claude Desktop
- Usa el puente
mcp-remote, que guarda la clave en este equipo (un conector añadido en claude.ai con la clave en Request headers también aparece aquí). Abre Settings → Developer → Edit Config y añade:
{
"mcpServers": {
"chainstack": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.chainstack.com/mcp",
"--header",
"Authorization: Bearer <YOUR_API_KEY>"
]
}
}
}- Sustituye el marcador por tu clave y reinicia Claude Desktop.
El puente necesita Node.js en tu equipo.
claude.ai
- Abre el formulario de conectores en claude.ai. Este botón rellena el nombre y la URL por ti:
Añadir a claude.ai (se abre en una pestaña nueva)
- Comprueba que la URL es
https://mcp.chainstack.com/mcp. En Request headers, añadeAuthorization: Bearer <YOUR_API_KEY>con tu clave de Chainstack y luego haz clic en Add. - Actívalo en un chat desde el menú de herramientas.
Los planes gratuitos permiten un conector personalizado. En los planes Team y Enterprise lo añade un propietario en Organization settings → Connectors.
Cursor
Añadir a Cursor (se abre en una pestaña nueva)
O añádelo a mano en ~/.cursor/mcp.json (todos los proyectos) o en .cursor/mcp.json (este proyecto):
{
"mcpServers": {
"chainstack": {
"url": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}VS Code
Añádelo a .vscode/mcp.json. VS Code pide la clave la primera vez y la guarda de forma segura:
{
"servers": {
"chainstack": {
"type": "http",
"url": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer ${input:api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "api-key",
"description": "API key",
"password": true
}
]
}Devin Desktop
- Añádelo a
~/.config/devin/mcp_config.json(macOS y Linux) o a%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"chainstack": {
"serverUrl": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}- Actualiza la lista de servidores MCP en Cascade.
Devin Desktop es el nuevo nombre de Windsurf. Para los servidores remotos lee serverUrl (o url).
Codex
codex mcp add chainstack --url https://mcp.chainstack.com/mcp --bearer-token-env-var CHAINSTACK_API_KEYO edita directamente ~/.codex/config.toml:
[mcp_servers.chainstack]
url = "https://mcp.chainstack.com/mcp"
bearer_token_env_var = "CHAINSTACK_API_KEY"Asigna tu clave a CHAINSTACK_API_KEY en el shell que ejecuta Codex.
Gemini CLI
gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" chainstack https://mcp.chainstack.com/mcpAsí lo añades al proyecto actual. Añade -s user para usarlo en todas partes.
Cualquier cliente
La mayoría de los clientes aceptan esta forma. Algunos llaman de otra manera al campo de la URL: serverUrl en Devin Desktop, httpUrl en el archivo de ajustes de Gemini CLI.
{
"mcpServers": {
"chainstack": {
"type": "http",
"url": "https://mcp.chainstack.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Zed pone los servidores bajo context_servers en sus ajustes. Cline necesita "type": "streamableHttp"; si no, supone SSE.
¿Tu cliente solo inicia servidores locales? Conéctalo con npx -y mcp-remote https://mcp.chainstack.com/mcp.
Insertar
Muestra Chainstack en un README o en tu web. Cada inserción enlaza a esta página, usa la URL propia del servidor y no instala cookies. Cómo funcionan las inserciones
La tarjeta, el iframe y el JSON están en inglés. Añade ?lang=it, fr, de o es a su dirección para otro idioma.
Insignia para README
[](https://mcp.tc/i/chainstack)<a href="https://mcp.tc/i/chainstack"><img src="https://mcp.tc/i/chainstack/badge.svg" alt="Chainstack on mcp.tc" height="20"></a>Sigue el modo claro u oscuro de quien lee. Añade ?theme=light o ?theme=dark para fijarlo, o ?style=compact para mostrar el símbolo sin la palabra.
Tarjeta para web
<script src="https://mcp.tc/w/chainstack.js" async></script>La tarjeta aparece donde esté la etiqueta. Añade data-theme="dark" o data-size="compact" a la etiqueta para cambiarla. El archivo contiene todo lo que necesita, así que no hace otras solicitudes ni instala cookies.
iframe
<iframe src="https://mcp.tc/embed/chainstack" title="Chainstack on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Úsalo en páginas que no permiten scripts. Añade ?theme=light o ?theme=dark a la dirección para fijar los colores.
JSON
La ficha como datos para tus propias páginas y herramientas: nombre, descripción corta, la URL propia del servidor, herramientas y los enlaces «Add to». Cualquier web puede leerla (CORS abierto).
https://mcp.tc/i/chainstack.jsonPrompt para la IA
Pégalo en un asistente de programación con IA, como Claude Code o Cursor, y añadirá la tarjeta de Chainstack a tu web.
Añade a mi web la tarjeta de mcp.tc de Chainstack, un servidor MCP. Es un solo script estático: sin paso de build, sin paquetes que instalar, sin cookies.
Pon esta etiqueta donde deba aparecer la tarjeta. La tarjeta se muestra justo antes de ella:
```html
<script src="https://mcp.tc/w/chainstack.js" async></script>
```
Para mostrarla en otro sitio, pon allí este marcador y carga el mismo script una sola vez, por ejemplo antes de `</body>`. Deja el enlace dentro: lo ven los visitantes sin JavaScript.
```html
<div data-mcptc="chainstack"><a href="https://mcp.tc/i/chainstack">Chainstack on mcp.tc</a></div>
```
Opciones:
- `data-theme="light"` o `"dark"` en la etiqueta o el marcador fija los colores. Sin él, la tarjeta sigue el modo claro u oscuro del visitante.
- `data-size="compact"` da una tarjeta más pequeña, sin el eslogan.
- La variable CSS `--mcptc-max-width` en el marcador o en un elemento padre fija el ancho (por defecto `520px`).
- `?lang=` en la URL del script fija el idioma de la tarjeta: `en`, `it`, `fr`, `de` o `es`.
Si el sitio tiene una Content Security Policy, permite `script-src https://mcp.tc` e `img-src data:` (el icono va incrustado).
Para un README u otra documentación en Markdown, usa la insignia:
```markdown
[](https://mcp.tc/i/chainstack)
```
Referencia: https://mcp.tc/es/embedHistorial de cambios
Leemos la lista de herramientas de este servidor cada 3 horas y registramos lo que cambia. Última lectura: 18 nov 2026, 05:34 UTC.
-
Nueva versión 1.12.0 (antes 1.11.4). Declarada por el servidor.
-
2 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 26 oct 2026, 11:38 UTC
Cambiadas 2
create_nodedescripción y esquema de entradaAntesDeploy 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.DespuésDeploy a new blockchain node. Call get_deployment_options first for valid IDs. Use a Global option (node_tier "Global") from get_deployment_options.
- Descripción de
cloudAntesCloud ID from get_deployment_options (e.g.,
CC-0016 for Global; Trader IDs vary by region).DespuésCloud ID of a Global option from get_deployment_options (e.g., CC-0016).
- Descripción de
get_doc_pageesquema de entrada- Descripción de
pageAntesPage 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 prefixa…DespuésPage path from search results — pass the `page` field from a search_docs result (e.g., "docs/ethereum-tooling"). The leading slash, the `.mdx` extension, and the docs.chainstack.com URL prefix are al…
- Descripción de
Instrucciones del servidor
AntesChainstack 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: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. - Trader:
region-bound, full/archive, paid plans; cloud ID per region fro…DespuésChainstack 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: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. Deploy these. - Trader: regional nodes; don't deploy new ones. - Dedicate…
-
Nueva versión 1.11.2 (antes 1.11.1). Declarada por el servidor.
-
23 herramientas cambiadas.
Detalles, 23 oct 2026, 04:35 UTC
Cambiadas 23
contact_chainstacktítulo y indicacionestítulo
Antesninguno
DespuésContact Chainstack
idempotentHintsin indicar pasa a no
create_nodetítulo y indicacionestítulo
Antesninguno
DespuésCreate node
idempotentHintsin indicar pasa a no
create_node_access_ruletítulo y indicacionestítulo
Antesninguno
DespuésCreate node access rule
idempotentHintsin indicar pasa a no
create_projecttítulo y indicacionestítulo
Antesninguno
DespuésCreate project
idempotentHintsin indicar pasa a no
delete_nodetítulo y indicacionestítulo
Antesninguno
DespuésDelete node
idempotentHintsin indicar pasa a sí
delete_node_access_ruletítulo y indicacionestítulo
Antesninguno
DespuésDelete node access rule
idempotentHintsin indicar pasa a sí
delete_projecttítulo y indicacionestítulo
Antesninguno
DespuésDelete project
idempotentHintsin indicar pasa a sí
get_chainstack_pricingtítulo y indicacionestítulo
Antesninguno
DespuésGet Chainstack pricing
openWorldHintsí pasa a noidempotentHintsin indicar pasa a sí
get_deployment_optionstítulo y indicacionestítulo
Antesninguno
DespuésGet deployment options
openWorldHintsí pasa a noidempotentHintsin indicar pasa a sí
get_doc_pagetítulo y indicacionestítulo
Antesninguno
DespuésGet docs page
openWorldHintsí pasa a noidempotentHintsin indicar pasa a sí
get_nodeget_organizationget_platform_statusget_projectlist_node_access_ruleslist_nodeslist_projectsrequest_testnet_fundssearch_docsset_node_access_rules_statusupdate_nodeupdate_node_access_ruleupdate_project -
Nueva versión 1.11.1 (antes 1.11.0). Declarada por el servidor.
-
3 herramientas cambiadas. Instrucciones del servidor cambiadas.
Nuevas instrucciones del servidor
Detalles, 12 oct 2026, 13:33 UTC
Cambiadas 3
create_nodeesquema de entrada- Descripción de
cloudAntesCloud ID from get_deployment_options (e.g., CC-0016 for
Global, CC-0020 for London).DespuésCloud ID from get_deployment_options (e.g., CC-0016 for Global; Trader IDs vary by region).
- Descripción de
get_deployment_optionsesquema de salidarequest_testnet_fundsdescripción y esquema de salidaAntesTop 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.
DespuésTop 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.
Instrucciones del servidor
AntesChainstack 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: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. -
Trader (CC-0020–0028):region-bound, full/archive, paidplans.DespuésChainstack 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: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. - Trader: region-bound, full/archive, paid plans; cloud ID per region fro…
-
Nueva versión 1.11.0 (antes 1.10.11). Declarada por el servidor.
-
5 herramientas añadidas y 2 herramientas cambiadas. Instrucciones del servidor cambiadas.
Herramienta nueva marcada como destructiva, Nuevas instrucciones del servidor
Detalles, 11 oct 2026, 07:31 UTC
Añadidas 5
create_node_access_rulePuede borrarAdd 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.
delete_node_access_rulePuede borrarDelete 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.
list_node_access_rulesSolo lecturaList 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.
set_node_access_rules_statusPuede borrarActivate 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.
update_node_access_rulePuede borrarChange 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.
Cambiadas 2
contact_chainstackdescripciónAntesSubmit 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…
DespuésSubmit 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, trans…
get_chainstack_pricingdescripciónAntesFetch 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…
DespuésFetch 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 re…
Instrucciones del servidor
AntesChainstack 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: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - When the user asks about a protocol's features or RPC methods, SEARCH DOCS first — Chainstack has per-protocol guides covering configuration, supported methods, and node setup. - Some Chainstack features are not available through the API but are self-serve in the console: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on (flat-fee RPS tiers). If the user asks about these, point them to https://console.chainstack.com. - If the user needs testnet funds for development, use request_testnet_funds. The faucet tops the address up to the per-network cap (it doesn't send a fixed amount). - If the user wants custom node configuration, offer to submit a request via contact_chainstack. Examples include custom gas caps, transaction pool settings, custom tracers, and private networking — but Chainstack is open to any customization request. - For pricing questions — plan fit, overage math, dedicated-node quotes, add-on costs — call get_chainstack_pricing first. It returns live plan tiers, a feature matrix, add-on tables, and a per-chain dedicated-node catalog. Do the arithmetic yourself from that snapshot; don't recite prices from memory. - To migrate a project from another RPC provider — QuickNode, Alchemy, or any other — fetch the migration runbook with get_doc_page('docs/migrate-to-chainstack-with-ai') and follow it. It assesses the project's current endpoints and usage, estimates the equivalent Chainstack cost and savings (call get_chainstack_pricing; pricing.md carries the QuickNode/Alchemy conversion multipliers), and repoints endpoints after the user approves. Authentication: - search_docs, get_doc_page, get…
DespuésChainstack 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: - If the user needs a node, DEPLOY IT with create_node. Never send them to the console — they're using MCP to stay in their IDE. - For a protocol's features or RPC methods, SEARCH DOCS first. - Not in the API but self-serve at https://console.chainstack.com: warp transactions, Solana Geyser, MEV protection, and the unlimited node add-on. - request_testnet_funds tops an address up to the per-network cap; it doesn't send a fixed amount. - For custom node configuration (gas caps, txpool, tracers, private networking, anything else), offer a contact_chainstack request. - For pricing (plan fit, overage math, dedicated nodes, add-ons), call get_chainstack_pricing and do the arithmetic from it; don't quote prices from memory. - To migrate from QuickNode, Alchemy, or another provider, follow get_doc_page('docs/migrate-to-chainstack-with-ai'). - Node access rules (IP and Origin allowlists, Global nodes only) do nothing until activated. Active IP and Origin rules are both enforced: a request must pass each, or it gets 403. Before activating, confirm the IP rules cover every client. Origin rules block servers and scripts (no Origin header), even from allowed IPs. Authentication: - search_docs, get_doc_page, get_platform_status, contact_chainstack, and get_chainstack_pricing need no API key. Other tools need a Chainstack API key as Authorization: Bearer <key> in the MCP client config. - On a 401, explain instead of dumping the error: no key is set yet (node management needs a free key), or the key is invalid or expired. Point to https://console.chainstack.com/user/settings/api-keys. Never ask the user to paste the key into the chat. Node tiers: - Global (CC-0016): load-balanced, instant, all plans. - Trader (CC-0020–0028): region-bound, full/archive, paid plans.
-
Inicio del seguimiento: 18 herramientas.
Preguntas frecuentes
¿Puedo pegar mcp.tc/i/chainstack en mi cliente MCP?
No. Los enlaces de mcp.tc son páginas, no direcciones de servidores. Conéctate con https://mcp.chainstack.com/mcp, para que tu cliente hable directamente con Chainstack. Tu clave también va ahí, nunca a mcp.tc. El enlace rápido sirve para compartir: abre esta página, con los pasos de configuración para cada cliente.
¿Chainstack necesita una clave de API o iniciar sesión?
Sí. Chainstack necesita una clave de API, enviada en la cabecera Authorization. Consíguela en Chainstack y guárdala en la configuración de tu cliente, nunca en un archivo compartido.
¿Chainstack es un servidor remoto o local?
Remoto. Lo aloja Chainstack en https://mcp.chainstack.com/mcp, y usa Streamable HTTP. No hay nada que instalar.
¿Qué puede hacer Chainstack?
Tiene 23 herramientas, entre ellas get_organization, get_deployment_options y list_projects. Puedes desplegar, renombrar y eliminar nodos blockchain, crear, actualizar y eliminar proyectos que contienen nodos y listar las opciones válidas de blockchain, nube y región antes de desplegar.
¿Qué clientes pueden usarlo?
Cualquier cliente compatible con servidores MCP remotos que pueda enviar tu clave: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed y otros. En claude.ai y Claude Desktop, añade la clave como cabecera de la solicitud al crear el conector personalizado. ChatGPT no puede enviar una clave, así que no puede usarlo.
¿mcp.tc sigue los cambios de Chainstack?
Sí. La pestaña Historial de Chainstack muestra cada cambio que encontramos en sus herramientas, hasta las descripciones y los parámetros, además de las versiones nuevas y las ediciones de su responsable. Sigue la ficha para recibir un correo cuando cambie.
¿Quién escribió esta página?
El robot de mcp.tc leyó los metadatos propios de Chainstack (su handshake MCP, su lista de herramientas y sus páginas públicas), y un modelo de IA redactó el texto a partir de ellos. Una persona revisa todo lo que las comprobaciones no pueden confirmar. Aun así, el texto puede contener errores, así que si encuentras uno, usa Reportar esta ficha en esta página. Esta traducción la hizo un modelo de IA a partir del texto en inglés.
mcp.tc no tiene relación con Chainstack. Esta página se creó a partir de los metadatos públicos de Chainstack, comprobados por última vez el 17 nov 2026, y un modelo de IA escribió la descripción, así que puede contener errores. Los nombres y marcas pertenecen a sus titulares. ¿Algo no cuadra? Reportar esta ficha. La traducción la hizo un modelo de IA a partir del texto en inglés.