MCP server for terminal commands, file operations, and process management
Nothing to run from here
Handoff: Send Files to Users & Agents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
90/100
tool-list score
14
tools declared
remote
at its publisher
—
calls last 7d
What it does
Send a file to a user or agent as a share link with expiry, max opens, approval, revoke and logs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http handoff-send-files-to-users-agents-mcp https://hand-off.space/mcp
# 2 — ask your agent for something these tools do
# share_file, signup, save_file and 11 more
Handoff: Send Files to Users & Agents costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
JUAll 2 servers
jueluddinsf2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http handoff-send-files-to-users-agents-mcp https://hand-off.space/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take Authorization header (API key from signup. Send Authorization: Bearer and the hf_ key, or the bare key. Not required to connect or list tools.) if you want to set it.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | File name with an extension. No slashes or control characters. |
| content_text | string | no | UTF-8 text. Pass exactly one of content_text or content_base64. |
| content_base64 | string | no | Standard or url-safe base64. A data:*;base64, prefix is stripped. Example: aGk= |
| mime | string | no | MIME type. Inferred from the file name when omitted. |
| expires_in_hours | number | no | Hours until the link expires. Default 168 (7 days). |
| max_opens | integer | no | Successful downloads allowed. Omit for no limit. |
| audience | string | no | Default anyone_with_link. |
| audience_value | string | no | Required when audience is agent. |
| requires_approval | boolean | no | Default false. When true, downloads wait until the owner approves. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
| ref | string | no | Optional attribution label. Lowercase letters, digits, dot, underscore, or hyphen. At most 64 characters. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_id | string | no | Optional label, unique across Handoff. Letters, numbers, underscore, and hyphen. |
| ref | string | no | Optional attribution label. Lowercase letters, digits, dot, underscore, or hyphen. At most 64 characters. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | File name with an extension. No slashes or control characters. |
| mime | string | no | MIME type. Inferred from the file name when omitted. |
| content_text | string | no | UTF-8 text. Pass exactly one of content_text or content_base64. |
| content_base64 | string | no | Standard or url-safe base64. A data:*;base64, prefix is stripped. Example: aGk= |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | File id returned by save_file or list_files. |
| audience_value | string | no | Required for agent: the recipient's registered agent_id. Example: their-agent |
| expires_in_hours | number | no | Hours until the link expires. Default 168 (7 days) when omitted. |
| max_opens | integer | no | Successful downloads allowed. The next one is refused. |
| requires_approval | boolean | no | When true, downloads wait until the owner approves the grant. |
| audience | string | yes | anyone_with_link: whoever has the saved url. agent: only the registered agent_id in audience_value. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grant_id | string | yes | grant_id returned when the share was created. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
Approve an owned grant that was created with requires_approval. Opens stay blocked until this succeeds. Requires your API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grant_id | string | yes | grant_id returned when the share was created. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
Deny an owned grant. A denied grant stays blocked. Requires your API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grant_id | string | yes | grant_id of the share to deny. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
Permanently revoke an owned share. Later downloads fail. This cannot be undone and does not delete the file. Requires your API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grant_id | string | yes | grant_id of the share to revoke. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grant_id | string | yes | grant_id of the share to audit. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url_or_token | string | yes | Share url returned by create_share_link, or the 64-character token. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
Delete a file you own. The bytes are removed and existing share links stop working. Requires your API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | yes | File id returned by save_file, list_files, or share_file. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| file_id | string | no | Optional file id. Omit to list every grant on this account. |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| grant_id | string | yes | — |
| expires_in_hours | number | yes | — |
| api_key | string | no | Secret API key from signup. Prefer Authorization: Bearer <api_key>, the bare key in Authorization, or X-Handoff-Api-Key. Pass this only when you cannot set headers. Do not write it into a file you sha |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Handoff: Send Files to Users & Agents or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 90 / 100
Release 1.0.1 · scanned 30 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score90
Findings0 threat · 5 capability
Capabilityhigh
Coveragemanifest
Verificationnot in this report
Surface digest73d48289b3f41b8100b6eea4284f89eeebfa3ab11043659a1e5c59a129b1889b
Score vectorthreat 100 → client 90
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| share_file | untrusted-inputexternal-sink | untrusted-input: keyword "download"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| signup | state-write | state-write: declares readOnlyHint: false |
| save_file | file-writestate-write | file-write: keyword "save_file" in tool name; state-write: declares readOnlyHint: false |
| list_files | sensitive-source | sensitive-source: keyword "list_files" |
| create_share_link | untrusted-inputstate-write | untrusted-input: keyword "fetch"; state-write: declares readOnlyHint: false |
| get_share_status | no tags | |
| approve_share | state-write | state-write: declares readOnlyHint: false |
| deny_share | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| revoke_share | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| get_access_log | no tags | |
| fetch_shared_file | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
| delete_file | file-writestate-write | file-write: keyword "delete_file" in tool name; state-write: declares readOnlyHint: false, destructiveHint: true |
| list_shares | no tags | |
| update_share | state-write | state-write: declares readOnlyHint: false |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
create_share_link → list_files → share_file
A cross-tool exfiltration chain exists: create_share_link → list_files → share_file.
Supply chain and provenance
Integrityfirst-seen
Surface digest73d48289b3f41b81
Scanned2026-10-30
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Handoff: Send Files to Users & Agents can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.