Skip to content
Carragent logo

Carragent MCP server

Which MCP servers are Carragent's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to Carragent

Whose server it is
  • Registry namecom.carragent/carragentverified in the MCP registry

The registry name sits under carragent.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools4
  • Server calls itselfcarragent
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 123 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 1 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 1, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
  • Answeredmeasuring1 of the 7 daily checks it takes to print a share
  • Median first answer169 ms
  • Space in an agent's context≈ 470 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · Log supplier bills before their due dates
  • not sure · Send reminders for late customer invoices
  • not sure · Confirm customer bookings the day before

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers4 tools · read 2026-10-27
  • list_agents

    List every Carragent AI agent: what it does, when it runs, what waits for the owner's approval, what it never does and which tools (Stripe, Google Calendar, HubSpot…) it connects to. Use to answer 'what can Carragent do?'.

  • get_agent

    Get one agent by id (for example collections, scheduling, leads, reviews, report). Use after list_agents or search_carragent to give the details of one agent.

  • list_plans

    List the plans with monthly and yearly prices in USD cents (plus applicable taxes), their limits, the free-trial length and the refund terms. Use to answer 'how much does Carragent cost?'.

  • search_carragent

    Keyword search over Carragent's agents and plans, best match first. Use to find the agent for a task, such as 'chase late invoices' or 'confirm appointments'.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "carragent": {
      "type": "http",
      "url": "https://carragent.com/api/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http carragent https://carragent.com/api/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://carragent.com/api/mcp as a custom connector in the settings.

OpenAPI spec

11 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.