Noi e terze parti selezionate usiamo cookie o tecnologie simili per finalità tecniche e, con il tuo consenso, per analizzare l’uso del sito.

Puoi liberamente prestare, negare o revocare il tuo consenso in qualsiasi momento.

Chainstack

Server MCP di Chainstack

Distribuisci e gestisci nodi blockchain su oltre 70 protocolli, cerca nella documentazione Chainstack, controlla stato e prezzi e richiedi fondi testnet.

Serve una chiave API (Serve una chiave API del fornitore)Streamable HTTP

Collegati a Chainstack

Chainstack richiede una chiave API. Collegati con il suo URL e la tua chiave:

https://mcp.chainstack.com/mcp

Invia la tua chiave nell’header Authorization. mcp.tc non vede né conserva mai le chiavi. Dove trovare una chiave

Condividi questo server

Apre questa pagina, con l’URL e i passaggi di configurazione.

mcp.tc/i/chainstack

Descrizione

Collega un assistente alla piattaforma Chainstack. Puoi elencare progetti e nodi, crearli ed eliminarli, consultare le opzioni valide di blockchain e di distribuzione cloud, cercare nella documentazione dei protocolli e RPC, controllare lo stato della piattaforma, leggere i prezzi aggiornati, richiedere fondi dal faucet testnet e inviare un messaggio al team Chainstack.

Funziona come endpoint Streamable HTTP ospitato su https://mcp.chainstack.com/mcp. I tool di ricerca nella documentazione, recupero pagine, stato della piattaforma, prezzi e contatto funzionano senza chiave. I tool per nodi, progetti e faucet richiedono una chiave API di Chainstack inviata come header Authorization Bearer.

Cosa puoi fare

  • Distribuire, rinominare ed eliminare nodi blockchain
  • Creare, aggiornare ed eliminare progetti che contengono nodi
  • Elencare le opzioni valide di blockchain, cloud e regione prima della distribuzione
  • Cercare nella documentazione Chainstack e recuperare pagine complete
  • Controllare stato della piattaforma, incidenti e manutenzioni
  • Ottenere i prezzi aggiornati di piani, add-on e nodi dedicati
  • Ricaricare indirizzi testnet dal faucet Chainstack
  • Inviare un messaggio al team vendite e supporto di Chainstack

Tool 23

  • get_organizationSola lettura

    Ottiene nome e ID dell’organizzazione.

  • get_deployment_optionsSola lettura

    Elenca le combinazioni di blockchain, cloud e rete valide per la distribuzione dei nodi.

  • list_projectsSola lettura

    Elenca tutti i progetti, che sono contenitori di nodi.

  • create_projectScrive

    Crea un nuovo progetto con un nome e una descrizione facoltativa.

  • list_nodesSola lettura

    Elenca i nodi con stato ed endpoint, con filtro facoltativo per progetto.

  • get_nodeSola lettura

    Ottiene i dettagli completi di un nodo, inclusi endpoint e informazioni sul cloud.

  • create_nodeScrive

    Distribuisce un nuovo nodo blockchain in un progetto, sulla blockchain e sul cloud scelti.

  • get_projectSola lettura

    Ottiene i dettagli di un progetto.

  • update_projectPuò eliminare

    Aggiorna il nome o la descrizione di un progetto.

  • delete_projectPuò eliminare

    Elimina un progetto (irreversibile).

  • update_nodePuò eliminare

    Rinomina un nodo.

  • delete_nodePuò eliminare

    Elimina un nodo (irreversibile).

