--- title: "Chainstack MCP server | Agent MCP Directory" description: "Chainstack has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026." canonical: https://agentmcpdirectory.com/directory/chainstack-com site: "Agent MCP Directory" last_updated: 2026-11-05 section: "Directory entries" --- # Chainstack MCP server | Agent MCP Directory > Chainstack has an open MCP server with 23 tools and no authentication. Endpoint, auth type and tool list, checked by connecting on 4 November 2026. Source: https://agentmcpdirectory.com/directory/chainstack-com Site: Agent MCP Directory Last reviewed: 2026-11-05 # Chainstack: MCP server, CLI and agent surfaces Yes: Chainstack runs a public MCP server at mcp.chainstack.com that listed 23 tools to a client with no credentials on 4 November 2026. Examples: get\_organization, get\_deployment\_options, list\_projects. It speaks streamable-http, protocol 2025-11-25. Ora's cached score for chainstack.com is 71, grade B, read on 5 November 2026. ## Fact sheet | Company | Chainstack | | --- | --- | | Domain | chainstack.com | | Category | Infrastructure (assigned by this directory from the registry description) | | MCP server | Verified (No authentication) | | Ora score | 71, grade B; Ora scanned the domain on 24 August 2026 and the cached score was read on 5 November 2026 from its score API (Ora's score page for chainstack.com, a vendor-published score) | | Company found through | the GitHub MCP Registry; the official MCP Registry | | Last verified | 4 November 2026 | ## MCP server | Endpoint | https://mcp.chainstack.com/mcp | | --- | --- | | How it was found | listed in the GitHub MCP Registry; the official MCP Registry | | Transport | streamable-http | | HTTP status | 200 | | Protocol version | 2025-11-25 | | Server | Chainstack 1.12.0 | | Capabilities | experimental, logging, prompts, resources, tools, extensions | | Tools | 23 | | Resources | 2 | | Prompts | 0 | | Connected | 4 November 2026, 20:02 UTC | | Handshake time | 1,539 ms over 1 attempt | ### Tools listed 23 tools - get\_organization - get\_deployment\_options - list\_projects - create\_project - list\_nodes - get\_node - create\_node - get\_project - update\_project - delete\_project - update\_node - delete\_node - list\_node\_access\_rules - create\_node\_access\_rule - update\_node\_access\_rule - delete\_node\_access\_rule - set\_node\_access\_rules\_status - search\_docs - get\_doc\_page - get\_platform\_status - contact\_chainstack - request\_testnet\_funds - get\_chainstack\_pricing ### Connector log 2 connections on 4 November 2026, read-only methods only - 19:56:51Z https://mcp.chainstack.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1715 ms - 20:02:23Z https://mcp.chainstack.com/mcp sent initialize, notifications/initialized, tools/list, resources/list, prompts/list result verified (HTTP 200) 1539 ms ## Authentication | Auth type | No authentication | | --- | --- | ### The sign-in route, step by step 1. Send the handshake to `https://mcp.chainstack.com/mcp` over streamable-http. Servers on the 2026-07-28 revision answer `server/discover`; older servers answer `initialize`. 2. Send `tools/list`, then `resources/list` and `prompts/list` if the capabilities name them. 3. Send no token. The connector sent none and the server answered, so any MCP client can read this list. 4. Calling a tool is a separate step this directory never takes. See [OAuth for MCP: client ID metadata documents and dynamic registration](https://agentmcpdirectory.com/guides/oauth-for-mcp-cimd-dcr/) for how each route works. ## CLI No CLI is on record for Chainstack. The directory checks a package only where a source names one, so this is a floor: a company can ship a command line that no source read for this edition mentions. See [shipping a CLI agents can use](https://agentmcpdirectory.com/guides/ship-a-cli-for-agents/). ## Other agent surfaces | Surface | Result | | --- | --- | | OpenAPI file | The request failed. | | WebMCP in the initial HTML | Not checked: the home page was not read by the shared crawl. | | MCP discovery file | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card | Not checked: the domain is not in the shared crawl for this edition. | | A2A agent card (older path) | Not checked: the domain is not in the shared crawl for this edition. | | agents.json | Not checked: the domain is not in the shared crawl for this edition. | | OAuth authorization server metadata | Not checked: the domain is not in the shared crawl for this edition. | | NLWeb endpoint | Not checked in this edition. | ## Registry listings | Registry | Listed | | --- | --- | | Official MCP Registry | Yes: com.chainstack/chainstack | | GitHub MCP Registry | Yes | | awesome-remote-mcp-servers | No | | Smithery | Not checked: Smithery's listing pages and search API were unavailable on 4 November 2026. | | Glama | Not checked: Glama's API needs a key and attribution terms. | Edition 4 November 2026 Method [How rows are verified](https://agentmcpdirectory.com/method/) Data [CSV and JSON](https://agentmcpdirectory.com/data/) Markdown [This page as markdown](https://agentmcpdirectory.com/directory/chainstack-com/index.md) ## Sources - [Ora score page for chainstack.com](https://ora.ai/score/chainstack.com?utm_source=agentmcpdirectory.com&utm_medium=referral&utm_campaign=entry), read 5 November 2026 (vendor-published score, scanned 24 August 2026, read from GET /api/score) - [Official MCP Registry search](https://registry.modelcontextprotocol.io/v0/servers?search=chainstack), read 4 November 2026 - [Chainstack website](https://chainstack.com), read 4 November 2026 - [Official MCP Registry API, the registry read for this edition](https://registry.modelcontextprotocol.io/v0/servers), read 4 November 2026 Last reviewed 5 November 2026