Other · Remote MCP server
Handoff
IT asset management - track equipment, allocations, and digital responsibility terms for your team.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.tiagoyonamine/handoff- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-05-26
- Updated
- 2026-05-26
- Publisher
- tiagoyonamine (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/tiagoyonamine) · how
- Website
- usehandoff.com.br
- Repository
- github.com/tiagoyonamine/handoff
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.usehandoff.com.br/api/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.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401
- Checked on
- 2026-10-05
How to connect Handoff
Handoff is a remote MCP server: there is nothing to install. Its endpoint is https://app.usehandoff.com.br/api/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 other servers
| Server | Runs |
|---|---|
| HALLUXCheck that a package, module or DOI exists before an agent installs, imports or cites it. | Remote · HTTPLive check: ✓ handshake |
| Halowerk MCP134 paid APIs as MCP tools, billed per call in USDC on Base. No account, no login. | Local · stdio |
| 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 |
| 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 |
| Handoff MCP ServerDurable agent-to-agent handoffs and shared scratchpad for multi-agent workflows. | Remote · HTTPLive check: sign-in required |
| 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 |