Handoff

io.github.tiagoyonaminePublished by GitHub account tiagoyonaminev1.0.0Updated Oct 24, 2026

IT asset management — track equipment, allocations, and digital responsibility terms for your team.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Lets an assistant manage IT assets, including equipment, allocations, and digital responsibility terms for a team.

What you can do
Handoff is a remote MCP endpoint for an IT asset management service, letting an assistant work with equipment tracking, allocation records, and digital responsibility terms for a team. The tool list is not published in the supplied information, so the exact operations depend on the service.
When to use it
Use it when a team wants an assistant to look up or manage IT assets, equipment allocations, and digital responsibility terms. It fits organizations already tracking assets on the Handoff platform.
Requirements
Needs a connection to the remote endpoint and OAuth authentication. No local package or environment variables are required.
Before you install
OAuth grants access to an organization's asset and allocation data and may allow records to be written or changed; confirm the granted scopes and available actions before installing.

Installation

In SourceWeft

  1. Open Handoff 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.tiagoyonamine%2Fhandoff/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://app.usehandoff.com.br/api/mcp"
    }
  }
}

README

This repository has no README.

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.0LatestSep 16, 2026

Score

60% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.