Find the right security-disclosure contact for any internet asset (domain, IP, package, repo, app).
Dev & Codev2.0.1streamable-httplookup.disclose.io
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 388ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo lookup-disclose-io@2.0.0 |
| tooling | 35 / 35 | tools/list OK: 2 tools e.g. "lookup_security_contact"; 2/2 described, 2/2 fully-typed schemas, median description 401 chars |
| latency | 10 / 10 | initialize round-trip 388ms |
| provenance | 5 / 15 | description present; no repository URL; version 2.0.1; namespace io.github.disclose does NOT match remote host (expected *.disclose.github.io) |
Score 90/100 · latency 388ms · 2 tools · auth: open
Claude Code:
claude mcp add --transport http lookup-disclose-io https://lookup.disclose.io/mcp
Generic MCP client config:
{ "mcpServers": { "lookup-disclose-io": { "type": "http", "url": "https://lookup.disclose.io/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.disclose/lookup-disclose-io · referral link https://mcpqueen.com/go/io.github.disclose/lookup-disclose-io (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/io.github.disclose/lookup-disclose-io)
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:15 | A | 90 | 388ms |