mcpbeat Sign in

Handoff — shareable agent result pages + human-in-the-loop approval gates MCP Server

by workers-notdown-app-handoff Your server? Claim it
answering

Handoff — shareable agent result pages + human-in-the-loop approval gates is answering right now. Last checked 9 min ago. It exposes 7 tools.

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

Uptime history 64 days of history · worst day 77%
64 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
341 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 7

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 7 September 2026. No other catalogue keeps this.

12 Sep a tool changed the parameters it asks for request_decision
10 Sep 3 tools appeared get_decision, list_decisions, request_decision
10 Sep a tool changed version
7 Sep 2 tool descriptions were rewritten publish_page, update_page

Nothing serious here today

Today is the operative word: we check Handoff — shareable agent result pages + human-in-the-loop approval gates every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

run in your terminal
claude mcp add publish-shareable-result-page --transport http 'https://handoff.notdown-app.workers.dev/mcp/{key}'
Settings → Connectors → Add custom connector, then paste this address
https://handoff.notdown-app.workers.dev/mcp/{key}
~/.codex/config.toml
[mcp_servers.publish-shareable-result-page]
url = "https://handoff.notdown-app.workers.dev/mcp/{key}"
.cursor/mcp.json
{
  "mcpServers": {
    "publish-shareable-result-page": {
      "url": "https://handoff.notdown-app.workers.dev/mcp/{key}"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "publish-shareable-result-page": {
      "type": "http",
      "url": "https://handoff.notdown-app.workers.dev/mcp/{key}"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

page
delete_page
Delete a page you published, by id.
update_page
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.
decision
get_decision
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.
decisions
list_decisions
List the decision gates you have created, newest first, with their status and answers.
pages
list_pages
List the pages you have published, newest first, with their URLs and view counts.
publish
publish_page
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.
request
request_decision
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.

Endpoints

URLTransportStateLatencyChecked
https://handoff.notdown-app.workers.dev/mcp/{key} streamable-http answering 468 ms 9 min ago

Alternatives to Handoff — shareable agent result pages + human-in-the-loop approval gates

same job, measured the same way
Handoff — shareable agent result pages + human-in-the-loop approval gates
by workers-notdown-app-handoff

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

7 tools answering
G
Glyt
by glyt

Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.

6 tools answering
Logi Approval
by 1pass

logi Agent Approval Gate — human approval on the phone before high-risk agent actions.

51 installs/wk local only
X-EGO
by x-ego

Human approval for irreversible AI agent actions, bound to the exact tool call by a passkey tap

4 tools answering
AgentGate
by agentkitai

Human-in-the-loop approval gateway for AI agents over MCP: request, decide, approve.

57 installs/wk local only
Approval Gate MCP
by itcustomsolution

Fail-closed human approval gates for AI agent actions. Default-deny, TTL expiry, audit log.

124 installs/wk local only
Lassare
by lassare

Human-in-the-loop for AI coding agents — ask questions, get approvals via Slack.

answering
Impri
by sekera-radim

Impri MCP server — human-in-the-loop approval inbox for AI agents

48 installs/wk 8 tools answering

Handoff — shareable agent result pages + human-in-the-loop approval gates — questions

Answers built from our own checks of this server.

What can Handoff — shareable agent result pages + human-in-the-loop approval gates do?
It exposes 7 tools, read directly from the server on our last check. Among them: delete_page, get_decision, list_decisions, list_pages, publish_page, request_decision and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Handoff — shareable agent result pages + human-in-the-loop approval gates working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 341 ms. The bar chart above shows every period we have measured.
How do I connect Handoff — shareable agent result pages + human-in-the-loop approval gates?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Handoff — shareable agent result pages + human-in-the-loop approval gates need an API key?
No. Handoff — shareable agent result pages + human-in-the-loop approval gates completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Handoff — shareable agent result pages + human-in-the-loop approval gates?
It answers our handshake in 341 ms on average, which is faster than 41% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.