io.github.disclose/lookup-disclose-io
REMOTE · LOOKUP.DISCLOSE.IO · SCANNED SEP 21
Find the right security-disclosure contact for any internet asset (domain, IP, package, repo, app).
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 239 tokens (~119/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.disclose/lookup-disclose-io MCP server?
io.github.disclose/lookup-disclose-io is a hosted endpoint at https://lookup.disclose.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · lookup.disclose.io
claude mcp add --transport http disclose-lookup-disclose-io 'https://lookup.disclose.io/mcp'
{
"mcpServers": {
"disclose-lookup-disclose-io": {
"url": "https://lookup.disclose.io/mcp"
}
}
} {
"servers": {
"disclose-lookup-disclose-io": {
"type": "http",
"url": "https://lookup.disclose.io/mcp"
}
}
} [mcp_servers.disclose-lookup-disclose-io] url = "https://lookup.disclose.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"disclose-lookup-disclose-io": {
"type": "remote",
"url": "https://lookup.disclose.io/mcp",
"enabled": true
}
}
} openclaw mcp add disclose-lookup-disclose-io --url 'https://lookup.disclose.io/mcp' --transport streamable-http
mcp_servers:
disclose-lookup-disclose-io:
url: "https://lookup.disclose.io/mcp" {
"McpServers": {
"disclose-lookup-disclose-io": {
"Transport": "http",
"Url": "https://lookup.disclose.io/mcp"
}
}
} assistant mcp add disclose-lookup-disclose-io -t streamable-http -u 'https://lookup.disclose.io/mcp'
{
"mcpServers": {
"disclose-lookup-disclose-io": {
"type": "http",
"url": "https://lookup.disclose.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 −1
- Schema quality: excellent → good functional
- “classify_asset” added an optional parameter “asset_type” cosmetic
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://lookup.disclose.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=disclose.io | CN=WE1,O=Google Trust Services,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | e43aee8233216cfa0e3aada1dc314318 |
| SANs: disclose.io, *.disclose.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of lookup.disclose.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| disclose.io. | present | 2371 | 13 | Verified |
| lookup.disclose.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://lookup.disclose.io/mcp | Verified | 200 | |
| http (plaintext) | http://lookup.disclose.io/mcp | HTTPS enforced | 301 | https://lookup.disclose.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
classify_asset Asset Type Classifier ~75
Classify an input as a domain, IP, package, repository, etc. No network calls — instant response. Useful for understanding what an asset is before performing a full lookup.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_type | string | – | Interpret as this asset type, preserving the same normalization as lookup. |
| input | string | yes | The input to classify |
No output schema declared.
No examples provided.
lookup_security_contact Security Contact Lookup ~164
Find security reporting channels for responsible vulnerability disclosure. Takes a domain, IP, URL, package name, repository, container image, mobile app, hardware device, browser extension, desktop app, or organization name. Returns bug bounty programs, security.txt contacts, VDP links, abuse contacts, and national/global CERT fallbacks ordered by applicability to the queried owner and asset. This is informational only — not legal advice.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | The asset to look up. Examples: "cloudflare.com", "8.8.8.8", "npm:express", "gh:facebook/react", "app:WhatsApp", "hw:Cisco ASA 5505" |
| asset_type | string | – | Force a specific asset type. Auto-detected if omitted. |
No output schema declared.
No examples provided.
What is the io.github.disclose/lookup-disclose-io MCP server?
io.github.disclose/lookup-disclose-io is an MCP server listed in the public MCP registry as io.github.disclose/lookup-disclose-io. Find the right security-disclosure contact for any internet asset (domain, IP, package, repo, app). This page covers its hosted endpoint (https://lookup.disclose.io/mcp).
Is the io.github.disclose/lookup-disclose-io MCP server safe to use?
io.github.disclose/lookup-disclose-io scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.disclose/lookup-disclose-io MCP server expose?
io.github.disclose/lookup-disclose-io exposes 2 tools: lookup_security_contact, classify_asset. Their descriptions and schemas cost roughly 239 tokens of context every time the server is loaded.
Does the io.github.disclose/lookup-disclose-io MCP server require authentication?
No. We connected to io.github.disclose/lookup-disclose-io without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.disclose/lookup-disclose-io MCP server still maintained?
io.github.disclose/lookup-disclose-io is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.