MCP Server

Anthid publishes a Model Context Protocol server at https://mcp.anthid.com/mcp. It exposes two things as tools an MCP client can call: the REST API reference, generated from the live services, and the public anthid.com site. An assistant connected to it answers from the current reference rather than from memory, and writes requests against the parameters and examples the API actually documents.

Access

The server requires no authentication. It serves published reference material and holds no account data, so there is no API key to configure and no organization scoping.

The API tools describe the API; they do not call it. Requests still go to https://api.anthid.com with your own credentials. See Introduction for how those are sent.

Browser clients are restricted by CORS to https://anthid.com. MCP clients that are not browsers are unaffected.

Transport

Streamable HTTP, one JSON-RPC request per request body.

Property	Value
Endpoint	`https://mcp.anthid.com/mcp`
Method	`POST`
Protocol version	`2025-06-18`
Batch requests	Not supported

A GET to the endpoint returns 405. The server offers no server-initiated stream, which the specification permits.

Connecting

Claude Code:

claude mcp add --transport http anthid https://mcp.anthid.com/mcp

Clients configured through JSON:

{
  "mcpServers": {
    "anthid": {
      "type": "http",
      "url": "https://mcp.anthid.com/mcp"
    }
  }
}

API tools

Tool	Arguments	Returns
`search_anthid_api`	`query` (required), `limit` (optional, 1–20, default 5)	Matching endpoints with method, path, and summary
`describe_anthid_endpoint`	`endpoint` (required), `method` (optional)	One endpoint in full: auth, parameters, request body, examples
`get_anthid_api_schema`	`name` (required)	One named schema with its references expanded
`list_anthid_endpoints`	`service` (optional)	Every documented endpoint, grouped by service

search_anthid_api

Finds the endpoint for a task — “submit an order”, “position history”, “set a risk control”. Ranks on summary, path, and operation ID above the prose, so the endpoint that does the thing outranks one that merely mentions it.

describe_anthid_endpoint

The tool to reach for before writing a request. Returns the security schemes the operation accepts, every parameter with its type and example, the request body schema with references expanded, and the response examples. Accepts three forms, because clients reliably use all three:

/v1/orders            a path
POST /v1/intents      a signature
submitIntent          an operation ID

A bare path served by several methods returns the choices rather than guessing one. Pass method to disambiguate directly.

get_anthid_api_schema

Returns a named schema — SubmitIntentParams, OrdersResponse — with $refs expanded. Use it when an endpoint description names a schema you need in full. A misspelled name returns near matches.

list_anthid_endpoints

The whole API surface, grouped by service. Pass service to narrow to one: accounts, connections, controls, intents, ledger, or organizations.

Tool	Arguments	Returns
`search_anthid_site`	`query` (required), `limit` (optional, 1–20, default 5)	Matching pages as excerpts with their URLs
`get_anthid_overview`	None	The positioning overview for the platform
`list_anthid_pages`	None	Every public page with its title, description, and URL

Methods

Method	Behavior
`initialize`	Returns the protocol version, tool capabilities, and server instructions
`ping`	Returns an empty result
`tools/list`	Returns the tool catalog with input schemas
`tools/call`	Runs one tool and returns its text content

Notifications receive 202 with no body. An unknown method returns -32601.

Example

curl https://mcp.anthid.com/mcp \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "describe_anthid_endpoint",
      "arguments": {
        "endpoint": "submitIntent"
      }
    }
  }'

Content freshness

The server reads its two corpora from the published sites rather than embedding them: the API reference from this documentation site, the page content from anthid.com. Both are cached for five minutes. A schema change reaches the server on the next docs deploy, and site copy on the next marketing deploy — neither needs a release of the server itself. If one origin is unreachable the server serves its last good copy rather than failing, and the tools for the other corpus are unaffected.

Support

For questions about connecting a client or the tools returned, contact support@anthid.com.

Connections

Organizations

Controls

Accounts

Intents

Ledger

Stream

MCP

Access

Transport

Connecting

API tools

search_anthid_api

describe_anthid_endpoint

get_anthid_api_schema

list_anthid_endpoints

Site tools

search_anthid_site

get_anthid_overview

list_anthid_pages

Methods

Example

Content freshness

Support

​Access

​Transport

​Connecting

​API tools

​search_anthid_api

​describe_anthid_endpoint

​get_anthid_api_schema

​list_anthid_endpoints

​Site tools

​search_anthid_site

​get_anthid_overview

​list_anthid_pages

​Methods

​Example

​Content freshness

​Support

Access

Transport

Connecting

API tools

search_anthid_api

describe_anthid_endpoint

get_anthid_api_schema

list_anthid_endpoints

Site tools

search_anthid_site

get_anthid_overview

list_anthid_pages

Methods

Example

Content freshness

Support