MCP QUEEN
com.senzing/mcp A
Entity resolution — data mapping, SDK code generation, docs search, and error troubleshooting
Dev & Codev1.28.5streamable-httpmcp.senzing.com
Grade evidence — probed 2026-07-13 06:45 UTC
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 257ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-03-26, serverInfo rmcp@1.7.0 |
| tooling | 34 / 35 | tools/list OK: 13 tools e.g. "analyze_record"; 13/13 described, 12/13 fully-typed schemas, median description 667 chars |
| latency | 10 / 10 | initialize round-trip 257ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.28.5; namespace com.senzing matches endpoint/repo |
Score 96/100 · latency 257ms · 13 tools · auth: open
Connect your agent
Claude Code:
claude mcp add --transport http mcp https://mcp.senzing.com/mcp
Generic MCP client config:
{ "mcpServers": { "mcp": { "type": "http", "url": "https://mcp.senzing.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.senzing/mcp · referral link https://mcpqueen.com/go/com.senzing/mcp (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.senzing/mcp)
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-13 06:45 | A | 96 | 257ms |