Check what an MCP endpoint actually returns.
An MCP link is a useful lead. A live response gives you more evidence. Start by checking whether the endpoint speaks the protocol, requires authentication and returns an understandable tool inventory.
What our checker does
The checker requests tool metadata from a public HTTPS endpoint. It tries a current per-request tool listing and can fall back to a supported legacy initialization flow. It reports the HTTP response, observation time, available inventory and missing basic descriptions or schema objects.
It does not send your account credentials, follow endpoint redirects, call discovered tools, resolve external schema references or perform a security audit. Authentication-required responses can be a normal property of a protected service.
Endpoint, documentation and website are different URLs
Use the publisher’s actual MCP endpoint, such as https://example.com/mcp. A homepage or a page explaining MCP is not necessarily an endpoint. Our directory’s MCP filter records publisher declarations; check the source before connecting.
Test the public interface before real actions
- Confirm the endpoint and transport in the publisher documentation.
- Inspect authentication and required permissions in your client.
- Read the returned tool names, descriptions and input schemas.
- Test a low-impact read in an authorized environment.
- Confirm the result against the underlying source before granting broader capabilities.
A valid schema object does not prove the tool behaves as described. Treat descriptions and annotations as claims and preserve the client’s normal approval boundaries for changes and transactions.
Current and older MCP revisions
MCP revisions differ in negotiation and request metadata. A server can expose useful tools while supporting a different revision from your client. Our report names a negotiated legacy version when available and leaves it unknown when the response does not establish one. Follow the current transport reference for your integration.
Find declared interfaces · Connect Agent Web Map · Understand browser tools
More: WebMCP: give agents a clearer way in. · Can AI find, understand and cite your website? · Agentic commerce needs evidence behind the interface. · Find the right documentation before using it. · The llms.txt project · What is llms.txt? · llms.txt examples · llms.txt best practices · checker · generator