Handoff Mcp Server

io.github.josephibraPublished by GitHub account josephibrav1.0.1Updated Oct 24, 2026

Durable agent-to-agent handoffs and shared scratchpad for multi-agent workflows.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

A remote MCP service for durable agent-to-agent handoffs and a shared scratchpad, so multiple agents can pass work and notes between each other.

What you can do
Pass work between agents as durable handoffs, so a task started by one agent can be picked up by another without losing state, per the description and README. Share a common scratchpad that multiple agents read and write during a multi-agent workflow. Expose the service over an HTTP MCP endpoint, with separate endpoints for service info, health and storage stats, and discovery files. The README does not list individual tools, so the exact tool set is not documented here.
When to use it
Worth adding when you run multi-agent workflows and need agents to hand tasks to each other or share working notes across steps, rather than keeping everything in one agent's context.
Requirements
A remote endpoint reached over streamable HTTP; OAuth authentication is declared as required. The README also describes an API key supplied as a Bearer token or an x-api-key header for tool calls, and an Xpay key passed in the URL query when going through the Xpay host. No local runtime is needed.
Before you install
The README asks for secrets in several places: an API key in a header and an Xpay key in the URL query string, which can leak through logs and shared links. Tool calls require valid authentication, and the README notes that requests without the Xpay key are not forwarded. Handoffs and scratchpad content are stored server-side, so anything written there leaves your machine; avoid putting sensitive data in shared notes.

Installation

In SourceWeft

  1. Open Handoff Mcp Server in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.josephibra%2Fhandoff-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "handoff": {
      "type": "http",
      "url": "https://handoff-mcp-server-production.mcp.xpay.sh/mcp"
    }
  }
}

README

handoff-mcp-server

Durable handoffs and shared scratchpad for multi-agent workflows over MCP (HTTP transport).

Endpoints

  • GET / basic service info
  • GET /health health and storage stats
  • POST /mcp JSON-RPC MCP endpoint
  • GET /robots.txt discovery file
  • GET /llms.txt discovery file
  • GET /sitemap.xml discovery file

Environment Variables

  • PORT default 3000
  • DATA_DIR default /data
  • MCP_API_KEY required in production (NODE_ENV=production)
  • PUBLIC_MCP_DISCOVERY default true
  • PUBLIC_BASE_URL optional, used for absolute links in discovery files

Local Run

bash
npm cinpm run buildMCP_API_KEY=test-secret node dist/index.js

MCP Auth Behavior

  • Discovery methods (initialize, tools/list, resources/list, prompts/list, ping) can be public when PUBLIC_MCP_DISCOVERY=true.
  • tools/call requires valid upstream auth when MCP_API_KEY is set:
    • Authorization: Bearer <MCP_API_KEY> or
    • x-api-key: <MCP_API_KEY>

Xpay + Railway Configuration (Required)

  1. Railway variables:
  • MCP_API_KEY=<your-strong-key>
  • PUBLIC_MCP_DISCOVERY=true
  • PUBLIC_BASE_URL=https://handoff-mcp-server-production.up.railway.app
  1. Xpay MCP URL:
  • Use https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...
  • Without ?key=..., Xpay returns auth required and requests will not forward.
  1. Client calls through Xpay:
  • Keep the Xpay key in URL.
  • Also send upstream auth header for tools/call (x-api-key or Bearer token matching MCP_API_KEY).

Publishing

MCP Registry

  • Server name: io.github.josephibra/handoff-mcp-server
  • Primary remote: Xpay URL (with key at client usage time, not committed)
  • Secondary remote: Railway URL

Smithery

  • Namespace: josephibrahim
  • Server ID: handoff-mcp-server
  • MCP Server URL: https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...

Agentverse

  • Create a new agent and attach MCP server:
    • URL: https://handoff-mcp-server-production.mcp.xpay.sh/mcp?key=xpay_sk_...
    • Headers: x-api-key: <MCP_API_KEY> for tool execution paths

Recommended Extra Discovery Listings

  • PulseMCP directory
  • mcp.so
  • OpenTools catalog
  • MCPmarket / mcpservers.org

Use the same canonical MCP URL and matching auth notes everywhere to avoid inconsistent behavior.

Source: README.md at commit 43de49c

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.