Server definition
- Hash
- sha256:11a2ee5ffdc0c5115d14cc594f28984db59889afdd17dfcbf9a66e25b4ec6942
- What it is
- What a remote MCP server returned when asked what it offers: 4 tools
The blob, as servednamed by its sha256
{
"instructions": null,
"tools": [
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"path": {
"description": "Local stdio server only: file to notarize, hashed on your machine and never uploaded. The hosted server refuses it.",
"type": "string"
},
"sha256": {
"description": "Alternatively, a sha256 hex digest (with or without 'sha256:' prefix).",
"type": "string"
}
},
"type": "object"
},
"name": "markovian_notarize",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"data": {
"description": "Exact bytes/string to stamp. Hashed server-side; raw data is not stored.",
"type": "string"
},
"derived_from": {
"description": "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.",
"items": {
"properties": {
"data_hash": {
"type": "string"
},
"merkle_root": {
"type": "string"
},
"relationship": {
"type": "string"
}
},
"required": [
"merkle_root",
"data_hash"
],
"type": "object"
},
"type": "array"
},
"label": {
"description": "Optional human label for the stamp.",
"type": "string"
},
"wallet": {
"description": "Optional. Omit and the protocol mints an ephemeral committer for you. Provide one to attribute the stamp.",
"type": "string"
}
},
"required": [
"data"
],
"type": "object"
},
"name": "markovian_stamp",
"outputSchema": {
"properties": {
"attestation": {
"type": "string"
},
"block_height": {
"description": "Legacy field, null for stamps after 2026-07. Historical values are internal sequence heights of a retired chain (never a Bitcoin block).",
"type": [
"integer",
"null"
]
},
"data_hash": {
"type": "string"
},
"issuer": {
"description": "The committer handle, as named in the transparency-log leaf. Attribution metadata, not a cryptographic identity.",
"type": "string"
},
"merkle_root": {
"type": "string"
},
"schema": {
"type": "string"
},
"stamped_at": {
"type": "string"
},
"verify": {
"type": "string"
},
"wallet": {
"description": "Compatibility alias for issuer (kept because existing clients require it).",
"type": "string"
},
"zk_commitment": {
"description": "Legacy field, null for stamps after 2026-07. Historical values are Pedersen points that shipped without an opening, so clients could never check them.",
"type": [
"string",
"null"
]
}
},
"required": [
"schema",
"merkle_root",
"data_hash",
"wallet",
"stamped_at",
"verify",
"attestation"
],
"type": "object"
}
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"merkle_root": {
"description": "root of the stamp to trace.",
"type": "string"
}
},
"required": [
"merkle_root"
],
"type": "object"
},
"name": "markovian_trace",
"outputSchema": null
},
{
"description": "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.",
"inputSchema": {
"additionalProperties": false,
"properties": {
"merkle_root": {
"description": "merkle_root to verify.",
"type": "string"
}
},
"required": [
"merkle_root"
],
"type": "object"
},
"name": "markovian_verify",
"outputSchema": null
}
]
}Verify it yourself
curl -s https://api.teppi.xyz/v1/evidence/sha256:11a2ee5ffdc0c5115d14cc594f28984db59889afdd17dfcbf9a66e25b4ec6942 | sha256sum