# io.github.sipyourdrink-ltd/bernstein-mcp (remote · mcp.bernstein.run)

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

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.bernstein.run`: 69/100 (this document), [markdown](https://verifymcp.io/servers/sipyourdrink-ltd-bernstein-mcp/mcp.md), [page](https://verifymcp.io/servers/sipyourdrink-ltd-bernstein-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.bernstein.run/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 949 tokens (~94/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.sipyourdrink-ltd/bernstein-mcp server?

io.github.sipyourdrink-ltd/bernstein-mcp is a hosted endpoint at https://mcp.bernstein.run/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http sipyourdrink-ltd-bernstein-mcp 'https://mcp.bernstein.run/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "sipyourdrink-ltd-bernstein-mcp": {
      "url": "https://mcp.bernstein.run/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.sipyourdrink-ltd-bernstein-mcp]
url = "https://mcp.bernstein.run/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sipyourdrink-ltd-bernstein-mcp": {
      "type": "remote",
      "url": "https://mcp.bernstein.run/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sipyourdrink-ltd-bernstein-mcp --url 'https://mcp.bernstein.run/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  sipyourdrink-ltd-bernstein-mcp:
    url: "https://mcp.bernstein.run/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "sipyourdrink-ltd-bernstein-mcp": {
      "Transport": "http",
      "Url": "https://mcp.bernstein.run/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add sipyourdrink-ltd-bernstein-mcp -t streamable-http -u 'https://mcp.bernstein.run/mcp'
```

### Other

```json
{
  "mcpServers": {
    "sipyourdrink-ltd-bernstein-mcp": {
      "type": "http",
      "url": "https://mcp.bernstein.run/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 68, +1)

- [functional regression] Schema quality: 71 → 94
- [functional improvement] Tool coverage: 60% → 67%
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] New tool “explain_trace_mapping”
- [functional] New tool “verify_delegation_chain”
- [functional] New tool “verify_trace_record”

### 2026-09-18 (score 67)

First indexed and scored.

## MCP tools (10)

### `server_info` (~20 tokens)

Server info

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

Output parameters:

- `keys_url` (string)
- `limits` (object)
- `name` (string)
- `verdict_key`: Public Ed25519 JWK this deployment signs verdicts with; also at keys_url.
- `version` (string)

### `verify_receipt` (~141 tokens)

Verify a run 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.

Input parameters:

- `receipt` (required): The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object.

Output parameters:

- `checks` (array)
- `divergent_step`
- `failing_check`
- `keys_url` (string)
- `note` (string|null)
- `receipt_sha256` (string)
- `signed_verdict`: DSSE envelope over the verdict statement (JCS JSON in payload), Ed25519 over the DSSE PAE.
- `summary`
- `verdict` (string)
- `verify_url` (string|null)

### `explain_receipt` (~79 tokens)

Explain a run 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.

Input parameters:

- `receipt` (required): The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object.

Output parameters:

- `explanation` (string)
- `receipt_sha256` (string)
- `verdict` (string)

### `verify_chain` (~156 tokens)

Verify a hash 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.

Input parameters:

- `entries` (required): Rows in chain order, oldest first: a JSON array, or the raw text of the file.
- `kind` (string)

Output parameters:

- `detail` (string)
- `divergent_index`
- `entries` (integer)
- `head` (string)
- `intact` (boolean)
- `kind` (string)

### `verify_trace_record` (~155 tokens)

Verify a TRACE Trust 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.

Input parameters:

- `record` (required): A TRACE v0.2 Trust Record: the file contents as a string, or the parsed object.

Output parameters:

- `checks` (array)
- `failing_check`
- `note` (string|null)
- `record_sha256` (string)
- `summary`
- `verdict` (string)

### `verify_delegation_chain` (~195 tokens)

Verify a TRACE 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).

Input parameters:

- `context` (object)
- `records` (required): The record set in any order: a JSON array of records (objects or strings), or the raw text of a file.

Output parameters:

- `classification` (string)
- `codes` (array)
- `depth` (integer)
- `failures` (array)
- `first_broken_link`
- `note` (string|null)
- `walk` (array)
- `warnings` (array)

### `explain_trace_mapping` (~102 tokens)

Explain the bernstein → 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.

Input parameters:

- `receipt`: Optional run receipt: the file contents as a string, or the parsed object.

Output parameters:

- `mapping` (array)
- `markdown` (string)
- `receipt_sha256` (string|null)
- `verdict`

### `list_presets` (~30 tokens)

List compliance presets

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

Output parameters:

- `bernstein_version` (string)
- `presets` (array)

### `get_preset` (~34 tokens)

Get a compliance preset

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

Input parameters:

- `name` (string, required)

Output parameters:

- `bernstein_version` (string)
- `config` (object)
- `name` (string)

### `list_adapters` (~37 tokens)

List agent adapters

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

Output parameters:

- `adapters` (array)
- `bernstein_version` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/sipyourdrink-ltd-bernstein-mcp/mcp#diagnostics

## Score history

- 2026-09-20: 69
- 2026-09-19: 68
- 2026-09-18: 67

## Common questions

### What is the io.github.sipyourdrink-ltd/bernstein-mcp server?

io.github.sipyourdrink-ltd/bernstein-mcp is listed in the public MCP registry as io.github.sipyourdrink-ltd/bernstein-mcp. Verifies Bernstein run receipts and hash chains; lists the shipped presets and adapters. Read-only. This page covers its hosted endpoint (https://mcp.bernstein.run/mcp).

### Is the io.github.sipyourdrink-ltd/bernstein-mcp server safe to use?

io.github.sipyourdrink-ltd/bernstein-mcp scores 69 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.sipyourdrink-ltd/bernstein-mcp server expose?

io.github.sipyourdrink-ltd/bernstein-mcp exposes 10 tools: server_info, verify_receipt, explain_receipt, verify_chain, verify_trace_record, and 5 more. Their descriptions and schemas cost roughly 949 tokens of context every time the server is loaded.

### Does the io.github.sipyourdrink-ltd/bernstein-mcp server require authentication?

No. We connected to io.github.sipyourdrink-ltd/bernstein-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.sipyourdrink-ltd/bernstein-mcp server still maintained?

io.github.sipyourdrink-ltd/bernstein-mcp is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.bernstein.run/mcp
- Repository: https://github.com/sipyourdrink-ltd/bernstein-mcp
- Website: https://mcp.bernstein.run/
- Changelog RSS feed: https://verifymcp.io/servers/sipyourdrink-ltd-bernstein-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sipyourdrink-ltd-bernstein-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/sipyourdrink-ltd-bernstein-mcp/mcp