Bernstein MCP Server

by sipyourdrink-ltd Your server? Claim it

answering

Bernstein MCP is answering right now. Last checked moments ago. It exposes 12 tools. Last commit 4 Nov 2026.

Verifies Bernstein run receipts and hash chains; lists the shipped presets and adapters. Read-only.

Uptime history 53 days of history · worst day 92%

53 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

245 ms

Response time

average over 24h

Stars

last commit 4 Nov 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 24 September 2026. No other catalogue keeps this.

4 Nov a tool appeared trace_verify_record

24 Sep a tool appeared verify_agent_manifest

Nothing serious here today

Today is the operative word: we check Bernstein MCP every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add bernstein-mcp --transport http https://mcp.bernstein.run/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.bernstein.run/mcp

~/.codex/config.toml

[mcp_servers.bernstein-mcp]
url = "https://mcp.bernstein.run/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "bernstein-mcp": {
      "url": "https://mcp.bernstein.run/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "bernstein-mcp": {
      "type": "http",
      "url": "https://mcp.bernstein.run/mcp"
    }
  }
}

Available tools 12

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

verify

verify_agent_manifest

Agent Manifest v0.2 conformance checks on one manifest, stateless, no account: schema (vendored agent-manifest.schema.json), profile context, version, canonicalization, COSE envelope signature (Ed25519, key identified by kid in the protected header; ML-DSA-65 is reported unverifiable). Optionally checks that a TRACE Trust Record cites this manifest by digest. Nothing is fetched; resolvers are checked as URIs only. The manifest hash is sha256 over the COSE payload bytes (or RFC 8785 canonical JSON for object input).

verify_chain

Walk bernstein chain rows and recompute every link: journal rows (event_hash), lineage spine entries (entry_hash) or audit events (prev_hmac linkage). The row kind is detected from the fields, or pass `kind` explicitly. Reports the first divergent index. Pass `entries` as the file text (a JSON array or one row per line, as journal.jsonl is written) for byte-exact hashing; a parsed array also works, but then a float spelled 1.0 or -0.0 in the file cannot be told apart from an integer.

verify_delegation_chain

TRACE v0.2 delegation-chain conformance, stateless, no account: index every Trust Record by the RFC 8785 digest of its complete form, start at the leaf, follow delegation.parent_record_hash to the root, and check each hop's signature, the root key against `trusted_root_keys`, the depth bound, the link's digest algorithm, the credential (registered, issuer = parent subject, holder = record subject, window at the hop's own iat) and data_class narrowing under `data_class_lattice`. Classification: provenance-invalid outranks authorization-invalid; an unread link is unverifiable, not broken. Pass `records` as a JSON array or as file text (one record per line or a JSON array).

verify_receipt

Recompute every hash chain a bernstein run receipt embeds (journal, lineage spine, optional audit range), rebuild the signed subject from the recomputed heads, and check the Ed25519 signature with the key the receipt carries. Needs no secret and reads nothing but the receipt. Returns the verdict, the first failing check, one line per check, and the same verdict as a DSSE envelope signed by this verifier's Ed25519 key (public key at keys_url) so the outcome can be kept and re-checked offline.

verify_trace_record

TRACE v0.2 conformance checks on one Trust Record, stateless, no account: schema (vendored trace-claim.json), profile, subject URI, software-only runtime rule, policy digest, public-only confirmation key, the embedded signature (EdDSA, ES256 or ES384 with the key in cnf.jwk), appraisal, delegation link shape and references. Nothing is fetched: resolvers are checked as URIs only. `record_sha256` is the RFC 8785 digest of the complete record, signature included — the value a child hop puts in delegation.parent_record_hash.

explain

explain_receipt

Verify a run receipt and narrate the result in plain language: what the run recorded, which chains recomputed, where the first divergence is, and what an auditor can and cannot conclude without the producing install's keys.

explain_trace_mapping

How a bernstein run maps onto a TRACE v0.2 Trust Record: one row per claim with the journal field it is sourced from and the rule that derives it. Pass a run receipt to fill in the rows its embedded journal can answer (subject, iat, model, data_class, policy digest, tool transcript) alongside the receipt's own verdict.

adapters

list_adapters

The agent adapters bundled with bernstein v3.19.2: adapter name, the binary it drives, the module that implements it.

preset

get_preset

Every field of one compliance preset as bernstein v3.19.2 resolves it.

presets

list_presets

The compliance presets bernstein v3.19.2 ships, with the switches each one turns on.

server

server_info

Identity, version, and request limits for this MCP server.

trace

trace_verify_record

Verify a TRACE v0.2 Ed25519 Trust Record locally with optional caller public key and freshness controls. Nothing is fetched. Embedded keys establish internal consistency only; revocation is not affirmed.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.bernstein.run/mcp	streamable-http	answering	175 ms	0 min ago

Alternatives to Bernstein MCP

same job, measured the same way

RunGlance

by openlyuseful

Read-only local progress, usage, lock state, work lists, and verified run receipts.

35 installs/wk local only

Computeledger

by rudrendupaul

Signs, hash-chains, and verifies compute usage receipts via an MCP server, no issuer trust required.

106 installs/wk local only

LiquiLens Evidence Carrier

by beepboop2025

Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts.

local only

Most Recommended Books

by mostrecommendedbooks

Read-only MCP server for verified book recommendations and reading lists.

6 tools answering

Agora

by mo-grantsmith

Find governed AI capabilities and verify signed receipts. Read-only, no account.

3 tools answering

Proxmox MCP

by servosity

Read-only Proxmox VE and Backup Server: which client guests have a verified, recent restore point.

local only

AKKO MCP server for Trino

by ab2dridi

Read-only MCP server for Trino: queries run as the verified user, and Trino's own policies decide.

893 installs/wk local only

ProofCheck

by something-agent

Free x402 offer/receipt checker: verifies signatures and whether the signer fits the host.

5 tools answering

Bernstein MCP — questions

Answers built from our own checks of this server.

What can Bernstein MCP do?

It exposes 12 tools, read directly from the server on our last check. Among them: explain_receipt, explain_trace_mapping, get_preset, list_adapters, list_presets, server_info and 6 more. 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 →

What is Bernstein MCP mostly used for?

Its tools cluster around verify and explain. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is Bernstein MCP 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 245 ms. The bar chart above shows every period we have measured.

How do I connect Bernstein MCP?

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 Bernstein MCP need an API key?

No. Bernstein MCP completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Bernstein MCP?

It answers our handshake in 245 ms on average, which is faster than 56% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Bernstein MCP open source?

The code is open source: it is published under the Apache-2.0 licence, written in TypeScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.bernstein.run, which runs on its operator's own terms.