Person lookup from email: name, title, company, social profiles. x402.
Dev & Codev1.1.0sseperson-enrichment.api.klymax402.com repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 1143ms |
| protocol | 8 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo person-enrichment@1.0.0 — registry declares deprecated 'sse' transport |
| tooling | 35 / 35 | tools/list OK: 2 tools e.g. "person_enrich_from_email"; 2/2 described, 2/2 fully-typed schemas, median description 1567 chars |
| latency | 7 / 10 | initialize round-trip 1143ms |
| provenance | 15 / 15 | description present; repository linked; version 1.1.0; namespace io.github.Br0ski777 matches endpoint/repo |
Score 90/100 · latency 1143ms · 2 tools · auth: open
Claude Code:
claude mcp add --transport http person-enrichment https://person-enrichment.api.klymax402.com/mcp
Generic MCP client config:
{ "mcpServers": { "person-enrichment": { "type": "http", "url": "https://person-enrichment.api.klymax402.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/io.github.Br0ski777/person-enrichment · referral link https://mcpqueen.com/go/io.github.Br0ski777/person-enrichment (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.Br0ski777/person-enrichment)
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.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 14:01 | A | 90 | 1143ms |