Handoff — shareable agent result pages + human-in-the-loop approval gates
REMOTE · HANDOFF.NOTDOWN-APP.WORKERS.DEV
Followable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions.
Available components
Last scanned (just now)
Scores higher than 0% of remote servers
Reachable. Last reached 27 Sep 2026.
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security0
- TLS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.Unverified
- Authorisation not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.Unverified
- HTTPS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check. View diagnostics → Unverified
- HSTS not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.Unverified
- DNSSEC not yet verified: the listed URL is a template whose key variable has no value or default, so there was no address for us to check.Unverified
Transport & Reachability0
- Transport not yet verified: the listed URL is a template whose key variable has no value or default, so there is no address for us to connect to. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 7 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 −63
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://handoff.notdown-app.workers.dev/mcp/{key}
Transports 1 probe
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| http (plaintext) | http://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D | Inconclusive |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
delete_page ~24
Delete a page you published, by id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_decision ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gate_id | string | yes | – |
No output schema declared.
No examples provided.
list_decisions ~33
List the decision gates you have created, newest first, with their status and answers.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
list_pages ~32
List the pages you have published, newest first, with their URLs and view counts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | – |
No output schema declared.
No examples provided.
publish_page ~300
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The page body. Markdown is supported (headings, lists, links, code, bold/italic, blockquotes). |
| format | string | – | How to render content. Default markdown. |
| slug | string | – | 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 f… |
| title | string | – | Page title (shown at top and in the browser tab). |
No output schema declared.
No examples provided.
request_decision ~408
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.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Optional context shown under the question — a diff summary, what will happen, links. Markdown supported. |
| expires_in_seconds | number | – | How long the gate stays open before auto-resolving to safe_default. Default 86400 (24h), max 30 days. |
| notify_url | string | – | 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-resolve… |
| options | array | – | The choices (2-6). Default ["approve","deny"]. |
| question | string | yes | The decision to put to the human, phrased as a clear question (e.g. "Deploy build 1a2b to production?"). |
| safe_default | string | – | Which option to auto-pick if no one answers before expiry. Default = the last/most-conservative option. |
No output schema declared.
No examples provided.
update_page ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | – | – |
| id | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
How do I install the Handoff — shareable agent result pages + human-in-the-loop… MCP server?
Handoff — shareable agent result pages + human-in-the-loop… is a hosted endpoint at https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · handoff.notdown-app.workers.dev
claude mcp add --transport http dev-workers-notdown-app-handoff-human-approval-d 'https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D'
What is the Handoff — shareable agent result pages + human-in-the-loop… MCP server?
Handoff — shareable agent result pages + human-in-the-loop… is an MCP server listed in the public MCP registry as dev.workers.notdown-app.handoff/human-approval-decision-gat…. Followable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions. This page covers its hosted endpoint (https://handoff.notdown-app.workers.dev/mcp/{key}).
Is the Handoff — shareable agent result pages + human-in-the-loop… MCP server safe to use?
Handoff — shareable agent result pages + human-in-the-loop… scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Handoff — shareable agent result pages + human-in-the-loop… MCP server expose?
Handoff — shareable agent result pages + human-in-the-loop… exposes 7 tools: publish_page, update_page, list_pages, delete_page, request_decision, and 2 more. Their descriptions and schemas cost roughly 995 tokens of context every time the server is loaded.
Does the Handoff — shareable agent result pages + human-in-the-loop… MCP server require authentication?
Its publisher declares no required credentials for Handoff — shareable agent result pages + human-in-the-loop…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Handoff — shareable agent result pages + human-in-the-loop… MCP server still maintained?
Handoff — shareable agent result pages + human-in-the-loop… is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.