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

- Trust score: 0/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `handoff.notdown-app.workers.dev`: 0/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-notdown-app-handoff-human-approval-decision-gate-and-shareable-resul/mcp-key.md), [page](https://verifymcp.io/servers/dev-workers-notdown-app-handoff-human-approval-decision-gate-and-shareable-resul/mcp-key)

## Channel facts

- Endpoint: `https://handoff.notdown-app.workers.dev/mcp/{key}`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-24.

- **Endpoint Security**: 0/100
  - 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.
  - 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.
  - 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.
  - 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.
  - 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.
- **Transport & Reachability**: 0/100
  - 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.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

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

## Install

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

### Claude

```bash
claude mcp add --transport http dev-workers-notdown-app-handoff-human-approval-d 'https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-handoff-human-approval-d": {
      "url": "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-notdown-app-handoff-human-approval-d": {
      "type": "http",
      "url": "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-notdown-app-handoff-human-approval-d]
url = "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-notdown-app-handoff-human-approval-d": {
      "type": "remote",
      "url": "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-notdown-app-handoff-human-approval-d --url 'https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-notdown-app-handoff-human-approval-d:
    url: "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-notdown-app-handoff-human-approval-d": {
      "Transport": "http",
      "Url": "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-notdown-app-handoff-human-approval-d -t streamable-http -u 'https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-notdown-app-handoff-human-approval-d": {
      "type": "http",
      "url": "https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 0, −63)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 63, +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.

### 2026-09-25 (score 62, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 62, +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.

### 2026-09-21 (score 61, +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.

### 2026-09-13 (score 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-12 (score 0)

First indexed and scored.

## MCP tools (7)

### `publish_page` (~300 tokens)

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.

Input parameters:

- `content` (string, required): 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).

### `update_page` (~115 tokens)

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.

Input parameters:

- `content` (string)
- `id` (string, required)
- `title` (string)

### `list_pages` (~32 tokens)

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

Input parameters:

- `limit` (number)

### `delete_page` (~24 tokens)

Delete a page you published, by id.

Input parameters:

- `id` (string, required)

### `request_decision` (~408 tokens)

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.

Input parameters:

- `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, required): 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.

### `get_decision` (~83 tokens)

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.

Input parameters:

- `gate_id` (string, required)

### `list_decisions` (~33 tokens)

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

Input parameters:

- `limit` (number)

## Diagnostics

Captured diagnostic sections: Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-notdown-app-handoff-human-approval-decision-gate-and-shareable-resul/mcp-key#diagnostics

## Score history

- 2026-10-24: 0
- 2026-10-23: 0
- 2026-10-22: 0
- 2026-10-21: 0
- 2026-10-20: 0
- 2026-10-19: 0
- 2026-10-18: 0
- 2026-10-17: 0
- 2026-10-16: 0
- 2026-10-15: 0
- 2026-10-14: 0
- 2026-10-13: 0
- 2026-10-12: 0
- 2026-10-10: 0
- 2026-10-05: 0
- 2026-10-04: 0
- 2026-10-03: 0
- 2026-10-02: 0
- 2026-10-01: 0
- 2026-09-30: 0
- 2026-09-29: 0
- 2026-09-28: 0
- 2026-09-27: 63
- 2026-09-26: 63
- 2026-09-25: 62
- 2026-09-24: 62
- 2026-09-23: 62
- 2026-09-22: 61
- 2026-09-21: 61
- 2026-09-20: 60

## Common questions

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

## Links

- Remote endpoint: https://handoff.notdown-app.workers.dev/mcp/%7Bkey%7D
- Website: https://handoff.notdown-app.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-notdown-app-handoff-human-approval-decision-gate-and-shareable-resul/mcp-key.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-notdown-app-handoff-human-approval-decision-gate-and-shareable-resul/mcp-key.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-notdown-app-handoff-human-approval-decision-gate-and-shareable-resul/mcp-key