Mcpuptimeledger MCP

What mcpuptimeledger-mcp MCP server does

The mcpuptimeledger-mcp MCP server connects an MCP client to the hosted MCP Uptime Ledger service. Its purpose is to monitor operational and compliance-related signals for MCP servers: availability, tool definitions, authentication behavior, service-level evidence, and exported status information.

The service is intended for teams that need to inspect MCP endpoints or produce records about their condition. It is a hosted, paid offering, so it is not a local monitoring package that can be run directly from the repository.

How it works

The production service exposes an MCP endpoint at https://mcpuptimeledger.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint using Streamable HTTP. Each production request must include a bearer token in the HTTP authorization header:

Authorization: Bearer <token>

The token is obtained through the product website after selecting a plan and creating or requesting API access. Browser requests made without authentication receive a JSON error response rather than internal service details.

The repository also publishes a server card at https://mcpuptimeledger.clauxel.com/server-card.json and identifies the service in the registry as com.clauxel.mcpuptimeledger/mcpuptimeledger-mcp.

Setup and configuration

To use the mcpuptimeledger-mcp MCP server, first visit the product website and choose an available plan. Obtain an API token, then configure an MCP client that supports remote Streamable HTTP servers with the published endpoint. The client must send the bearer token with its JSON-RPC calls.

No required environment variable names are documented in the provided material. Configuration details are therefore handled by the MCP client and the hosted service rather than by a documented local process. The repository itself is a public reference for documentation and directory submission; it does not provide the private production implementation.

Tools and capabilities

The service exposes five MCP tools:

• check_mcp_server_uptime checks MCP server availability.
• validate_tool_schema validates the schema for MCP tools.
• detect_auth_failure detects authentication failures.
• issue_sla_receipt issues an SLA receipt as service evidence.
• export_status_report exports a status report.

These tools cover the checks and evidence workflows described by the service. The supplied documentation does not specify input fields, output schemas, polling behavior, report formats, retention rules, or the exact contents of SLA receipts.

Limitations and notes

The service is paid and hosted remotely. A valid bearer token is required for production calls, so local operation without the hosted endpoint is not described. Client compatibility depends on support for Streamable HTTP remote MCP servers; the documentation does not identify specific MCP client products.

The public repository should not be treated as the service implementation. It contains documentation and directory-submission material, while the production source remains private. Consult the product page for plan and pricing information before integrating it into a production workflow.