MCP Canary
REMOTE · API.MCPCANARY.COM
Inspect any remote MCP server: transport, protocol, tools, and side-effect hints. No tool calls.
Available components
Last scanned (2 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Monitoring and Observability
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 → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 348 tokens (~174/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management9
- Stability check failed: schema churn in the 12 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 −4
- Stability: 0.33 → fail ▼ security
- A breaking change shipped without a version bump: still 1.0.0 ▼ security
- Tool “inspect_endpoint” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- “inspect_endpoint” changed the type of “url”: string → string|null ▼ functional
- “inspect_endpoint” added an optional parameter “website” cosmetic
- “inspect_endpoint” reworded the description of “headers” cosmetic
- “inspect_endpoint” reworded the description of “url” cosmetic
- “inspect_endpoint” made “url” optional cosmetic
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
- Tool “inspect_endpoint” rewrote its description, which is the text the model reads security
- Schema quality: 119 → 133 ▼ functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 24 Oct 26 70
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 5 Nov 2026 · Probed https://api.mcpcanary.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.mcpcanary.com | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6b7fc77687fffd1d9248a32de074d66fe89 |
| SANs: api.mcpcanary.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcpcanary.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mcpcanary.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcpcanary.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.mcpcanary.com/mcp | HTTPS enforced | 301 | https://api.mcpcanary.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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_pricing Get MCP Canary pricing ~40
MCP Canary plans, monthly prices (in cents), and limits, plus the free trial. The trial needs no payment and starts on the first monitor write.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | yes | – |
| plans | array | yes | – |
| trial | object | yes | – |
No examples provided.
inspect_endpoint Inspect MCP endpoint ~252
Connects to a remote MCP endpoint (Streamable HTTP, then legacy SSE), lists its tools, and classifies each tool's side effects from its MCP hints. Never calls a tool on the target. agent_readiness lists what is wrong with the tool definitions and protocol compliance of the target, each with a fix, and a grade A-F. A target problem is status=failed with a stable failure code (e.g. TARGET_UNAVAILABLE, TARGET_AUTH_FAILED, MCP_PROTOCOL_ERROR). Private and loopback addresses are rejected. Set website (not url) to inspect a web page whose JavaScript registers WebMCP tools: the page is opened in a browser; the result has transport=webmcp.
| Name | Type | Req | Description |
|---|---|---|---|
| headers | object|null | – | Optional HTTP headers for the target, e.g. Authorization. Sent to the target only, never stored. Not with website. |
| url | string|null | – | Absolute http or https URL of the MCP endpoint, e.g. https://mcp.deepwiki.com/mcp. Set url or website. |
| website | string|null | – | Absolute http or https URL of a web page with WebMCP tools, e.g. a Shopify storefront. Set url or website. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_readiness | object|null | – | – |
| duration_ms | integer | yes | – |
| endpoint | string | yes | – |
| failure | object|null | yes | – |
| instructions | string|null | – | – |
| protocol | string|null | yes | – |
| server | object|null | yes | – |
| status | string | yes | – |
| tools | array | yes | – |
| transport | string|null | yes | – |
No examples provided.
How do I install the MCP Canary server?
MCP Canary is a hosted endpoint at https://api.mcpcanary.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcpcanary.com
claude mcp add --transport http com-mcpcanary-inspect 'https://api.mcpcanary.com/mcp'
What is the MCP Canary server?
MCP Canary is listed in the public MCP registry as com.mcpcanary/inspect. Inspect any remote MCP server: transport, protocol, tools, and side-effect hints. No tool calls. This page covers its hosted endpoint (https://api.mcpcanary.com/mcp).
Is the MCP Canary server safe to use?
MCP Canary scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Canary server expose?
MCP Canary exposes 2 tools: get_pricing, inspect_endpoint. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.
Does the MCP Canary server require authentication?
No. We connected to MCP Canary without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Canary server still maintained?
MCP Canary is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.