AI call analysis and voice agents for sales teams. Signup, usage, agents and call data over MCP.
Scored across 2 tools
The two tools have clearly distinct roles: start_signup initiates the signup flow and returns a claim URL, while check_signup_status polls for completion and returns the API key. There is no overlap or ambiguity between them.
Both tool names follow a consistent verb_noun snake_case pattern (start_signup, check_signup_status), making the set predictable and easy to navigate.
Only two tools are present, which is slightly below the typical 3-15 range, but the narrow scope of the signup/onboarding workflow justifies this small surface. Each tool is necessary and earns its place.
The signup lifecycle is fully covered: start_signup begins the process and returns tracking information, while check_signup_status completes it by delivering the API key once the trial is live. There are no missing steps for the stated purpose.
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.
Inputs: intentToken (required).
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.
Inputs: website (required), companyName (required), notes, language, +1 more.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
AI agent platform: manage leads, conversations, bots, calendar and CRM via MCP.
Phone, SMS and email for AI agents. One remote MCP endpoint, OAuth login, zero install.
Analytics your AI agent can actually use. Track, experiment, and optimize via MCP.
AI receptionist: calls, leads, credits, usage, workflows and guided setup via OAuth
Add one secure layer between your agents and this server.
