Local MCP capabilities provider for Expo
Nothing to run from here
Bernstein (bernstein-mcp) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Verifies Bernstein run receipts and hash chains; lists the shipped presets and adapters. Read-only.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bernstein-bernstein-mcp https://mcp.bernstein.run/mcp
# 2 — ask your agent for something these tools do
# server_info, verify_receipt, explain_receipt and 8 more
Bernstein (bernstein-mcp) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SLAll 2 servers
sipyourdrink-ltd2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bernstein-bernstein-mcp https://mcp.bernstein.run/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Identity, version, and request limits for this MCP server.
No parameter schema on file.
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 ve
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt | yes | The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt | yes | The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entries | yes | Rows in chain order, oldest first: a JSON array, or the raw text of the file. | |
| kind | string | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| record | yes | A TRACE v0.2 Trust Record: the file contents as a string, or the parsed object. |
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 chec
| Parameter | Type | Required | Notes |
|---|---|---|---|
| manifest | yes | The agent manifest: COSE envelope as base64 string, or the parsed JSON object (payload). | |
| trustRecord | object | no | Optional TRACE v0.2 Trust Record to check if it cites this manifest (references[].rel == 'agent-manifest'). |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| records | yes | The record set in any order: a JSON array of records (objects or strings), or the raw text of a file. | |
| context | object | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| receipt | no | Optional run receipt: the file contents as a string, or the parsed object. |
The compliance presets bernstein v3.19.2 ships, with the switches each one turns on.
No parameter schema on file.
Every field of one compliance preset as bernstein v3.19.2 resolves it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | — |
The agent adapters bundled with bernstein v3.19.2: adapter name, the binary it drives, the module that implements it.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bernstein (bernstein-mcp) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.2.0.
0.2.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Bernstein (bernstein-mcp) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.