Inspect any remote MCP server: transport, protocol, tools, and side-effect hints. No tool calls.
Scored across 2 tools
The two tools serve completely different purposes: get_pricing returns plan and pricing information, while inspect_endpoint performs remote MCP endpoint inspection. There is no plausible confusion about which tool to select for a given task.
Both names use a consistent snake_case verb_noun pattern (get_pricing, inspect_endpoint). The convention is predictable and readable.
Two tools is thin for a server that appears to be a monitoring/canary service. Pricing plus inspection may cover a minimal surface, but additional lifecycle tools would be expected for the apparent scope.
The get_pricing description references a 'monitor write' and free trial, implying monitor management, but no tools exist to create, list, update, or delete monitors. The surface is severely limited for a canary/monitoring product, leaving agents unable to perform core lifecycle operations.
MCP Canary plans, monthly prices (in cents), and limits, plus the free trial. The trial needs no payment and starts on the first monitor write.
Inputs: no named parameters. Returns: plans, trial, currency
Connects to a remote MCP endpoint (Streamable HTTP, then legacy SSE), lists its tools, and classifies each tool's side effects from its MCP hints. Never calls a tool on the target. agent_readiness lists what is wrong with the tool definitions and protocol compliance of the target, each with a fix, and a grade A-F. A target problem is status=failed with a stable failure code (e.g. TARGET_UNAVAILABLE, TARGET_AUTH_FAILED, MCP_PROTOCOL_ERROR). Private and loopback addresses are rejected. Set website (not url) to inspect a web page whose JavaScript registers WebMCP tools: the page is opened in a browser; the result has transport=webmcp.
Inputs: url, headers, website. Returns: tools, server, status, failure, +6 more
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Check whether an MCP server answers, what its tools claim, and whether that claim has changed.
Check an MCP endpoint resolves: liveness, live tool list, schema drift. Free.
Free, read-only security scanner for remote MCP servers, before you connect them.
Score any remote MCP server for Claude, ChatGPT, Gemini and MCP Registry readiness.
Add one secure layer between your agents and this server.
