Model Context Protocol streamable-HTTP transport
Exposes the lookup tools as an MCP server over streamable HTTP per the Model Context Protocol spec. Stateless mode. Authentication is optional and uses the same Bearer/X-API-Key tiers as REST. See https://modelcontextprotocol.io for the wire protocol.
Tools:
- lookup_security_contact — full lookup; returns a Markdown summary (content[0].text) plus the structured LookupResult (structuredContent), identical to POST /api/lookup.
- classify_asset — instant asset-type classifier, no network.
Clients must send Accept: application/json, text/event-stream. Add to Claude Code in one line: claude mcp add --transport http lookup https://lookup.disclose.io/mcp or point any URL-based MCP client at https://lookup.disclose.io/mcp.
Request
- Base URL: https://lookup.disclose.io
- URL: https://lookup.disclose.io/mcp
- Auth: one of:
- none
- HTTP bearer
- API key in header X-API-Key
Headers
Caller-supplied request identifier. Must match ^[A-Za-z0-9._:-]+$ and be at most 128 characters. Replaced with a server-generated req_<uuid> if absent or malformed. Echoed on every response.
Must be application/json, text/event-stream for the streamable-HTTP transport.
Stable opaque browser/client identifier used only to give individual users a fair new-work allowance behind shared NATs. Must be 20–128 characters from A-Z a-z 0-9 . _ : -. Create once and persist; do not rotate per request. Missing or malformed values fall back to IP policy. API-key requests use their key quota instead.
Request body
JSON-RPC 2.0 envelope per the MCP spec.
Response
MCP response (streamable).
Changes
No recorded changes to this operation across all 1 revision of this API.