_ registry / mcp streamable-http · checked 1h ago

Handoff

https://handoff.notdown-app.workers.dev

Registry code: 974559ec4ccd1f29

api record

Followable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions.

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

endpoint
https://handoff.notdown-app.workers.dev/mcp/{key}
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 Handoff live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Handoff free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does Handoff have?
7 tools: update_page, request_decision, publish_page, list_decisions, delete_page, list_pages, get_decision.
Is Handoff 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 99.4%· all time 99.4%

latency
1,122ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 333 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • publish a shareable result page
  • ask a human for approval
  • check a decision gate status
takes → gives
text → web pages, data
tools
3 reads3 changes data1 sends messages
_ 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 7 tools
7 auth-required 7 of 7 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.

  • update_page changes data auth-required never probed

    Update the title and/or content of a page you previously published; the URL never changes. Use this to keep one stable link current across sessions or runs — a live status page, a running changelog, an append-as-you-go log, or a dashboard the recipient can bookmark once and always see fresh. Each update notifies anyone subscribed to the page's RSS/JSON feed, so updating is how followers stay in the loop.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        },
        "title": {
          "type": "string"
        },
        "content": {
          "type": "string"
        }
      }
    }
    arguments 17 lines
  • request_decision sends messages auth-required never probed

    Ask a specific human for a bounded yes/no (or pick-one) decision BEFORE you do something irreversible or high-stakes — deploy, send, delete, charge, merge, publish. Returns a gate_url you hand to the person: they open it in a browser and click one option, no login. Unlike a followable page (awareness), this is a real gate — exactly one authorized answer that resolves the decision, or it auto-resolves to a safe default at expiry so your run never hangs forever. Then call get_decision to read what they chose. The gate page is a durable audit trail of what was asked, what was answered, and when. Use this instead of blocking on a human in chat, or when the human isn't watching the session.

    mcp-tool

    {
      "type": "object",
      "required": [
        "question"
      ],
      "properties": {
        "detail": {
          "type": "string",
          "description": "Optional context shown under the question — a diff summary, what will happen, links. Markdown supported."
        },
        "options": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "The choices (2-6). Default [\"approve\",\"deny\"]."
        },
        "question": {
          "type": "string",
          "description": "The decision to put to the human, phrased as a clear question (e.g. \"Deploy build 1a2b to production?\")."
        },
        "notify_url": {
          "type": "string",
          "description": "Optional https webhook. Handoff POSTs a JSON payload to it when the gate is created ({event:'gate.created', gate_url, question, options, expires_at}) and again when a human answers or it auto-resolves ({event:'gate.answered', answer, status}). Point this at a push/notification channel so the human is alerted to the pending decision instead of you having to deliver the link yourself. Best-effort, https only."
        },
        "safe_default": {
          "type": "string",
          "description": "Which option to auto-pick if no one answers before expiry. Default = the last/most-conservative option."
        },
        "expires_in_seconds": {
          "type": "number",
          "description": "How long the gate stays open before auto-resolving to safe_default. Default 86400 (24h), max 30 days."
        }
      }
    }
    arguments 35 lines
  • publish_page changes data auth-required never probed

    Publish text or markdown as a clean, shareable public web page and get back a URL you can hand to a human. Use this whenever you produce a report, summary, plan, table, or any result a person should read in a browser instead of the chat window. The page is FOLLOWABLE: the human can subscribe to it via RSS/JSON (returned as feed_url/json_url) and gets the new version whenever you re-publish — so they never have to ask you for an update. To keep ONE page updated across runs/sessions, pass a stable `slug`: publishing again with the same slug overwrites the same page at the same URL — no need to remember a generated id. Mention the subscribe option when you hand over the link.

    mcp-tool

    {
      "type": "object",
      "required": [
        "content"
      ],
      "properties": {
        "slug": {
          "type": "string",
          "description": "Optional stable name for a page you intend to keep updating (e.g. \"deploy-status\", \"nightly-report\"). Re-publishing with the same slug updates that same page in place at the same URL. Perfect for a fresh-context agent that can't remember a generated id — just reuse the slug. Omit for a one-off page with a random id."
        },
        "title": {
          "type": "string",
          "description": "Page title (shown at top and in the browser tab)."
        },
        "format": {
          "enum": [
            "markdown",
            "text"
          ],
          "type": "string",
          "description": "How to render content. Default markdown."
        },
        "content": {
          "type": "string",
          "description": "The page body. Markdown is supported (headings, lists, links, code, bold/italic, blockquotes)."
        }
      }
    }
    arguments 28 lines
  • list_decisions reads auth-required 9h ago

    List the decision gates you have created, newest first, with their status and answers.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number"
        }
      }
    }
    arguments 8 lines
  • delete_page changes data auth-required never probed

    Delete a page you published, by id.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string"
        }
      }
    }
    arguments 11 lines
  • list_pages reads auth-required 9h ago

    List the pages you have published, newest first, with their URLs and view counts.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "number"
        }
      }
    }
    arguments 8 lines
  • get_decision reads auth-required 9h ago

    Read the current state of a decision gate you created with request_decision. Returns status (pending / resolved / timed_out), the chosen answer (once answered or auto-resolved), and timing. Poll this to find out what the human decided; if status is still 'pending' no one has answered yet and it hasn't expired.

    mcp-tool

    {
      "type": "object",
      "required": [
        "gate_id"
      ],
      "properties": {
        "gate_id": {
          "type": "string"
        }
      }
    }
    arguments 11 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 974559ec4ccd1f29.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/974559ec4ccd1f29/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/974559ec4ccd1f29/badge.svg)](https://brick.blue/agent/974559ec4ccd1f29?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
100%

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.