_ registry / mcp + a2a streamable-http · checked 13h ago

markovian

https://api.quantsynth.net

Registry code: 799964fa92718cda

api record

Stamp any data to the Markovian chain for a verifiable provenance receipt. Proves timing, not truth.

from a public catalogue that lists it, not from the operator

endpoint
https://api.markovianprotocol.com/mcp/
door code
40dc50752034ae77
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is markovian live?
No — it has stopped answering the hub's checks (checked 13h ago). It answered 0% of checks over the last 30 days.
Is markovian free to use?
Not measured yet.
What tools does markovian have?
4 tools: markovian_stamp, markovian_verify, markovian_trace, markovian_notarize.
Is markovian safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
down
uptime, 30 days
0%

90 days 87.9%· all time 88.3%

latency
499ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 174 checks · signed record
  • degraded → down· HTTP 530
  • degraded → down· HTTP 530
  • live → degraded· HTTP 530
  • live → degraded· HTTP 530
_ what it is for
used for
  • stamp data into a transparency log
  • notarize a file hash
  • verify a provenance stamp
  • trace a stamp's lineage
takes → gives
data, documents → data
tools
2 reads2 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
4 never probed 0 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • markovian_stamp changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "data"
      ],
      "properties": {
        "data": {
          "type": "string",
          "description": "Exact bytes/string to stamp. Hashed server-side; raw data is not stored."
        },
        "label": {
          "type": "string",
          "description": "Optional human label for the stamp."
        },
        "wallet": {
          "type": "string",
          "description": "Optional. Omit and the protocol mints an ephemeral committer for you. Provide one to attribute the stamp."
        },
        "derived_from": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "merkle_root",
              "data_hash"
            ],
            "properties": {
              "data_hash": {
                "type": "string"
              },
              "merkle_root": {
                "type": "string"
              },
              "relationship": {
                "type": "string"
              }
            }
          },
          "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."
        }
      },
      "additionalProperties": false
    }
    arguments 43 lines
  • markovian_verify reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "merkle_root"
      ],
      "properties": {
        "merkle_root": {
          "type": "string",
          "description": "merkle_root to verify."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • markovian_trace reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "merkle_root"
      ],
      "properties": {
        "merkle_root": {
          "type": "string",
          "description": "root of the stamp to trace."
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • markovian_notarize changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "path": {
          "type": "string",
          "description": "Local stdio server only: file to notarize, hashed on your machine and never uploaded. The hosted server refuses it."
        },
        "sha256": {
          "type": "string",
          "description": "Alternatively, a sha256 hex digest (with or without 'sha256:' prefix)."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 799964fa92718cda.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/799964fa92718cda/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/799964fa92718cda/badge.svg)](https://brick.blue/agent/799964fa92718cda?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we knowoff the mcp door
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
1
ok
0
failed
1
success rate
0%
median latency
83ms
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

1 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.