mcpbeat Sign in

Witness MCP Server

not responding

Witness is listed as active in the registry but did not answer our last check. It exposes 1 tools.

Production proofs for breaking JSON Schema/MCP changes; UNKNOWN/NO_WITNESS_FOUND not compatible.

Uptime history 75 days of history · worst day 0%
75 days agonow
0.0%
Uptime 24h
0 of 182 checks
1
Tools
read from the server
82 ms
Response time
average over 24h
open, no key
Access
streamable-http

Witness does not always answer

Over the last week it answered 13.4% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add witness --transport http https://witness-edge-phase-c-test.witness-test.workers.dev/mcp
Settings → Connectors → Add custom connector, then paste this address
https://witness-edge-phase-c-test.witness-test.workers.dev/mcp
~/.codex/config.toml
[mcp_servers.witness]
url = "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "witness": {
      "url": "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "witness": {
      "type": "http",
      "url": "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 1

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

contract
contract_witness
Produce a concrete independently revalidated JSON-Schema/MCP backward-compatibility witness before merge/deploy. UNKNOWN or NO_WITNESS_FOUND never means compatible.

Endpoints

URLTransportStateLatencyChecked
https://witness-edge-phase-c-test.witness-test.workers.dev/mcp streamable-http answering 82 ms 15 min ago
https://witness-contractwitness-production.witness-test.workers.dev/mcp streamable-http answering 77 ms 15 min ago

Alternatives to Witness

same job, measured the same way
Specwise MCP
by bytestay

OpenAPI and JSON Schema validation and OpenAPI breaking-change diffs for AI agents.

956 installs/wk local only
Fixzi — MCP & API Schema Drift Monitor
by rohitcodilya

Monitor MCP servers, API contracts and AI outputs for schema drift. Alerts on breaking changes.

answering
Vdiff MCP
by mcurmi05

Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes.

53 installs/wk local only
LogPulse
by lovable-release-ripple-roadmap

Changelogs for coding agents: versions, breaking changes, migrations. Free changelog-to-JSON.

9 tools answering
Deprecation MCP
by tsvillain

MCP server for cross-vendor API/SDK deprecation and breaking-change tracking

54 installs/wk local only
Lingua Universale MCP Server
by rafapra3008

Verify AI agent communication with session types and formal proofs

102 installs/wk local only
SHAR Production Metadata MCP
by sharproduction

Read-only validation of rights-aware production metadata manifests for MCP-compatible clients.

local only
headlesson
by headlesson

Find and compare headless apps (CLI, MCP, API) for agents, with sources, lessons and changes.

4 tools answering

Witness — questions

Answers built from our own checks of this server.

What can Witness do?
It exposes 1 tools, read directly from the server on our last check. Among them: contract_witness. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Witness working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 182 checks got a reply (0.0%), average response time 82 ms. The bar chart above shows every period we have measured.
The registry lists Witness as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Witness?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Witness need an API key?
No. Witness completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 1 of them are readable on this page. This is what we observed, not what the docs claim.