MCP QUEEN
com.catchintent/catchintent A
The intent layer for B2B outbound. Find, triage, and act on warmth-scored leads.
Otherv2.0.0streamable-httpengine.catchintent.com
Grade evidence — probed 2026-07-12 23:15 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 74ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo catchintent@2.0.0 |
| tooling | 35 / 35 | tools/list OK: 14 tools e.g. "lead_search"; 14/14 described, 14/14 fully-typed schemas, median description 192 chars |
| latency | 10 / 10 | initialize round-trip 74ms |
| provenance | 12 / 15 | description present; no repository URL; version 2.0.0; namespace com.catchintent matches endpoint/repo |
Score 97/100 · latency 74ms · 14 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http catchintent https://engine.catchintent.com/mcp
Generic MCP client config:
{ "mcpServers": { "catchintent": { "type": "http", "url": "https://engine.catchintent.com/mcp" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.catchintent/catchintent · referral link https://mcpqueen.com/go/com.catchintent/catchintent (counts as “routed via the queen”).
Own this server? Embed your grade badge
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.catchintent/catchintent)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Queen Watch
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
Probe history
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-12 23:15 | A | 97 | 74ms |