Problem
There is no public, simple way to understand the status, version, and capabilities of the public MCP service, which makes adoption and troubleshooting harder for clients.
Proposed solution
Publish a public MCP service status and capability page that includes uptime, version, tools, prompts, resources, client setup guidance, and aggregate reliability information without exposing identity or user-specific data.
Acceptance criteria
- Public status and capability page.
- Uptime, version, and service metadata.
- Tool, prompt, and resource inventory.
- Client setup instructions and examples.
- Aggregate reliability without identity or user context.
- Documentation and operational ownership.
Privacy and trust
The page must aggregate service health without identity information. It should avoid exposing user-specific activity, diagnostics, or account-level details.
Dependencies
- Public MCP service metadata and health pipeline.
- Documentation and client examples.
- Reliability and uptime monitoring.
Problem
There is no public, simple way to understand the status, version, and capabilities of the public MCP service, which makes adoption and troubleshooting harder for clients.
Proposed solution
Publish a public MCP service status and capability page that includes uptime, version, tools, prompts, resources, client setup guidance, and aggregate reliability information without exposing identity or user-specific data.
Acceptance criteria
Privacy and trust
The page must aggregate service health without identity information. It should avoid exposing user-specific activity, diagnostics, or account-level details.
Dependencies