Mostra altri 11 tool
  • list_node_access_rulesSola lettura

    List node access rules

  • create_node_access_rulePuò eliminare

    Create node access rule

  • update_node_access_rulePuò eliminare

    Update node access rule

  • delete_node_access_rulePuò eliminare

    Delete node access rule

  • set_node_access_rules_statusPuò eliminare

    Activate or deactivate all node access rules

  • search_docsSola lettura

    Cerca nella documentazione Chainstack metodi RPC, configurazione dei nodi ed esempi di codice.

  • get_doc_pageSola lettura

    Recupera il contenuto completo di una pagina della documentazione Chainstack.

  • get_platform_statusSola lettura

    Controlla lo stato della piattaforma, gli incidenti attivi e le manutenzioni.

  • contact_chainstackPuò eliminare

    Invia un messaggio al team vendite e supporto di Chainstack dopo la conferma dell’utente.

  • request_testnet_fundsPuò eliminare

    Ricarica un indirizzo testnet dal faucet Chainstack fino al limite per rete.

  • get_chainstack_pricingSola lettura

    Restituisce un’istantanea aggiornata di livelli dei piani, add-on e prezzi dei nodi dedicati.

Letti dal server attivo (17 nov 2026). Sola lettura, Scrive e Può eliminare sono indicazioni dichiarate dal server; è il tuo client a decidere se chiederti conferma prima di eseguire un tool.

Prompt di esempio

  • Distribuisci un nodo Ethereum nel mio progetto predefinito

  • Cerca nella documentazione Chainstack i parametri supportati di eth_call

  • Ci sono incidenti attivi sulla piattaforma Chainstack?

  • Ricarica il mio indirizzo Sepolia con ETH di testnet

Configurazione

Ogni client si collega a mcp.chainstack.com. Scegli il tuo; la pagina ricorda la tua scelta.

Claude Code

  1. Eseguilo in un terminale, nella cartella del tuo progetto:
claude mcp add --transport http chainstack https://mcp.chainstack.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
  1. Sostituisci il segnaposto con la tua chiave prima di eseguirlo, poi controlla con /mcp dentro Claude Code.

Aggiungi --scope user per renderlo disponibile in tutti i progetti, non solo in questo.

Claude Desktop

  1. Usa il bridge mcp-remote, che tiene la chiave su questo computer (anche un connettore aggiunto su claude.ai con la chiave in Request headers compare qui). Apri Settings → Developer → Edit Config e aggiungi:
claude_desktop_config.json
{
  "mcpServers": {
    "chainstack": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.chainstack.com/mcp",
        "--header",
        "Authorization: Bearer <YOUR_API_KEY>"
      ]
    }
  }
}
  1. Sostituisci il segnaposto con la tua chiave e riavvia Claude Desktop.

Il bridge richiede Node.js sul tuo computer.

claude.ai

  1. Apri il modulo dei connettori su claude.ai. Questo pulsante compila nome e URL per te:
  1. Controlla che l’URL sia https://mcp.chainstack.com/mcp. In Request headers aggiungi Authorization: Bearer <YOUR_API_KEY> con la tua chiave di Chainstack, poi fai clic su Add.
  2. Attivalo in una chat dal menu degli strumenti.

I piani gratuiti consentono un connettore personalizzato. Nei piani Team ed Enterprise lo aggiunge un owner in Organization settings → Connectors.

Cursor

Oppure aggiungilo a mano in ~/.cursor/mcp.json (tutti i progetti) o in .cursor/mcp.json (questo progetto):

