5.5M verified entities, 10 countries, 13 tools. EU VAT, BORME, GLEIF, KYB. Free 100/mo.
Dev & Codev4.3.2streamable-httpmcp.entia.systems repository
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 25ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2024-11-05, serverInfo entia-mcp-ts@1.1.1-worker |
| tooling | 35 / 35 | tools/list OK: 13 tools e.g. "entity_lookup"; 13/13 described, 13/13 fully-typed schemas, median description 141 chars |
| latency | 10 / 10 | initialize round-trip 25ms |
| provenance | 8 / 15 | description present; repository linked; version 4.3.2; namespace io.github.entia-systems-core does NOT match remote host (expected *.entia-systems-core.github.io) |
Score 93/100 · latency 25ms · 13 tools · auth: open
Claude Code:
claude mcp add --transport http entity-verification https://mcp.entia.systems/mcp
Generic MCP client config:
{ "mcpServers": { "entity-verification": { "type": "http", "url": "https://mcp.entia.systems/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.entia-systems-core/entity-verification · referral link https://mcpqueen.com/go/io.github.entia-systems-core/entity-verification (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.entia-systems-core/entity-verification)
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-14 00:45 | A | 93 | 25ms |