← Registry

AI & Machine Learning

screwtape.ai

An MCP server for judging AI agent outputs, running consensus checks, and managing paid verification receipts.

1 endpoint5 known toolsFirst detected October 21, 2026Last detected October 21, 2026

ENDPOINT 1

https://screwtape.ai/mcp

No auth detected

MCP server metadata

Name
Screwtape.ai
Version
1.0.0
Capabilities
tools
Server instructions

False-consensus check and pass/fail/retry verdicts for agent output. Use judge on one draft answer before you return it (send evidence; it does not search the web). Use consensus when 2 to 16 answers to the same task agree and you are about to trust the majority. Use get_api_key only if no key is configured and you can compute SHA-256 in code. judge and consensus cost one call each: a free key gives 100 per UTC day, or pay $0.005 USDC on Base or Solana with x402. An unpaid tools/call returns HTTP 200 with isError true and the x402 PaymentRequirements in structuredContent. Retry with params._meta['x402/payment']. Settlement is echoed in result._meta['x402/payment-response']. Judged content is not stored unless retain is true. A successful judge or consensus result includes an Ed25519 receipt when signing is configured. Public keys are at https://screwtape.ai/.well-known/screwtape-receipt-keys.json. POST /v1/receipts/verify checks a receipt. publish_receipt publishes one receipt you own. It needs the Bearer key and does not accept x402. Not the arXiv paper named Screwtape.

Known tools 5

judge

An independent pass/fail/retry verdict on ONE agent output.

Inferred read-only
consensus

False-consensus check for 2 to 16 answers to the same task.

Inferred read-only
get_api_key

Create a free Screwtape.

Potential side effects
buy_pack

Return the x402 payment requirements for a Starter ($30, 10000 calls) or Builder ($100, 50000 calls) prepaid pack, plus how to pay with USDC on Base or Solana.

Potential side effects
publish_receipt

Publish a signed receipt you own so a public page and a Screwtape Verified badge can link to that one verdict.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.screwtape-ai]
url = "https://screwtape.ai/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "screwtape-ai": {
      "type": "http",
      "url": "https://screwtape.ai/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: screwtape-ai
Remote MCP URL: https://screwtape.ai/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "screwtape-ai": {
      "url": "https://screwtape.ai/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "screwtape-ai": {
      "type": "http",
      "url": "https://screwtape.ai/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "screwtape-ai",
  "transport": "streamable-http",
  "url": "https://screwtape.ai/mcp"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.