mcp-registry/com.catchintent/catchintent · v2.0.0
As of 2026-10-19 12:20 UTC, the Catchintent MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 2 minutes.
The intent layer for B2B outbound. Find, triage, and act on warmth-scored leads.
Claude Code
claude mcp add --transport http catchintent-mcp-server https://engine.catchintent.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"catchintent-mcp-server": {
"type": "http",
"url": "https://engine.catchintent.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
37 parameter(s) across 12 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Handshake + tools/list takes ~1,862 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fcom.catchintent%2Fcatchintent/fixes
{
"name": "lead_get",
"description": "Get full details of one lead: profile, discovery context (fit reason, pain hypothesis, role signals, disqualifiers), the AI-drafted outreach sequence (lead.outreach), warmth score, and status.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"leadId"
],
"properties": {
"leadId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "lead_search",
"description": "Search leads in the workspace. A lead is always a person discovered on LinkedIn. Filter by warmth, status, or text.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"page": {
"type": "integer",
"default": 1,
"maximum": 9007199254740991,
"minimum": 1
},
"search": {
"type": "string",
"maxLength": 200
},
"status": {
"type": "array",
"items": {
"enum": [
"new",
"seen",
"saved",
"pushed",
"archived"
],
"type": "string"
}
},
"warmth": {
"type": "array",
"items": {
"enum": [
"hot",
"warm",
"cool"
],
"type": "string"
}
},
"pageSize": {
"type": "integer",
"default": 20,
"maximum": 200,
"minimum": 1
},
"productId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
},
"workflowTag": {
"type": "array",
"items": {
"type": "string"
}
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "lead_update_sequence",
"description": "Replace the lead's outreach sequence steps with edited versions (marks the sequence as edited).",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"leadId",
"steps"
],
"properties": {
"steps": {
"type": "array",
"items": {
"type": "object",
"required": [
"order",
"channel",
"purpose",
"delayDays",
"body"
],
"properties": {
"body": {
"type": "string"
},
"order": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": -9007199254740991
},
"channel": {
"type": "string"
},
"purpose": {
"type": "string"
},
"delayDays": {
"type": "integer",
"maximum": 9007199254740991,
"minimum": 0
}
}
},
"minItems": 1
},
"leadId": {
"type": "string",
"format": "uuid",
"pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$"
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.catchintent/catchintent"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/com.catchintent/catchintent"}) over MCP.
product_update ~526 tokensproduct_create ~450 tokenslead_search ~252 tokenslead_update_sequence ~241 tokenslead_push_to_crm ~207 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fcom.catchintent%2Fcatchintent?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fcom.catchintent%2Fcatchintent?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.catchintent%2Fcatchintent.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.catchintent%2Fcatchintent.svg :target: https://glimind.com/server/mcp-registry%2Fcom.catchintent%2Fcatchintent?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e1bbc89839c329b5…, first seen 2026-10-17, included at leaf 3131 of 26,655. Version history · verify what your client received.
Compare: most reliable data servers · most reliable crm servers · most reliable communication servers · most reliable search servers · most reliable productivity servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 12:20 UTC, the Catchintent MCP server is up with a Glimind reliability score of 89/100 (grade B). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 2 minutes.
Catchintent MCP server advertises 14 tools, including lead_enrich, lead_get, lead_push_to_crm, lead_regenerate_sequence, lead_search.
Point your MCP client at this streamable-http endpoint: https://engine.catchintent.com/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.