Other · Remote MCP server
Handoff - shareable agent result pages + human-in-the-loop approval gates
Followable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions.
Visit Handoff - shareable agent result pages + human-in-the-loop approval gates's website
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
dev.workers.notdown-app.handoff/human-approval-decision-gate-and-shareable-result-page-publisher- Version
- 0.5.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-12
- Updated
- 2026-09-12
- Publisher
- dev.workers.notdown-app.handoff
- Namespace
- Namespace verified by the MCP Registry via the domain handoff.notdown-app.workers.dev or a parent domain of it · how
- Website
- handoff.notdown-app.workers.dev
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://handoff.notdown-app.workers.dev/mcp/{key} | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Checked
- Not requested: URL template placeholder
- Checked on
- 2026-10-05
How to connect Handoff - shareable agent result pages + human-in-the-loop approval gates
Handoff - shareable agent result pages + human-in-the-loop approval gates is a remote MCP server: there is nothing to install. Its endpoint is https://handoff.notdown-app.workers.dev/mcp/{key}, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The URL contains placeholders to fill in before connecting: {key}.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More other servers
| Server | Runs |
|---|---|
| HaldirGuardian layer for AI agents: identity, secrets, audit via MCP. | Local · stdio |
| HALLUXCheck that a package, module or DOI exists before an agent installs, imports or cites it. | Remote · HTTPLive check: ✓ handshake |
| HaltproofFail-closed deterministic checks and hash-chained receipts for AI agent outputs via MCP. | Local · stdio |
| HandoffCross-session memory for Claude over MCP - prioritised briefs, supersession, cross-project recall. | Local · stdio |
| HandoverShared, versioned context that humans and AI agents can publish, review, annotate, and continue. | Remote · HTTPLive check: ✓ handshake |
| Hands for AgentsHuman-operated physical world in the EU: make, assemble, measure, verify, ship. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| HandsetA business phone system for AI agents: send texts, place calls, read transcripts, buy numbers. | Local · stdio |
| HANRIA agent mandate checkCheck an agent action against its operator's mandate before acting: permit, deny or escalate. | Remote · HTTPLive check: ✓ handshake |