Witness is answering right now. Last checked 5 min ago. It exposes 1 tools.
Production proofs for breaking JSON Schema/MCP changes; UNKNOWN/NO_WITNESS_FOUND not compatible.
Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.
claude mcp add witness --transport http https://witness-edge-phase-c-test.witness-test.workers.dev/mcp
{
"mcpServers": {
"witness": {
"url": "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
}
}
}
[mcp_servers.witness]
url = "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
{
"mcpServers": {
"witness": {
"url": "https://witness-edge-phase-c-test.witness-test.workers.dev/mcp"
}
}
}
{
"mcpServers": {
"witness": {
"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.
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
contract_witness
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://witness-edge-phase-c-test.witness-test.workers.dev/mcp | streamable-http | answering | 206 ms | 5 min ago |
| https://witness-contractwitness-production.witness-test.workers.dev/mcp | streamable-http | answering | 413 ms | 5 min ago |
Monitor MCP servers, API contracts and AI outputs for schema drift. Alerts on breaking changes.
Breaking-change diffs for npm packages: removed exports, changed signatures, migration notes.
MCP server for cross-vendor API/SDK deprecation and breaking-change tracking
Verify AI agent communication with session types and formal proofs
Read-only validation of rights-aware production metadata manifests for MCP-compatible clients.
VibeRaven MCP for production-readiness checks and Launch Autopilot next actions
MCP server for generating production-ready HTML landing pages.
MCP server for RabbitMQ and Kafka message inspection with JSON Schema validation
Answers built from our own checks of this server.