Other · Remote MCP server
Handoff MCP Server
Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.josephibra/handoff-mcp-server- Version
- 1.0.1
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-05-14
- Updated
- 2026-05-14
- Publisher
- josephibra (GitHub) · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/josephibra) · how
- Repository
- github.com/josephibra/handoff-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://handoff-mcp-server-production.mcp.xpay.sh/mcp | None |
| Streamable HTTP | https://handoff-mcp-server-production.up.railway.app/mcp | 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.
- Endpoint
https://handoff-mcp-server-production.mcp.xpay.sh/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
- Endpoint
https://handoff-mcp-server-production.up.railway.app/mcp(HTTP)- Reachable
- Yes (HTTP 404)
- Handshake
- HTTP 404
- Checked on
- 2026-10-05
How to connect Handoff MCP Server
Handoff MCP Server is a remote MCP server: there is nothing to install. Its endpoints are https://handoff-mcp-server-production.mcp.xpay.sh/mcp and https://handoff-mcp-server-production.up.railway.app/mcp, 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.
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; the live check above only shows whether the endpoint answered. 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 from josephibra (GitHub)
| Server | Runs |
|---|---|
| Shadowgate MCPSecurity firewall for AI agents - scans MCP calls for injection, secrets, and risks. | Remote · HTTPLive check: sign-in required |
More other servers
| Server | Runs |
|---|---|
| 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 |
| HandoffIT asset management - track equipment, allocations, and digital responsibility terms for your team. | Remote · HTTPLive check: sign-in required |
| Handoff - shareable agent result pages + human-in-the-loop approval gatesFollowable agent result pages + human-in-the-loop yes/no approval gates before irreversible actions. | Remote · HTTP |
| 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 |