Bernstein MCP server

• explain_receiptFree

  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_mappingFree

  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.

• get_presetFree

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

• list_adaptersFree

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

• list_presetsFree

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

• server_infoFree

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

• verify_chainFree

  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_chainFree

  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_receiptFree

  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_recordFree

  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.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1157ms20/20
• Tool poisoning10 tool descriptions checked15/15
• Auth qualityopen endpoint, read-only tools10/15
• Maintenancelast push 0 days ago15/15
• Maintainer identityregistry namespace matches repository owner7/10

Grade history

• 2026-09-19restoreB → Ascore 89

Bernstein: common questions

Is Bernstein MCP server safe?

Yes, by our scan: it is graded A (89/100). Read the Bernstein safety report

How do I install Bernstein?

It runs remotely at mcp.bernstein.run. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Bernstein need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Bernstein maintained?

The last commit was in the last day (2026-09-19). The latest release is v0.2.0.

Is Bernstein up?

100% of our last 2 checks got an answer. We check remote servers about four times a day.