mcp-registry/io.github.sipyourdrink-ltd/bernstein-mcp · vv3.19.2
As of 2026-10-19 22:55 UTC, the Sipyourdrink Ltd Bernstein MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Verifies Bernstein run receipts and hash chains; lists the shipped presets and adapters. Read-only.
Claude Code
claude mcp add --transport http sipyourdrink-ltd-bernstein-mcp-server https://mcp.bernstein.run/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"sipyourdrink-ltd-bernstein-mcp-server": {
"type": "http",
"url": "https://mcp.bernstein.run/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
11 of 11 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
3 parameter(s) across 3 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
2 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.sipyourdrink-ltd%2Fbernstein-mcp/fixes
{
"name": "explain_receipt",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"receipt"
],
"properties": {
"receipt": {
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
],
"description": "The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Explain a run receipt"
}{
"name": "explain_trace_mapping",
"description": "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.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"receipt": {
"anyOf": [
{
"type": "string"
},
{
"type": "object",
"propertyNames": {
"type": "string"
},
"additionalProperties": {}
}
],
"description": "Optional run receipt: the file contents as a string, or the parsed object."
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Explain the bernstein → TRACE mapping"
}{
"name": "get_preset",
"description": "Every field of one compliance preset as bernstein v3.19.2 resolves it.",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"name"
],
"properties": {
"name": {
"enum": [
"development",
"hipaa",
"regulated",
"standard"
],
"type": "string"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "Get a compliance preset"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.sipyourdrink-ltd/bernstein-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.sipyourdrink-ltd/bernstein-mcp"}) over MCP.
verify_delegation_chain ~675 tokensverify_agent_manifest ~315 tokensverify_chain ~276 tokensverify_trace_record ~251 tokensverify_receipt ~250 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.sipyourdrink-ltd%2Fbernstein-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.sipyourdrink-ltd%2Fbernstein-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sipyourdrink-ltd%2Fbernstein-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.sipyourdrink-ltd%2Fbernstein-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.sipyourdrink-ltd%2Fbernstein-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:038fe49ec771cf8c…, first seen 2026-10-17, included at leaf 10185 of 29,285. Version history · verify what your client received.
Compare: most reliable security servers · most reliable knowledge servers · most reliable other servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-19 22:55 UTC, the Sipyourdrink Ltd Bernstein MCP server is up with a Glimind reliability score of 97/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Sipyourdrink Ltd Bernstein MCP server advertises 11 tools, including explain_receipt, explain_trace_mapping, get_preset, list_adapters, list_presets.
Point your MCP client at this streamable-http endpoint: https://mcp.bernstein.run/mcp
Glimind scanned all 11 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.