_ registry / mcp streamable-http · checked 56m ago

temoinpublic

https://temoinpublic.fr

Registry code: d7770a6b4e240e6f

api record

Témoin public prouve qu’un document existait à une date, sans modification. Pour prouver ce qu’une page web disait aujourd’hui : dater_url. Donnez toujours à l’utilisateur l’adresse du reçu et le reçu complet : c’est sa preuve. Vérification humaine : https://temoinpublic.fr/verifier

endpoint
https://temoinpublic.fr/mcp
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 temoinpublic live?
Yes — it answered the hub's last check (checked 56m ago). It answered 100% of checks over the last 30 days.
Is temoinpublic free to use?
Yes — the hub reached it with no key and no payment.
What tools does temoinpublic have?
4 tools: chercher_empreinte, lire_recu, dater_url, dater_empreinte.
Is temoinpublic 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
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
140ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

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

  • chercher_empreinte unknown 56m ago

    Rend chaque dépôt de cette empreinte SHA-256 : jour, ligne du registre, adresse du reçu. Aucun dépôt : le document n’a pas été daté par ce service.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sha256"
      ],
      "properties": {
        "sha256": {
          "type": "string",
          "pattern": "^[0-9a-fA-F]{64}$",
          "description": "Empreinte SHA-256, 64 caractères hexadécimaux."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • lire_recu unknown 56m ago

    Rend la ligne publique d’un reçu par son identifiant (64 caractères hexadécimaux) : empreinte, jour, ligne du registre.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "pattern": "^[0-9a-f]{64}$"
        }
      },
      "additionalProperties": false
    }
    arguments 13 lines
  • dater_url unknown never probed

    Le service lit lui-même l’adresse publique (http ou https, 20 Mo et 30 s au plus) et inscrit l’empreinte SHA-256 des octets lus dans le registre public, ancré dans Bitcoin. Rend le reçu : à remettre à l’utilisateur, il prouve que ce contenu était servi à cette adresse à cet instant. Une même adresse se lit une fois par jour.

    mcp-tool

    {
      "type": "object",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "description": "Adresse publique à lire."
        },
        "libelle": {
          "type": "string",
          "maxLength": 200,
          "description": "Un nom pour s’y retrouver ; il reste dans le reçu, jamais publié."
        }
      },
      "additionalProperties": false
    }
    arguments 18 lines
  • dater_empreinte unknown never probed

    Inscrit dans le registre public l’empreinte SHA-256 d’un document que l’utilisateur garde ; le document n’est jamais envoyé. Rend le reçu, qui prouve que ce document existait à cette date, sans modification.

    mcp-tool

    {
      "type": "object",
      "required": [
        "sha256"
      ],
      "properties": {
        "sha256": {
          "type": "string",
          "pattern": "^[0-9a-fA-F]{64}$",
          "description": "Empreinte SHA-256, 64 caractères hexadécimaux."
        },
        "libelle": {
          "type": "string",
          "maxLength": 200,
          "description": "Un nom pour s’y retrouver ; il reste dans le reçu, jamais publié."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
_ try it 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 d7770a6b4e240e6f.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/d7770a6b4e240e6f/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/d7770a6b4e240e6f/badge.svg)](https://brick.blue/agent/d7770a6b4e240e6f?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 know
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
0
ok
0
failed
0
success rate
—
median latency
—
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
—

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