io.github.sipyourdrink-ltd/bernstein-mcp

Est-ce que io.github.sipyourdrink-ltd/bernstein-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.sipyourdrink-ltd/bernstein-mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 11 outils

• explain_receipt≈ 257 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • receipt · ? · requis
    The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object.

  Exemple d'appel

  {"name": "explain_receipt", "arguments": {"receipt": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"verdict": "valid", "explanation": "texte", "receipt_sha256": "texte"}}

• explain_trace_mapping≈ 356 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • receipt · ? · optionnel
    Optional run receipt: the file contents as a string, or the parsed object.

  Exemple d'appel

  {"name": "explain_trace_mapping", "arguments": {"receipt": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"mapping": [], "verdict": "texte", "markdown": "texte", "receipt_sha256": "texte"}}

• get_preset≈ 179 tokens

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

  Paramètres, retour & exemple (1)

  Paramètres

  • name · string · requis · development | hipaa | regulated | standard

  Exemple d'appel

  {"name": "get_preset", "arguments": {"name": "development"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "config": {}, "bernstein_version": "texte"}}

• list_adapters≈ 177 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_adapters", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"adapters": [], "bernstein_version": "texte"}}

• list_presets≈ 166 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_presets", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"presets": [], "bernstein_version": "texte"}}

• server_info≈ 331 tokens

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

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "server_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"name": "texte", "limits": {}, "version": "texte", "keys_url": "texte", "verdict_key": "texte"}}

• verify_agent_manifest≈ 711 tokens

  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 checked as URIs only. The manifest hash is sha256 over the COSE payload bytes (or RFC 8785 canonical JSON for object input).

  Paramètres, retour & exemple (2)

  Paramètres

  • manifest · ? · requis
    The agent manifest: COSE envelope as base64 string, or the parsed JSON object (payload).
  • trustRecord · object · optionnel
    Optional TRACE v0.2 Trust Record to check if it cites this manifest (references[].rel == 'agent-manifest').

  Exemple d'appel

  {"name": "verify_agent_manifest", "arguments": {"manifest": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "checks": [], "summary": "texte", "verdict": "valid", "failing_check": "texte", "manifest_sha256": "texte"}}

• verify_chain≈ 416 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • kind · string · optionnel · journal | spine | audit_linkage
  • entries · ? · requis
    Rows in chain order, oldest first: a JSON array, or the raw text of the file.

  Exemple d'appel

  {"name": "verify_chain", "arguments": {"entries": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"head": "texte", "kind": "journal", "detail": "texte", "intact": true, "entries": 1, "divergent_index": "texte"}}

• verify_delegation_chain≈ 1087 tokens

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

  Paramètres, retour & exemple (2)

  Paramètres

  • context · object · optionnel
  • records · ? · requis
    The record set in any order: a JSON array of records (objects or strings), or the raw text of a file.

  Exemple d'appel

  {"name": "verify_delegation_chain", "arguments": {"records": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "walk": [], "codes": [], "depth": 1, "failures": [], "warnings": [], "classification": "verified", "first_broken_link": "texte"}}

• verify_receipt≈ 932 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • receipt · ? · requis
    The run receipt: pass the file contents as a string for byte-exact verification, or the parsed object.

  Exemple d'appel

  {"name": "verify_receipt", "arguments": {"receipt": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "checks": [], "summary": "texte", "verdict": "valid", "keys_url": "texte", "verify_url": "texte", "failing_check": "texte", "divergent_step": "texte", "receipt_sha256": "texte", "signed_verdict": "texte"}}

• verify_trace_record≈ 711 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • record · ? · requis
    A TRACE v0.2 Trust Record: the file contents as a string, or the parsed object.

  Exemple d'appel

  {"name": "verify_trace_record", "arguments": {"record": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "checks": [], "summary": "texte", "verdict": "valid", "failing_check": "texte", "record_sha256": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.bernstein.run/mcp