# CatchIntent ID: 05-catchintent Page: https://gtmmcps.com/tools/05-catchintent JSON: https://gtmmcps.com/data/tools/05-catchintent.json Documentation references: https://gtmmcps.com/docs/05-catchintent/ Category: Signals & Intent MCP support: official Testing: RESEARCHED API access: paid Last checked: 2026-09-07 Endpoint check: not-probed; date: Not recorded A B2B intent tool that monitors social and web sources for buying signals, ranks the people behind them by warmth, enriches the profiles and drafts personalised openers, then pushes leads to a CRM or outreach account. ## MCP links - https://engine.catchintent.com/mcp - https://catchintent.com/mcp - https://catchintent.com/changelog/ - https://github.com/CatchIntent/skills ## Sources - https://catchintent.com/mcp - https://catchintent.com/changelog/ - https://catchintent.com/pricing - https://engine.catchintent.com/mcp ## Research notes Verified 2026-09-07: POST of an MCP initialize to https://engine.catchintent.com/mcp with no credentials returned HTTP 200 with a JSON-RPC result, serverInfo name "catchintent" version "2.0.0"; the control POST to /zzz-not-a-route returned 404 with a JSON body reading "Cannot POST /zzz-not-a-route". Live first-party server; initialize is open and the OAuth gate sits at tool-call time. The vendor's own MCP page says "28+ typed tools across six surfaces" while the v3.0.0 changelog line says "27 typed tools"; both vendor figures are recorded as found, not reconciled. The pricing page publishes plan sizes but no plan prices, so the api_gate is paid on the vendor's own statement that every plan is paid, with the amount unknown. The catchintent.com/mcp page is not linked from the homepage; it was reached via the registry listing that named the endpoint. 2026-09-07: https://engine.catchintent.com/mcp returned 200 with a JSON-RPC initialize result to an MCP initialize POST (https://engine.catchintent.com/mcp). 2026-09-12 (P6-04 repo sweep): first-party repository recorded at https://github.com/CatchIntent/skills - first-party agent skills that wire the hosted server, NOT the server source. Evidence: the org CatchIntent, whose profile site is catchintent.com, and whose README install line is "claude mcp add catchintent --transport http https://engine.catchintent.com/mcp", which is the endpoint this entry already records. ## Named capabilities Tool names below are reported by sources. Their presence is not a successful call. - lead_enrich: Trigger full LinkedIn profile enrichment via Apify (~$0.002, idempotent).; evidence: live-list; party: - lead_get: 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.; evidence: live-list; party: - lead_push_to_crm: 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.; evidence: live-list; party: - lead_regenerate_sequence: 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.; evidence: live-list; party: - lead_search: Search leads in the workspace. A lead is always a person discovered on LinkedIn. Filter by warmth, status, or text.; evidence: live-list; party: - lead_update_sequence: Replace the lead's outreach sequence steps with edited versions (marks the sequence as edited).; evidence: live-list; party: - lead_update_status: 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.; evidence: live-list; party: - product_create: 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 fi; evidence: live-list; party: - product_delete: Delete a product. Fails only if it's the workspace's only product. Its audience and leads cascade-delete.; evidence: live-list; party: - product_get: 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.; evidence: live-list; party: - product_list: List every product/brand tracked by this workspace. Each product has its own brand profile, audience, and leads. Returns id, name, and timestamps.; evidence: live-list; party: - product_update: 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 i; evidence: live-list; party: - workspace_icp_options: 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.; evidence: live-list; party: - workspace_usage: Current workspace usage vs plan limits: leads delivered this billing period, team members, products, AI compute budget, daily/monthly caps.; evidence: live-list; party: ## CLI evidence Status: none-found Read current vendor documentation before configuring or running commands.