Backlog

Next up

In Progress

Done

Main Roadmap

OpenTelemetry alignment for logs, snapshots, and metrics in MCP Status.Make MCP Status data portable and interoperable by aligning internal events and time series with OpenTelemetry conventions. This enables clean exports to any OTel compatible backend and makes it easier for customers to join MCP Status data with the rest of their observability stack.<h1>Why this matters</h1>Teams already standardize on OTel for traces, metrics, and logs. If MCP Status emits OTel friendly signals, it becomes easier to adopt, easier to integrate, and easier to trust. It also makes “capability integrity” measurable in the same language as uptime, latency, and errors.<h1>Scope</h1><ul><li>Snapshot events and probe run events as structured logs</li></ul><ul><li>Metrics Synthetic health metrics and probe metrics as OTel metrics with stable naming and units</li><li>Traces Optional but recommended. Each run becomes a trace with spans for transport, auth, handshake, list tools, tool call, resource read, prompt evaluation, and validation steps</li></ul>

In Review

OpenTelemetry alignment

John

Expose an MCP Status MCP server so agents and tools can directly communicate with the service.This server should let you query live status data, inspect capabilities, trigger checks, and react to incidents programmatically. It turns MCP Status from a dashboard into an active system component your agents can reason over and act on.Benefits<ul><li>Access real time health, probe results, and capability metadata via a standard MCP interface</li><li>Enable autonomous agents to monitor, alert, and respond without manual intervention</li><li>Integrate MCP Status into existing agent workflows and toolchains</li><li>Keep monitoring logic close to where decisions are made, not just where data is viewed</li></ul>

MCP Server for mcpstatus.io

Add OAuth2 authentication as an alternative to Bearer Token for secured MCP servers and APIs.Modern MCP servers and APIs increasingly rely on OAuth2 for secure access using short lived, scoped access tokens instead of static credentials. Supporting OAuth2 would allow monitors to authenticate through standardized token flows rather than long lived bearer secrets.Benefits this unlocks for users:<ul><li>OAuth enables delegated access, allowing clients to access protected resources without exposing user credentials or long lived static tokens.</li><li>Access is time limited and revocable. Tokens issued via OAuth can expire and be revoked, reducing risk if compromised compared to static bearer tokens.</li><li>Fine grained permissions and scoped access make it possible to request only the permissions needed for monitoring instead of granting broad access.</li><li>User credentials are never shared or stored. Only tokens are used, minimizing exposure of sensitive data.</li><li>Integration with modern identity providers, enterprise SSO, and external authentication systems becomes straightforward, improving interoperability with real world production environments.</li></ul>Suggested design and implementation notes:<ul><li>OAuth support should cover standard HTTP based MCP transports, since OAuth inherently operates over HTTP, similar to how other clients expose OAuth support.</li><li>OAuth should be offered as an optional authentication mode alongside Bearer Token to avoid breaking existing setups.</li><li>Token storage and automatic refreshing should be supported, including access and refresh tokens, to enable long lived monitoring without manual intervention.</li></ul>

OAuth2 Authentication

Add the ability for each monitor to actively probe tools resources and prompts with real inputs and expected outcomes.Users can configure one or multiple probers per tool with a specific input payload. The system will then run these probes on a schedule and validate the returned output for consistency robustness and reliability over time.This would allow teams to:<ul><li>Detect silent failures where endpoints are up but behavior is broken</li><li>Validate functional correctness not just availability</li><li>Track long term reliability of agent tools and prompts</li><li>Catch regressions after updates</li></ul>== Update Jan 10 ==Scope has been changed from Tools, Resources and Prompts to Tools only.