Bernstein MCP is answering right now. Last checked moments ago. It exposes 10 tools. Last commit 20 Sep 2026.
Verifies Bernstein run receipts and hash chains; lists the shipped presets and adapters. Read-only.
Uptime history
4 days of history · worst day 99%
4 days agonow
98.9%
Uptime 24h
91 of 92 checks
10
Tools
read from the server
286 ms
Response time
average over 24h
0
Stars
last commit 20 Sep 2026
Bernstein MCP missed one check this week
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.
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.
run in your terminal
claude mcp add bernstein-mcp --transport http https://mcp.bernstein.run/mcp~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"bernstein-mcp": {
"url": "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
{
"mcpServers": {
"bernstein-mcp": {
"url": "https://mcp.bernstein.run/mcp"
}
}
}Available tools 10
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
verify
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.bernstein.run/mcp | streamable-http | answering | 309 ms | 0 min ago |
Alternatives to Bernstein MCP
same job, measured the same wayRunGlance
by openlyuseful
Read-only local progress, usage, lock state, work lists, and verified run receipts.
Computeledger
by rudrendupaul
Signs, hash-chains, and verifies compute usage receipts via an MCP server, no issuer trust required.
I
ReceiptRail — x402 Delivery Receipts
by xka0085-byte
On-chain x402 delivery receipts on Solana: hash-locked, verifiable proof of delivery.
LiquiLens Evidence Carrier
by beepboop2025
Offline verification of local evidence carriers, fleet briefs, and hash-only trade-safety receipts.
Most Recommended Books
by mostrecommendedbooks
Read-only MCP server for verified book recommendations and reading lists.
Agora
by mo-grantsmith
Find governed AI capabilities and verify signed receipts. Read-only, no account.
Postcept
by postcept
Verify agent actions against the system of record and get signed completion receipts.
Behind the Watt
by ykorets
Verified behind-the-meter data center power, announcements, and provenance receipts.
Bernstein MCP — questions
Answers built from our own checks of this server.
What can Bernstein MCP do?
It exposes 10 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 4 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 91 of 92 checks got a reply (98.9%), average response time 286 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 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 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 10 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 286 ms on average, which is faster than 55% 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?
Yes — it is published under the Apache-2.0 licence, written in TypeScript, 0 stars on GitHub and 1 open issue. The source link is on this page, so you can read exactly what it does with your data before you connect it.