MCP Exposure Context 1.3.0 FREE LIVE CHECKS

MCP exposure review

Know what an MCP connection exposes.

Enter an MCP server address to see what it may expose to an AI: whether sign-in is required, what data could be reached, and what actions the server offers—all before you connect it.

01 Discover the access boundary
02 Authorize only when required
03 Contextualize reach and action power
LIVE EXPOSURE CHECK FREE LIVE CHECKS

Assess an MCP connection

Add authentication For protected MCP endpoints Optional
One check

Only use a token issued for the MCP endpoint above. Paste the value without “Bearer”. It is sent in the Authorization header for this check and is not saved.

Free point-in-time assessment. Optional access tokens are used only to request the token-present tool catalog. We never call tools, and credentials, endpoints, and results are not saved.

01 / EVIDENCEServer responses, authorization metadata, and published or identity-visible tool definitions.
02 / COVERAGEExactly which surface was visible before or after authorization.
03 / UNKNOWNSRuntime behavior, backend enforcement, and actual tool use remain unobserved.

One bounded assessment

From endpoint to exposure context—without invoking a tool.

01

Discover

Open the HTTPS endpoint and identify its MCP and authorization boundaries.

02

Authorize

If the catalog is protected, add a short-lived bearer token you already hold for this one assessment.

03

Inventory

Request the published or identity-visible tool list for this connection. No resources. No tool calls.

04

Contextualize

Translate the evidence into coverage, likely reach, action power, and explicit unknowns.