Canarics

AI call analysis and voice agents for sales teams. Signup, usage, agents and call data over MCP.

Should I use this

Quality & Safety

A
Description quality
90%
Schema completeness
100%
Naming quality
100%
Poisoning risk
80%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool 'start_signup' description contains placeholder textin start_signup
  • INFOTool description contains placeholder or incomplete textin start_signup

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~542Tokens (tool definitions)
~1.3 KBTypical response size
Minimal attention impact (0.42% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "canarics": {
      "url": "https://salestick-backend-647994203646.europe-central2.run.app/mcp"
    }
  }
}

Remote endpoints

https://salestick-backend-647994203646.europe-central2.run.app/mcpstreamable-http
https://canarics.com/mcpstreamable-http

What it can do

Tool inventory

Tools (2)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢start_signup(companyName, website, language, contactEmail, notes)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "companyName": {
      "type": "string",
      "minLength": 2,
      "maxLength": 120,
      "description": "Company name."
    },
    "website": {
      "type": "string",
      "minLength": 1,
      "maxLength": 300,
      "description": "Company website URL — the demo AI agent is generated from it."
    },
    "language": {
      "description": "Preferred conversation/summary language (e.g. Latvian, English, German). Default English.",
      "type": "string"
    },
    "contactEmail": {
      "description": "Contact email of the person who will claim the signup.",
      "type": "string"
    },
    "notes": {
      "description": "Short context on the intended use case (max 500 chars).",
      "type": "string",
      "maxLength": 500
    }
  },
  "required": [
    "companyName",
    "website"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}
🟢check_signup_status(intentToken)

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.

Input Schema

{
  "type": "object",
  "properties": {
    "intentToken": {
      "type": "string",
      "description": "The intentToken returned by start_signup."
    }
  },
  "required": [
    "intentToken"
  ],
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools