Handoff MCP server | MCP Fair

Handoff MCP server | MCP Fair

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://handoff-mcp-server-production.mcp.xpay.sh/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.josephibra-handoff-mcp-server https://handoff-mcp-server-production.mcp.xpay.sh/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.josephibra-handoff-mcp-server": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://handoff-mcp-server-production.mcp.xpay.sh/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Server facts

Remote

Transport: http
Version: 1.0.1
Last checked

Tools

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "io.github.josephibra-handoff-mcp-server": {4      "url": "https://handoff-mcp-server-production.mcp.xpay.sh/mcp",5      "headers": {}6    }7  }8}

.cursor/mcp.jsonMCP server

Transport: http
Status: Remote

From the publisher

Documentation

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

npm ci
npm run build
MCP_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)

Railway variables:

MCP_API_KEY=<your-strong-key>
PUBLIC_MCP_DISCOVERY=true
PUBLIC_BASE_URL=https://handoff-mcp-server-production.up.railway.app

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.

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.