mcpbeat

Verify MCP Server

com.kenoodl/verify
answering

Verify is answering right now. Last checked 2 min ago. It exposes 1 tools.

Runs your code against a contract; returns HELD or BROKE at the exact input. Deterministic.

Uptime history 47 hours of history
47 hours agonow
100.0%
Uptime 24h
92 of 92 checks
1
Tools
read from the server
173 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add verify --transport http https://kenoodl.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verify": {
      "url": "https://kenoodl.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verify]
url = "https://kenoodl.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verify": {
      "url": "https://kenoodl.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verify": {
      "url": "https://kenoodl.com/mcp"
    }
  }
}

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.

verify
verify
An outside check on code, executed in a sealed sandbox. Call it before code crosses a consequence boundary: before you merge it, deploy it, publish it, settle a payout on it, or report it done. A self-audit verifies consistency, never completeness: a check written inside the frame that produced the code passes on the code's own assumptions. This is the check that is not you. Also call it when a fix passes your own check but the target still fails; that means your check shares the code's assumption and cannot see the error. INPUT: code (JavaScript/Node or Python 3 source, deterministic only) plus ONE of: contract {fn, examples:[{call,expected}]} (copy call and expected from the test or spec the consequence depends on), or assumption (plain-language claim, weaker read). It checks the code against the contract exactly as given. VERDICTS (synchronous): BROKE: the code violates your contract, with the exact input and a rerunnable proof; do not proceed. HELD: the code meets the contract you gave; proceed on that contract, and nothing more. FINDINGS: a stated property strains under a generated input; check it before proceeding. DROP: not deterministically checkable. PAYMENT: 0.10 USDC per call, x402 v2 on Base, no account. Every delivered verdict is charged, HELD and DROP included. If no verdict is produced, the payment authorization is cancelled and you are not charged.

Endpoints

URLTransportStateLatencyChecked
https://kenoodl.com/mcp streamable-http answering 194 ms 2 min ago

Verify — questions

Answers built from our own checks of this server.

What can Verify do?
It exposes 1 tools, read directly from the server on our last check. Among them: verify. 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 Verify working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 173 ms. The bar chart above shows every period we have measured.
How do I connect Verify?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Verify need an API key?
No. Verify 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.
How fast is Verify?
It answers our handshake in 173 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.