com.catchintent/catchintent
REMOTE · ENGINE.CATCHINTENT.COM · SCANNED SEP 20
The intent layer for B2B outbound. Find, triage, and act on warmth-scored leads.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 978 tokens (~69/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "product_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.catchintent/catchintent MCP server?
com.catchintent/catchintent is a hosted endpoint at https://engine.catchintent.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · engine.catchintent.com
claude mcp add --transport http com-catchintent-catchintent 'https://engine.catchintent.com/mcp'
{
"mcpServers": {
"com-catchintent-catchintent": {
"url": "https://engine.catchintent.com/mcp"
}
}
} {
"servers": {
"com-catchintent-catchintent": {
"type": "http",
"url": "https://engine.catchintent.com/mcp"
}
}
} [mcp_servers.com-catchintent-catchintent] url = "https://engine.catchintent.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-catchintent-catchintent": {
"type": "remote",
"url": "https://engine.catchintent.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-catchintent-catchintent --url 'https://engine.catchintent.com/mcp' --transport streamable-http
mcp_servers:
com-catchintent-catchintent:
url: "https://engine.catchintent.com/mcp" {
"McpServers": {
"com-catchintent-catchintent": {
"Transport": "http",
"Url": "https://engine.catchintent.com/mcp"
}
}
} assistant mcp add com-catchintent-catchintent -t streamable-http -u 'https://engine.catchintent.com/mcp'
{
"mcpServers": {
"com-catchintent-catchintent": {
"type": "http",
"url": "https://engine.catchintent.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://engine.catchintent.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=catchintent.com | CN=WE1,O=Google Trust Services,C=US | 7 Aug 2026 | 5 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 89a181629d6a46b113b102bbd42314ce |
| SANs: catchintent.com, *.catchintent.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of engine.catchintent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| catchintent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://engine.catchintent.com/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://engine.catchintent.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';font-src 'self' https: data:;form-action 'self';frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Protected resource metadata
| Document | https://engine.catchintent.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://engine.catchintent.com/mcp |
| Authorisation server | https://engine.catchintent.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://engine.catchintent.com/mcp | Verified | 200 | |
| http (plaintext) | http://engine.catchintent.com/mcp | HTTPS enforced | 301 | https://engine.catchintent.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lead_enrich ~36
Trigger full LinkedIn profile enrichment via Apify (~$0.002, idempotent).
| Name | Type | Req | Description |
|---|---|---|---|
| leadId | string | yes | – |
No output schema declared.
No examples provided.
lead_get ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| leadId | string | yes | – |
No output schema declared.
No examples provided.
lead_push_to_crm ~78
Push leads to your connected CRM (HubSpot, Close, Pipedrive, Zoho). Each lead becomes a contact / deal in the destination. Lead status does not change automatically — call lead_update_status to mark as `pushed` once CRM confirms.
| Name | Type | Req | Description |
|---|---|---|---|
| leadIds | array | yes | – |
| provider | string | – | – |
No output schema declared.
No examples provided.
lead_regenerate_sequence ~59
Re-draft the lead's AI outreach sequence (LinkedIn/X steps). Optional instructions steer the rewrite. Capped per lead — edit directly once the cap is hit.
| Name | Type | Req | Description |
|---|---|---|---|
| instructions | string | – | – |
| leadId | string | yes | – |
No output schema declared.
No examples provided.
lead_search ~86
Search leads in the workspace. A lead is always a person discovered on LinkedIn. Filter by warmth, status, or text.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | – |
| pageSize | integer | – | – |
| productId | string | – | – |
| search | string | – | – |
| status | array | – | – |
| warmth | array | – | – |
| workflowTag | array | – | – |
No output schema declared.
No examples provided.
lead_update_sequence ~41
Replace the lead's outreach sequence steps with edited versions (marks the sequence as edited).
| Name | Type | Req | Description |
|---|---|---|---|
| leadId | string | yes | – |
| steps | array | yes | – |
No output schema declared.
No examples provided.
lead_update_status ~93
Move a lead through the triage funnel. Valid transitions: NEW → SEEN/SAVED/PUSHED/ARCHIVED, SEEN ↔ SAVED, SAVED → PUSHED/ARCHIVED, PUSHED → ARCHIVED, ARCHIVED → SEEN. PUSHED is irreversible — it marks handoff to an outreach tool / CRM.
| Name | Type | Req | Description |
|---|---|---|---|
| leadId | string | yes | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
product_create ~132
Create a new product. You can set sell (name/description/keywords/competitors), the structured offer, voice, and reach (roles/seniority/functions). Company firmographics (industries/size/country) are set in the dashboard, not here. Brand fields are optional and can be filled later via product_update.
| Name | Type | Req | Description |
|---|---|---|---|
| competitors | array | – | – |
| description | string | – | – |
| domain | string | – | – |
| icp | object | – | – |
| keywords | array | – | – |
| name | string | yes | – |
| offer | object | – | – |
| voice | object | – | – |
No output schema declared.
No examples provided.
product_delete ~38
Delete a product. Fails only if it's the workspace's only product. Its audience and leads cascade-delete.
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | – |
No output schema declared.
No examples provided.
product_get ~79
Resolved brand profile for a product, returned as nested sections with human-readable labels: sell (name/description/keywords/competitors/offer), fit (company firmographics), reach (roles/seniority/functions), plus offer, voice, and domain. Drives all AI scoring + outreach drafting for that product.
| Name | Type | Req | Description |
|---|---|---|---|
| productId | string | yes | – |
No output schema declared.
No examples provided.
product_list ~39
List every product/brand tracked by this workspace. Each product has its own brand profile, audience, and leads. Returns id, name, and timestamps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
product_update ~146
Update a product. Partial — only provided fields change. You can set sell (name/description/keywords/competitors), the structured offer, voice, and reach (roles/seniority/functions). Company firmographics (industries/size/country) are set in the dashboard, not here. Reach labels are resolved strictly to canonical IDs; unknown values rejected.
| Name | Type | Req | Description |
|---|---|---|---|
| competitors | array | – | – |
| description | string | – | – |
| domain | string | – | – |
| icp | object | – | – |
| keywords | array | – | – |
| name | string | – | – |
| offer | object | – | – |
| productId | string | yes | – |
| voice | object | – | – |
No output schema declared.
No examples provided.
workspace_icp_options ~58
Get the valid Seniority Level and Job Function labels for product targeting (the reach dimensions MCP can set; roles are free text). Call this before product_update — unknown labels are rejected, never silently dropped.
| Name | Type | Req | Description |
|---|---|---|---|
| field | string | – | – |
No output schema declared.
No examples provided.
workspace_usage ~35
Current workspace usage vs plan limits: leads delivered this billing period, team members, products, AI compute budget, daily/monthly caps.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the com.catchintent/catchintent MCP server?
com.catchintent/catchintent is an MCP server listed in the public MCP registry as com.catchintent/catchintent. The intent layer for B2B outbound. Find, triage, and act on warmth-scored leads. This page covers its hosted endpoint (https://engine.catchintent.com/mcp).
Is the com.catchintent/catchintent MCP server safe to use?
com.catchintent/catchintent scores 89 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.catchintent/catchintent MCP server expose?
com.catchintent/catchintent exposes 14 tools: lead_search, lead_get, lead_update_status, lead_regenerate_sequence, lead_update_sequence, and 9 more. Their descriptions and schemas cost roughly 978 tokens of context every time the server is loaded.
Does the com.catchintent/catchintent MCP server require authentication?
Yes. com.catchintent/catchintent asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the com.catchintent/catchintent MCP server still maintained?
com.catchintent/catchintent is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.