mcp.json
{
  "mcpServers": {
    "chainstack": {
      "url": "https://mcp.chainstack.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

VS Code

Aggiungilo a .vscode/mcp.json. VS Code chiede la chiave la prima volta e la conserva in modo sicuro:

.vscode/mcp.json
{
  "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

  1. Aggiungilo a ~/.config/devin/mcp_config.json (macOS e Linux) o a %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "chainstack": {
      "serverUrl": "https://mcp.chainstack.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}
  1. Aggiorna l’elenco dei server MCP in Cascade.

Devin Desktop è il nuovo nome di Windsurf. Per i server remoti legge serverUrl (o url).

Codex

codex mcp add chainstack --url https://mcp.chainstack.com/mcp --bearer-token-env-var CHAINSTACK_API_KEY

Oppure modifica direttamente ~/.codex/config.toml:

config.toml
[mcp_servers.chainstack]
url = "https://mcp.chainstack.com/mcp"
bearer_token_env_var = "CHAINSTACK_API_KEY"

Imposta CHAINSTACK_API_KEY con la tua chiave nella shell che esegue Codex.

Gemini CLI

gemini mcp add --transport http --header "Authorization: Bearer <YOUR_API_KEY>" chainstack https://mcp.chainstack.com/mcp

Così lo aggiungi al progetto corrente. Aggiungi -s user per usarlo ovunque.

Qualsiasi client

La maggior parte dei client accetta questa forma. Alcuni chiamano diversamente il campo dell’URL: serverUrl in Devin Desktop, httpUrl nel file di impostazioni di Gemini CLI.

{
  "mcpServers": {
    "chainstack": {
      "type": "http",
      "url": "https://mcp.chainstack.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_API_KEY>"
      }
    }
  }
}

Zed mette i server sotto context_servers nelle sue impostazioni. Cline ha bisogno di "type": "streamableHttp", altrimenti presume SSE.

Il tuo client avvia solo server locali? Collegalo con npx -y mcp-remote https://mcp.chainstack.com/mcp.

Embed

Mostra Chainstack in un README o sul tuo sito. Ogni embed rimanda a questa pagina, usa l’URL del server stesso e non imposta cookie. Come funzionano gli embed

Card, iframe e JSON sono in inglese. Aggiungi ?lang=it, fr, de o es al loro indirizzo per un’altra lingua.

Badge per il README

Anteprima del badge, chiaroAnteprima del badge, scuro
Markdown
[![Chainstack on mcp.tc](https://mcp.tc/i/chainstack/badge.svg)](https://mcp.tc/i/chainstack)
HTML
<a href="https://mcp.tc/i/chainstack"><img src="https://mcp.tc/i/chainstack/badge.svg" alt="Chainstack on mcp.tc" height="20"></a>

Segue la modalità chiara o scura di chi legge. Aggiungi ?theme=light o ?theme=dark per fissarla, oppure ?style=compact per mostrare il simbolo senza la scritta.

Card per il sito

HTML
<script src="https://mcp.tc/w/chainstack.js" async></script>

La card compare dove si trova il tag. Aggiungi data-theme="dark" o data-size="compact" al tag per cambiarla. Il file contiene tutto ciò che serve, quindi non fa altre richieste e non imposta cookie.

iframe

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

Usalo nelle pagine che non consentono script. Aggiungi ?theme=light o ?theme=dark all’indirizzo per fissare i colori.

JSON

La scheda come dati per le tue pagine e i tuoi strumenti: nome, descrizione breve, URL del server, tool e i link «Add to». Qualsiasi sito può leggerla (CORS aperto).

https://mcp.tc/i/chainstack.json

Cosa significa ogni campo

Prompt per l’AI

Incollalo in un assistente di programmazione con l’AI, come Claude Code o Cursor, e aggiungerà la card di Chainstack al tuo sito.

Markdown
Aggiungi al mio sito la card di mcp.tc per Chainstack, un server MCP. È un solo script statico: niente build, nessun pacchetto da installare, nessun cookie.

Metti questo tag dove deve comparire la card. La card appare subito prima del tag:

```html
<script src="https://mcp.tc/w/chainstack.js" async></script>
```

Per mostrarla altrove, metti lì questo segnaposto e carica lo stesso script una volta sola, per esempio prima di `</body>`. Lascia il link al suo interno: lo vede chi non ha JavaScript.

```html
<div data-mcptc="chainstack"><a href="https://mcp.tc/i/chainstack">Chainstack on mcp.tc</a></div>
```

Opzioni:
- `data-theme="light"` o `"dark"` sul tag o sul segnaposto fissa i colori. Senza l’attributo, la card segue la modalità chiara o scura di chi visita.
- `data-size="compact"` dà una card più piccola, senza la descrizione breve.
- La variabile CSS `--mcptc-max-width` sul segnaposto o su un elemento padre imposta la larghezza (predefinita `520px`).
- `?lang=` nell’URL dello script imposta la lingua della card: `en`, `it`, `fr`, `de` o `es`.

Se il sito ha una Content Security Policy, consenti `script-src https://mcp.tc` e `img-src data:` (l’icona è inline).

Per un README o altra documentazione in Markdown, usa invece il badge:

```markdown
[![Chainstack on mcp.tc](https://mcp.tc/i/chainstack/badge.svg)](https://mcp.tc/i/chainstack)
```

Riferimento: https://mcp.tc/it/embed

Cronologia delle modifiche

Leggiamo l’elenco dei tool di questo server ogni 3 ore e registriamo cosa cambia. Ultima lettura: 18 nov 2026, 05:34 UTC.

Segui Chainstack e ti mandiamo un’email quando qualcosa cambia.

  1. , Controllo automatico

    Nuova versione 1.12.0 (prima 1.11.4). Dichiarata dal server.

  2. , Controllo automatico

    2 tool modificati. Istruzioni del server modificate.

    Nuove istruzioni del server

    Dettagli, 26 ott 2026, 11:38 UTC

    Modificati 2

    • create_nodedescrizione e schema di input
      Prima

      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.

      Dopo

      Deploy a new blockchain node. Call get_deployment_options first for valid IDs. Use a Global option (node_tier "Global") from get_deployment_options.

      • Descrizione di cloud
        Prima

        Cloud ID from get_deployment_options (e.g., CC-0016 for Global; Trader IDs vary by region).

        Dopo

        Cloud ID of a Global option from get_deployment_options (e.g., CC-0016).

    • get_doc_pageschema di input
      • Descrizione di page
        Prima

        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 a…

        Dopo

        Page 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…

    Istruzioni del server

    Prima

    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: - 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…

    Dopo

    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: - 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…

  3. , Controllo automatico

    Nuova versione 1.11.2 (prima 1.11.1). Dichiarata dal server.

  4. , Controllo automatico

    23 tool modificati.

    Dettagli, 23 ott 2026, 04:35 UTC

    Modificati 23

    • contact_chainstacktitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Contact Chainstack

      • idempotentHint non indicato diventa no
    • create_nodetitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Create node

      • idempotentHint non indicato diventa no
    • create_node_access_ruletitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Create node access rule

      • idempotentHint non indicato diventa no
    • create_projecttitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Create project

      • idempotentHint non indicato diventa no
    • delete_nodetitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Delete node

      • idempotentHint non indicato diventa sì
    • delete_node_access_ruletitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Delete node access rule

      • idempotentHint non indicato diventa sì
    • delete_projecttitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Delete project

      • idempotentHint non indicato diventa sì
    • get_chainstack_pricingtitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Get Chainstack pricing

      • openWorldHint sì diventa no
      • idempotentHint non indicato diventa sì
    • get_deployment_optionstitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Get deployment options

      • openWorldHint sì diventa no
      • idempotentHint non indicato diventa sì
    • get_doc_pagetitolo e indicazioni

      titolo

      Prima

      nessuno

      Dopo

      Get docs page

      • openWorldHint sì diventa no
      • idempotentHint non indicato diventa sì

    get_node get_organization get_platform_status get_project list_node_access_rules list_nodes list_projects request_testnet_funds search_docs set_node_access_rules_status update_node update_node_access_rule update_project

  5. , Controllo automatico

    Nuova versione 1.11.1 (prima 1.11.0). Dichiarata dal server.

  6. , Controllo automatico

    3 tool modificati. Istruzioni del server modificate.

    Nuove istruzioni del server

    Dettagli, 12 ott 2026, 13:33 UTC

    Modificati 3

    • create_nodeschema di input
      • Descrizione di cloud
        Prima

        Cloud ID from get_deployment_options (e.g., CC-0016 for Global, CC-0020 for London).

        Dopo

        Cloud ID from get_deployment_options (e.g., CC-0016 for Global; Trader IDs vary by region).

    • get_deployment_optionsschema di output
    • request_testnet_fundsdescrizione e schema di output
      Prima

      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.

      Dopo

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

    Istruzioni del server

    Prima

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

    Dopo

    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: - 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…

  7. , Controllo automatico

    Nuova versione 1.11.0 (prima 1.10.11). Dichiarata dal server.

  8. , Controllo automatico

    5 tool aggiunti e 2 tool modificati. Istruzioni del server modificate.

    Nuovo tool indicato come distruttivo, Nuove istruzioni del server

    Dettagli, 11 ott 2026, 07:31 UTC

    Aggiunti 5

    • create_node_access_rulePuò eliminare

      Add 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_rulePuò eliminare

      Delete 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_rulesSola lettura

      List 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_statusPuò eliminare

      Activate 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_rulePuò eliminare

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

    Modificati 2

    • contact_chainstackdescrizione
      Prima

      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…

      Dopo

      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 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_pricingdescrizione
      Prima

      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…

      Dopo

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

    Istruzioni del server

    Prima

    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: - 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…

    Dopo

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

  9. , Controllo automatico

    Inizio del tracciamento: 18 tool.

Domande frequenti

Posso incollare mcp.tc/i/chainstack nel mio client MCP?

No. I link di mcp.tc sono pagine, non indirizzi di server. Collegati con https://mcp.chainstack.com/mcp, così il tuo client parla direttamente con Chainstack. Anche la tua chiave va lì, mai a mcp.tc. Il link rapido serve per condividere: apre questa pagina, con i passaggi di configurazione per ogni client.

Chainstack richiede una chiave API o un accesso?

Sì. Chainstack richiede una chiave API, inviata nell’header Authorization. Procuratene una da Chainstack e tienila nella configurazione del tuo client, mai in un file condiviso.

Chainstack è un server remoto o locale?

Remoto. Lo ospita Chainstack a https://mcp.chainstack.com/mcp, e usa Streamable HTTP. Non c’è nulla da installare.

Cosa può fare Chainstack?

Ha 23 tool, tra cui get_organization, get_deployment_options e list_projects. Puoi distribuire, rinominare ed eliminare nodi blockchain, creare, aggiornare ed eliminare progetti che contengono nodi e elencare le opzioni valide di blockchain, cloud e regione prima della distribuzione.

Quali client possono usarlo?

Qualsiasi client che supporta i server MCP remoti e può inviare la tua chiave: Claude Code, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed e altri. Su claude.ai e Claude Desktop aggiungi la chiave come header della richiesta quando crei il connettore personalizzato. ChatGPT non può inviare una chiave, quindi non può usarlo.

mcp.tc tiene traccia delle modifiche di Chainstack?

Sì. La sezione Cronologia di Chainstack mostra ogni modifica che troviamo ai suoi tool, fino a descrizioni e parametri, più le nuove versioni e le modifiche di chi lo gestisce. Segui la scheda per ricevere un’email quando cambia.

Chi ha scritto questa pagina?

Il robot di mcp.tc ha letto i metadati di Chainstack (il suo handshake MCP, l’elenco dei tool e le pagine pubbliche), e un modello di AI ne ha ricavato il testo. Una persona esamina tutto ciò che i controlli non riescono a confermare. Il testo può comunque contenere errori, quindi se ne trovi uno usa Segnala questa scheda su questa pagina. Questa traduzione è stata fatta da un modello di AI a partire dal testo inglese.

mcp.tc non è affiliato a Chainstack. Questa pagina è stata creata a partire dai metadati pubblici di Chainstack (ultimo controllo: 17 nov 2026), e la descrizione l’ha scritta un modello di AI, quindi può contenere errori. Nomi e marchi appartengono ai rispettivi titolari. Qualcosa non va? Segnala questa scheda. La traduzione è stata fatta da un modello di AI a partire dal testo inglese.