Summary
Built for orchestrating work across multiple AI agents, this server provides durable handoff primitives and a shared scratchpad over MCP's HTTP transport. It runs on Railway with optional Xpay proxy support and stores state to disk. Discovery endpoints are public by default, but tool execution requires API key auth via Bearer token or x-api-key header. You'd reach for this when coordinating agent chains where context needs to persist across sessions or when one agent's output becomes another's input. The dual-remote setup (Railway + Xpay) gives you flexibility in how clients authenticate and connect.
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
handoff-mcp-server
Durable handoffs and shared scratchpad for multi-agent workflows over MCP (HTTP transport).
Endpoints
GET /basic service infoGET /healthhealth and storage statsPOST /mcpJSON-RPC MCP endpointGET /robots.txtdiscovery fileGET /llms.txtdiscovery fileGET /sitemap.xmldiscovery file
Environment Variables
PORTdefault3000DATA_DIRdefault/dataMCP_API_KEYrequired in production (NODE_ENV=production)PUBLIC_MCP_DISCOVERYdefaulttruePUBLIC_BASE_URLoptional, 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 whenPUBLIC_MCP_DISCOVERY=true. tools/callrequires valid upstream auth whenMCP_API_KEYis set:Authorization: Bearer <MCP_API_KEY>orx-api-key: <MCP_API_KEY>
Xpay + Railway Configuration (Required)
- Railway variables:
MCP_API_KEY=<your-strong-key>PUBLIC_MCP_DISCOVERY=truePUBLIC_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-keyor Bearer token matchingMCP_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
- URL:
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.
Featured
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
