MCP Server Status

A published operational snapshot of the Digital Calculator MCP server at https://mcp.digitalcalculator.info/mcp. This is a published status snapshot, refreshed on each deploy — it is not real-time monitoring. For the definitive live picture, run the initialize handshake against the endpoint yourself (see How to check it yourself).

This is a snapshot, not a live dashboard

The values below reflect the last verified deploy, not a continuously-polling health check. A real-time status endpoint is planned for a later phase. If you need to confirm the endpoint is up right now, the fastest check is the handshake described below.

Current status

Published operational snapshot of the Digital Calculator MCP server
Item	Status
Endpoint (`https://mcp.digitalcalculator.info/mcp`)	Operational
Tools live	13
Anonymous-tier parity	Green — last 16-call golden baseline penny-exact
Transport	Streamable HTTP (POST JSON-RPC, no auth required)
Last verified	2026-07-01 (static — updated on each deploy)

What “parity: green” means

The anonymous tier is how developers evaluate the server before they commit. “Green” means the last CI run of our 16-call golden baseline — captured with no Authorization header — returned byte-for-byte, penny-exact matches against the recorded baseline. If any anonymous response had drifted, the deploy would have failed and this snapshot would not read green. See the Anonymous-Parity Guarantee for how it’s enforced.

How to check it yourself

Don’t take our snapshot on faith — the endpoint is the source of truth. Point any MCP client at https://mcp.digitalcalculator.info/mcp and run the initialize handshake; a successful response with a serverInfo.version field confirms the server is up and tells you the exact contract version it’s running. Then call tools/list to see all 13 tools. The Quickstart walks through connecting in under five minutes, and the Versioning & Deprecation Contract explains what each version number means.

What this page does and doesn’t cover

It is a deploy-time snapshot, not real-time monitoring. The “Last verified” date is when the snapshot was refreshed, not a live heartbeat.
It is not an uptime SLA. The anonymous tier is provided as-is with no availability guarantee. Bearer-tier availability commitments live in the Bearer terms.
It reports the shape-stability posture (parity) and the operational headline, not per-request latency or historical incident logs.

Report an issue

Seeing errors, timeouts, or unexpected output? Start with the onboarding page for integration help, or email admin@markcolabs.com with the tool name, your request payload, and the response you got. Bearer-tier customers receive priority handling via the contact on file.