What are the risks of connecting to mcp.bernstein.run?

No blocking issues were found in the static + spec checks. Overall trust grade B+ (87/100).

When was mcp.bernstein.run last audited?

Last checked 2026-10-03; wmcp.sh re-checks it on a schedule for tool drift and rug-pulls.

B+

mcp.bernstein.run

Item: mcp.bernstein.run
Rating: 87
Author: wmcp.sh

https://mcp.bernstein.run/mcp

87/100 · MCP Trust Grade · checked 26d ago · MCP 2025-06-18

Is the mcp.bernstein.run MCP server safe to use?

Independent trust grade B+ (87/100). No blocking issues found in the static + spec checks. wmcp.sh continuously watches mcp.bernstein.run for tool drift and rug-pulls. The grade is free and identical whether or not the operator pays.

✓ Watched since 2026-10-03 — behavioral baseline locked. We re-check this server's tool surface on a schedule; if it adds, removes, or silently rewrites a tool (rug-pull), we record it.

What it offers — 11 tools · Developer Tools

server_info

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

verify_receipt

Recompute every hash chain a bernstein run receipt embeds (journal, lineage spine, optional audit range), rebuild the signed subject from the recomput

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

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).

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 runt

verify_agent_manifest

Agent Manifest v0.2 conformance checks on one manifest, stateless, no account: schema (vendored agent-manifest.schema.json), profile context, version,

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 lea

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. Pas

list_presets

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

get_preset

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

list_adapters

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

Spec conformance20%100

✓ initialize → protocolVersion 2025-06-18
✓ initialize HTTP 200
✓ unknown method → -32601
✓ tools/list → 11 tools
✓ every tool has name + inputSchema

Security (OWASP MCP)30%100

11 tools scanned
no injection markup
no secret-path refs

Reliability / performance20%70

single-probe latency 1690ms (PRELIMINARY — continuous uptime/p95 from proxy telemetry lands in v2)

Tool hygiene15%84

73% of tools have typed inputSchema
11/11 declare outputSchema
no unannotated destructive tools

Transparency / provenance15%70

HTTPS ✓
advertises protocol 2025-06-18

Observed behavior

No proxied traffic observed for this host yet. Connect it at /connect and its grade gains a measured Reliability score + per-tool behavioral evidence — the half a static scan can't produce.

Findings

No blocking issues found in the static + spec checks.

Grade another server

We re-grade mcp.bernstein.run on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.

Run mcp.bernstein.run? Claim it (free) to get drift alerts and show an independently-verified trust badge. The grade stays free — claiming just ties it to you.

Share this report card

A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.

MCP Trust report card — mcp.bernstein.run grade B+

Share on X Open card image

https://wmcp.sh/mcp/grade/mcp.bernstein.run

Embed this grade

A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.

Markdown (for your README)

[![MCP Trust Grade B+](https://wmcp.sh/mcp/grade/mcp.bernstein.run/badge.svg)](https://wmcp.sh/mcp/grade/mcp.bernstein.run)

HTML

<a href="https://wmcp.sh/mcp/grade/mcp.bernstein.run"><img src="https://wmcp.sh/mcp/grade/mcp.bernstein.run/badge.svg" alt="MCP Trust Grade B+ · wmcp.sh"></a>

Agents: check this before connecting

Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:

https://wmcp.sh/mcp/trust

How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.