/inspect
A public trust page
for every remote MCP service.
Every service deployed through mcpctl automatically gets a public /inspect endpoint. Clients, operators, and evaluators can verify what's running — without needing console access or documentation that may be out of date.
What it looks like
Inspect at a glance.
Service
docs-assistant
Status
HealthyDeployed from
acme-org/docs-mcp @ main
PR #42 · merged 2h ago
Version
sha: a3f8c21
Tools exposed (3)
search_docs
Full-text search across documentation
get_page
Retrieve a specific documentation page by path
list_sections
List top-level documentation sections
Client validation evidence, when available
Example /inspect output — illustrative only. Fields and values reflect your actual deployed service.
What /inspect shows
The right amount of visibility.
Service health
Current status of the deployed service — reachable, degraded, or unhealthy — with a timestamp of last check.
Deployment visibility
Which version is live, when it was deployed, and what PR or commit it came from. Full traceability from /inspect to the merge that shipped it.
Tool surface
The exact set of tools the running service exposes — names, descriptions, and input schemas. What clients actually see, not what the code might expose.
Client validation evidence
Validation evidence against targeted MCP clients, when available. What has been tested against this specific deployment — not a universal compatibility claim.
What /inspect does NOT show
Public without being unsafe.
/inspect is designed to be safe to share publicly. It exposes operational visibility — not configuration secrets or internal implementation details.
API keys or auth credentials of any kind
Private environment variables or configuration values
Internal service URLs or infrastructure details
Other tenants' data or services
Unexposed tools or private tool implementations
Why it matters
Remote MCP needs a trust layer. /inspect is it.
When an MCP server is remote, clients and operators have no natural way to verify what's actually running. /inspect gives every deployed service a stable, public source of truth — so trust in a remote MCP endpoint is grounded in live service state, not documentation or verbal assurances.
Ship with inspect built in.
Every service deployed through mcpctl gets a public /inspect endpoint automatically. No separate wiring. No documentation to keep current.
Ship with inspect