accueil / serveurs / Dev & Code / io.github.MarkovianProtocol/provenance
io.github.MarkovianProtocol/provenance
serveur MCP (Model Context Protocol) · markovian 0.2.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que io.github.MarkovianProtocol/provenance est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.MarkovianProtocol/provenance » 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 4 outils
- markovian_notarize≈ 324 tokens
Notarize any file or hash into a public transparency log cosigned by 7 witnesses from 6 operators and anchored to Bitcoin. Hash-only: pass a sha256 hex string, or with the local stdio server a file path (hashed on your machine; the file never leaves it) — only 32 bytes reach the log. Returns a receipt with the leaf index, inclusion-proof URL, an offline c2sp.org/tlog-proof bundle URL, and the witness trust policy. Proves the hash existed no later than the covering checkpoint, in a single history everyone sees identically; does NOT prove authorship or that the content is true. Rate-limited (10/hour). Typical use: notarize an output the moment it is produced, keep the file, hand anyone the proof URL.
Paramètres, retour & exemple (2)
Paramètrespath· string · optionnel
Local stdio server only: file to notarize, hashed on your machine and never uploaded. The hosted server refuses it.sha256· string · optionnel
Alternatively, a sha256 hex digest (with or without 'sha256:' prefix).
Exemple d'appel{"name": "markovian_notarize", "arguments": {"path": "texte", "sha256": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - markovian_stamp≈ 754 tokens
Commit any data (an AI output, a decision, a record) into a public, witnessed transparency log and get back a verifiable, tamper-evident provenance stamp (canonical markovian-provenance/v1). It proves the data existed and was committed at this time; it does NOT assert the data is correct (provenance, not truth). No wallet, account, or funding is required, the first stamp just works, and only the SHA-256 hash of your data is sent to the public API, the raw data is never stored. The returned merkle_root is the handle: save it, then call markovian_verify(merkle_root) to prove integrity later, or pass prior stamps in derived_from to build a lineage you can walk with markovian_trace. Typical use: stamp an agent output the moment it is produced, so anyone can later confirm it was not altered.
Paramètres, retour & exemple (4)
Paramètresdata· string · requis
Exact bytes/string to stamp. Hashed server-side; raw data is not stored.label· string · optionnel
Optional human label for the stamp.wallet· string · optionnel
Optional. Omit and the protocol mints an ephemeral committer for you. Provide one to attribute the stamp.derived_from· array · optionnel
Optional lineage. A list of prior stamps this output was derived from, each {merkle_root, data_hash}. Bound inside the committed bytes so the link is tamper-evident; the payload is published so markovian_trace can walk it.
Exemple d'appel{"name": "markovian_stamp", "arguments": {"data": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"issuer": "texte", "schema": "texte", "verify": "texte", "wallet": "texte", "data_hash": "texte", "stamped_at": "texte", "attestation": "texte", "merkle_root": "texte", "block_height": 1, "zk_commitment": "texte"}} - markovian_trace≈ 206 tokens
Walk and verify a stamp's full provenance lineage by merkle_root. Use this when a stamp was created with derived_from links, to map what an output was built from. Returns a MAP of the graph (not a yes/no verdict): each node carries hash_binds and anchored, each edge carries edge_verified, and `valid` is true only if every node and edge checks out. A node whose payload was never published is an unresolved frontier (resolved:false). Read-only. Provenance, not truth.
Paramètres, retour & exemple (1)
Paramètresmerkle_root· string · requis
root of the stamp to trace.
Exemple d'appel{"name": "markovian_trace", "arguments": {"merkle_root": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - markovian_verify≈ 249 tokens
Look up a Markovian stamp by its merkle_root against the public verifier, with no key or account. verified:true means the stamp record exists and the response echoes its committed data_hash — recompute your content's SHA-256 and compare it to that data_hash yourself to confirm the content is unaltered. An unknown merkle_root returns verified:false. The trust-nobody path is the stamp's witnessed transparency-log leaf (log_index / inclusion URL from markovian_stamp): its inclusion proof verifies against the witnessed log head with no trust in this endpoint. Read-only; anyone can run it, including a party who does not trust the stamper.
Paramètres, retour & exemple (1)
Paramètresmerkle_root· string · requis
merkle_root to verify.
Exemple d'appel{"name": "markovian_verify", "arguments": {"merkle_root": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
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é ».