Canarics MCP server
com.canarics/canaricscanarics.comstreamable-httpv1.0.1Scanned
AI call analysis and voice agents for sales teams. Signup, usage, agents and call data over MCP.
2 tools: 2 change things.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
2 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Canarics MCP server can do
The Canarics MCP server is published by canarics.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (2 tools: start_signup and check_signup_status), but cannot delete data. None of its tools only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (credentials-mention and annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 12, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
2 tools
Changes things 2Claude Code: ask
check_signup_statusFollow a signup started with start_signup.1 finding
Why it is in this group
- The name "check_signup_status" says "status": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "check_signup_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_signup_status" says "status": a word for reading.
Description, as the server wrote it Follow a signup started with start_signup. Poll slowly — the human step takes minutes. Once the person has claimed the link and the trial is live, this returns a one-time read-only Canarics API key for the new team: store it and use it as the Bearer key on this same MCP endpoint (and /api/v1) from then on.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
start_signupBegin setting up Canarics (AI voice agents + call analysis) for a company that has no account yet.1 finding
Why it is in this group
- The name "start_signup" says "start": a word for a change.
Findings
- Info
The description mentions "credentials".
What this check looks forMatched text
description: "...er ask for or collect a password or any credentials in chat: identity is verified entirely..."
Description, as the server wrote it Begin setting up Canarics (AI voice agents + call analysis) for a company that has no account yet. Returns a claim URL: ALWAYS show that URL to the person immediately and verbatim — it is useless sitting in your context; they open it, sign in, verify their phone by SMS and accept the terms; the trial then provisions itself with a demo AI agent generated from the company website. Keep the returned intentToken to follow progress with check_signup_status. All other Canarics tools need the API key that check_signup_status hands you after the claim. GROUNDING: companyName and website must come from what the person actually told you in this conversation — if either is missing, ask for it; never guess, never use placeholders like "New Company" or example.com. Never ask for or collect a password or any credentials in chat: identity is verified entirely on the claim link.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://canarics.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://canarics.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://canarics.com/mcp: tools/list returned 2 tools to an anonymous client, including start_signup (write), check_signup_status (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "check_signup_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_signup_status" says "status": a word for reading.
- Infostart_signup
The description mentions "credentials".
What this check looks forMatched text
description: "...er ask for or collect a password or any credentials in chat: identity is verified entirely..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http canarics https://canarics.com/mcpclaude mcp add --transport http canarics https://canarics.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [],
"ask": [
"mcp__canarics__start_signup",
"mcp__canarics__check_signup_status"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as canarics. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.canarics/canarics/verify?hash=ac821937bf5df2ccd70a8a2d481df9eb97ed52bc8cbd6fc1bb491e68edb6d70f" | jq -e '.changed == false'Pinned hash ac821937bf5d, from Nov 12, 2026, 20:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.canarics/canarics/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.canarics/canarics)Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.
Canarics MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Canarics MCP server safe?
- No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Canarics MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Canarics MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Canarics MCP server have?
- 2 tools: 2 write. start_signup and check_signup_status.
Does the Canarics MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Canarics MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Canarics MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.