Anthid
REMOTE · MCP.ANTHID.COM · SCANNED AUG 7
Search the Anthid trading API reference, schemas, and product pages.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 760 tokens (~108/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.anthid.com
claude mcp add --transport http com-anthid-anthid https://mcp.anthid.com/mcp
[mcp_servers.com-anthid-anthid] url = "https://mcp.anthid.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-anthid-anthid": {
"type": "remote",
"url": "https://mcp.anthid.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-anthid-anthid --url https://mcp.anthid.com/mcp --transport streamable-http
mcp_servers:
com-anthid-anthid:
url: "https://mcp.anthid.com/mcp" {
"mcpServers": {
"com-anthid-anthid": {
"type": "http",
"url": "https://mcp.anthid.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 7 Aug 26 +1
- Tool “search_anthid_site” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 6 Aug 26 62
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 7 Aug 2026 · Probed https://mcp.anthid.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=anthid.com | CN=WE1,O=Google Trust Services,C=US | 20 Jul 2026 | 18 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | b3a0d183e0a5a26113dd3ce23a2838d1 |
| SANs: anthid.com, *.anthid.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC secure
Validation of mcp.anthid.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| anthid.com. | present | 2371 | 13 | Verified |
| mcp.anthid.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.anthid.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.anthid.com/mcp | HTTPS enforced | 301 | https://mcp.anthid.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
describe_anthid_endpoint Describe an Anthid API endpoint ~124
Return the full reference for one endpoint: the authentication it accepts, every parameter with its type and example, the request body schema and example, and the response examples. Read this before writing a request rather than inferring the shape. Accepts a path ("/v1/orders"), a signature ("POST /v1/intents"), or an operation id ("submitIntent").
| Name | Type | Req | Description |
|---|---|---|---|
| endpoint | string | yes | The path, signature, or operation id to describe. |
| method | string | – | HTTP method, when the endpoint is given as a bare path that serves several. |
No output schema declared.
No examples provided.
get_anthid_api_schema Get an Anthid API schema ~69
Return one named schema from the API reference with its references expanded — for example "SubmitIntentParams" or "OrdersResponse". Use this when an endpoint description names a schema you need in full.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The schema name, as it appears in the endpoint description. |
No output schema declared.
No examples provided.
get_anthid_overview Anthid overview ~58
Return the positioning overview for Anthid: what the platform does, what it replaces, who it is for, and where to go for implementation detail. Use this to answer "what is Anthid" before reaching for a search.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_anthid_endpoints List Anthid API endpoints ~65
List every documented endpoint grouped by service, with its method, path, and summary. Use this to see the shape of the API before searching it.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | – | Restrict the listing to one service, for example "ledger" or "controls". |
No output schema declared.
No examples provided.
list_anthid_pages List Anthid site pages ~41
List every public page on anthid.com with its title, description, and URL. Use this to find the right page to cite or to fetch.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_anthid_api Search the Anthid API ~113
Search the Anthid REST API reference and return matching endpoints with their method, path, and summary. Use this to find which endpoint does something — "submit an order", "list positions", "set a risk control". Follow a match with describe_anthid_endpoint to get its parameters and examples.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of endpoints to return. Defaults to 5. |
| query | string | yes | What the endpoint should do, for example "place an order" or "position history". |
No output schema declared.
No examples provided.
search_anthid_site Search the Anthid site ~156
Search anthid.com — the product, pricing, and company pages — and return matching excerpts with their URLs. Use this for questions about what Anthid is, what it costs, which brokers it connects, or how to get in touch. For endpoints, parameters, and payload schemas, use this server's API tools — search_anthid_api and describe_anthid_endpoint. For narrative guides and streaming client code, which neither corpus here carries, use the documentation MCP server at https://docs.anthid.com/mcp.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of pages to return. Defaults to 5. |
| query | string | yes | Search terms, for example "pricing free tier" or "which brokers". |
No output schema declared.
No examples provided.