io.github.sipyourdrink-ltd/bernstein-mcp
REMOTE · MCP.BERNSTEIN.RUN · SCANNED SEP 20
Verifies Bernstein run receipts and hash chains; lists the shipped presets and adapters. Read-only.
Available components
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. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 949 tokens (~94/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · mcp.bernstein.run
claude mcp add --transport http sipyourdrink-ltd-bernstein-mcp 'https://mcp.bernstein.run/mcp'
{
"mcpServers": {
"sipyourdrink-ltd-bernstein-mcp": {
"url": "https://mcp.bernstein.run/mcp"
}
}
} {
"servers": {
"sipyourdrink-ltd-bernstein-mcp": {
"type": "http",
"url": "https://mcp.bernstein.run/mcp"
}
}
} [mcp_servers.sipyourdrink-ltd-bernstein-mcp] url = "https://mcp.bernstein.run/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sipyourdrink-ltd-bernstein-mcp": {
"type": "remote",
"url": "https://mcp.bernstein.run/mcp",
"enabled": true
}
}
} openclaw mcp add sipyourdrink-ltd-bernstein-mcp --url 'https://mcp.bernstein.run/mcp' --transport streamable-http
mcp_servers:
sipyourdrink-ltd-bernstein-mcp:
url: "https://mcp.bernstein.run/mcp" {
"McpServers": {
"sipyourdrink-ltd-bernstein-mcp": {
"Transport": "http",
"Url": "https://mcp.bernstein.run/mcp"
}
}
} assistant mcp add sipyourdrink-ltd-bernstein-mcp -t streamable-http -u 'https://mcp.bernstein.run/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 19 Sept 26 +1
- Schema quality: 71 → 94 ▼ functional
- Tool coverage: 60% → 67% ▲ functional
- 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” functional
- 18 Sept 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp.bernstein.run/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bernstein.run | CN=YE2,O=Let's Encrypt,C=US | 10 Aug 2026 | 8 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5e69cbbbc77b03e1ae23c44b637f063c0b6 |
| SANs: *.bernstein.run, bernstein.run | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.bernstein.run. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| run. | present | 37315 | 8 | Verified |
| bernstein.run. | present | 2371 | 13 | Verified |
| mcp.bernstein.run. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.bernstein.run/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.bernstein.run/mcp | HTTPS enforced | 301 | https://mcp.bernstein.run/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explain_receipt Explain a run receipt ~79
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | – | yes | The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object. |
| Name | Type | Req | Description |
|---|---|---|---|
| explanation | string | yes | – |
| receipt_sha256 | string | yes | – |
| verdict | string | yes | – |
No examples provided.
explain_trace_mapping Explain the bernstein → TRACE mapping ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | – | – | Optional run receipt: the file contents as a string, or the parsed object. |
| Name | Type | Req | Description |
|---|---|---|---|
| mapping | array | yes | – |
| markdown | string | yes | – |
| receipt_sha256 | string|null | yes | – |
| verdict | – | yes | – |
No examples provided.
get_preset Get a compliance preset ~34
Every field of one compliance preset as bernstein v3.19.2 resolves it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| bernstein_version | string | yes | – |
| config | object | yes | – |
| name | string | yes | – |
No examples provided.
list_adapters List agent adapters ~37
The agent adapters bundled with bernstein v3.19.2: adapter name, the binary it drives, the module that implements it.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| adapters | array | yes | – |
| bernstein_version | string | yes | – |
No examples provided.
list_presets List compliance presets ~30
The compliance presets bernstein v3.19.2 ships, with the switches each one turns on.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| bernstein_version | string | yes | – |
| presets | array | yes | – |
No examples provided.
server_info Server info ~20
Identity, version, and request limits for this MCP server.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| keys_url | string | yes | – |
| limits | object | yes | – |
| name | string | yes | – |
| verdict_key | – | yes | Public Ed25519 JWK this deployment signs verdicts with; also at keys_url. |
| version | string | yes | – |
No examples provided.
verify_chain Verify a hash chain ~156
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.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | – | yes | Rows in chain order, oldest first: a JSON array, or the raw text of the file. |
| kind | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | yes | – |
| divergent_index | – | yes | – |
| entries | integer | yes | – |
| head | string | yes | – |
| intact | boolean | yes | – |
| kind | string | yes | – |
No examples provided.
verify_delegation_chain Verify a TRACE delegation chain ~195
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).
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | – |
| records | – | yes | The record set in any order: a JSON array of records (objects or strings), or the raw text of a file. |
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | yes | – |
| codes | array | yes | – |
| depth | integer | yes | – |
| failures | array | yes | – |
| first_broken_link | – | yes | – |
| note | string|null | yes | – |
| walk | array | yes | – |
| warnings | array | yes | – |
No examples provided.
verify_receipt Verify a run receipt ~141
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.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | – | yes | The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| divergent_step | – | yes | – |
| failing_check | – | yes | – |
| keys_url | string | yes | – |
| note | string|null | yes | – |
| receipt_sha256 | string | yes | – |
| signed_verdict | – | yes | DSSE envelope over the verdict statement (JCS JSON in payload), Ed25519 over the DSSE PAE. |
| summary | – | yes | – |
| verdict | string | yes | – |
| verify_url | string|null | yes | – |
No examples provided.
verify_trace_record Verify a TRACE Trust Record ~155
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.
| Name | Type | Req | Description |
|---|---|---|---|
| record | – | yes | A TRACE v0.2 Trust Record: the file contents as a string, or the parsed object. |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | yes | – |
| failing_check | – | yes | – |
| note | string|null | yes | – |
| record_sha256 | string | yes | – |
| summary | – | yes | – |
| verdict | string | yes | – |
No examples provided.
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.