Facts before confidence.

How to read a report

Measured by FrontierMCP: reachability, MCP protocol, authentication challenge, public tool count and latency.

Estimated by FrontierMCP: client fit based on published configuration requirements. “Likely compatible” is not a manual test inside that client.

Provided by the MCP publisher: tool names, descriptions, schemas and annotations. This content can be written in any language and is shown unchanged, repliable and explicitly labelled.

What we test

FrontierMCP checks public HTTPS Streamable HTTP endpoints, observes the MCP protocol version, reads public tools/list pages, records authentication challenges and compares snapshots over time.

What we never do

We never collect credentials, follow redirects to private networks, execute third-party code or call your tools. Descriptions and schemas are untrusted data.

Limits

A protected server may expose only its authentication surface. “Unknown” means not observable without authentication; it does not mean broken.