Security & Testing
bernstein.run
An MCP server for verifying Bernstein run receipts, hash chains, and TRACE records by recomputing chain links and checking Ed25519 signatures.
ENDPOINT 1
https://mcp.bernstein.run/mcp
MCP server metadata
- Name
- bernstein
- Version
- v3.19.2
Known tools 10
verify_receiptRecompute 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.
Inferred read-onlyexplain_receiptVerify 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.
Inferred read-onlyverify_chainWalk bernstein chain rows and recompute every link: journal rows (event_hash), lineage spine entries (entry_hash) or audit events (prev_hmac linkage).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.bernstein]
url = "https://mcp.bernstein.run/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"bernstein": {
"type": "http",
"url": "https://mcp.bernstein.run/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: bernstein
Remote MCP URL: https://mcp.bernstein.run/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"bernstein": {
"url": "https://mcp.bernstein.run/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"bernstein": {
"type": "http",
"url": "https://mcp.bernstein.run/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "bernstein",
"transport": "streamable-http",
"url": "https://mcp.bernstein.run/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.