Handoff: Send Files to Users & Agents is answering right now. Last checked moments ago. It exposes 14 tools. Last commit 30 Oct 2026.
Send a file to a user or agent as a share link with expiry, max opens, approval, revoke and logs.
Uptime history
59 hours of history
59 hours agonow
100.0%
Uptime 24h
92 of 92 checks
14
Tools
read from the server
890 ms
Response time
average over 24h
0
Stars
last commit 30 Oct 2026
Nothing serious here today
Today is the operative word: we check Handoff: Send Files to Users & Agents every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.
run in your terminal
claude mcp add handoff --transport http https://hand-off.space/mcpSettings → Connectors → Add custom connector, then paste this address
https://hand-off.space/mcp~/.codex/config.toml
[mcp_servers.handoff]
url = "https://hand-off.space/mcp".cursor/mcp.json
{
"mcpServers": {
"handoff": {
"url": "https://hand-off.space/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"handoff": {
"type": "http",
"url": "https://hand-off.space/mcp"
}
}
}Available tools 14
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
share
create_share_link
Create a controlled download link for a file you own. Use this when a person or another agent should fetch the file. The response includes url and token ONCE, plus expires_at and max_opens. Save the url immediately. Later status calls do not return it. When expires_in_hours is omitted, the link expires in 7 days. Download with GET on that url. Requires your API key.
get_share_status
Read an owned grant: token_prefix (not the secret), audience, approval, expiry, revocation, and open_count. Does not download the file and does not return the share URL. Requires your API key.
share_file
Share a file in one call and get a download link. Pass name and content_text (or content_base64). Works without an API key: if none is sent, a new account is created and its api_key is returned once; save it to revoke the link or read the access log later. Default link: anyone with the link, expires in 7 days.
update_share
Set when an owned share expires. expires_in_hours is measured from now. Example: 168 for 7 days. Does not return the token. Requires your API key.
access
get_access_log
Read the latest 1000 access attempts for an owned grant, including refused downloads. Use this to see whether a share was opened. Requires your API key.
approve
approve_share
Approve an owned grant that was created with requires_approval. Opens stay blocked until this succeeds. Requires your API key.
deny
deny_share
Deny an owned grant. A denied grant stays blocked. Requires your API key.
file
delete_file
Delete a file you own. The bytes are removed and existing share links stop working. Requires your API key.
files
list_files
List this account's files, newest first, up to 1000. Use this to find a file_id before sharing. Returns metadata only, never bytes or download URLs. Requires your API key.
revoke
revoke_share
Permanently revoke an owned share. Later downloads fail. This cannot be undone and does not delete the file. Requires your API key.
save
save_file
Save a private file for this account. Pass name and content_text or content_base64. Returns the file id and metadata. Does not share the file. Requires your API key.
shared
fetch_shared_file
Download a file from a share url or token. Use this when you were given a Handoff url and need the bytes. Honors expiry, open limits, approval, and agent audience. anyone_with_link needs no key. An agent audience uses your API key. Files up to 1048576 bytes return content_base64, plus content_text when the file is text. Larger files are not inlined: the error includes the byte size and tells you to GET the url. A successful inline return counts as an open. A file over the inline limit does not.
shares
list_shares
List grants you own. Pass file_id to limit the list to one file. Returns grant_id, status, open_count, max_opens, expires_at, and audience. Does not return tokens or download urls. Requires your API key.
signup
signup
Create a Handoff account and return an API key once. No Authorization header is required. Save api_key. On later calls send Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass api_key only if you cannot set headers. share_file can create this key for you. The key is a secret. Do not put it in a file you share.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://hand-off.space/mcp | streamable-http | answering | 5574 ms | 0 min ago |
Alternatives to Handoff: Send Files to Users & Agents
same job, measured the same wayMiniURL
by addychang
OAuth 2.1 short-link tools for AI agents with scoped tokens, approvals, audit logs, and revocation.
Willder
by willder
One memory for your AI agents: scoped, expiring, revocable per-agent tokens and an audit log.
Toolstile
by akshitkrnagpal
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
Toolstile
by toolstile
Managed MCP gateway with OAuth, per-agent permissions, shared accounts and activity logs.
CentsCheck AI Link
by centscheck
The budget app your AI agent can use. Check budgets and log spending, with no bank logins.
Orquesta
by getorquesta
Read a project's prompts, logs and agents, and send new work to the agent on your own machines.
ContextLib
by willykeenan
A project's long-term memory as plain Markdown files, with an append-only, tamper-evident log.
Logdigest
by cloudcorprecords
Condense a CI log to its failure sections and root-cause lines, with original line anchors.
Handoff: Send Files to Users & Agents — questions
Answers built from our own checks of this server.
What can Handoff: Send Files to Users & Agents do?
It exposes 14 tools, read directly from the server on our last check. Among them: approve_share, create_share_link, delete_file, deny_share, fetch_shared_file, get_access_log and 8 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
Is Handoff: Send Files to Users & Agents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 890 ms. The bar chart above shows every period we have measured.
How do I connect Handoff: Send Files to Users & Agents?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Handoff: Send Files to Users & Agents need an API key?
No. Handoff: Send Files to Users & Agents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 14 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Handoff: Send Files to Users & Agents?
It answers our handshake in 890 ms on average, which is faster than 7% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Handoff: Send Files to Users & Agents open source?
The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at hand-off.space, which runs on its operator's own terms.