MCP server for terminal commands, file operations, and process management
Nothing to run from here
Transfer 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.
93/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Free no-signup cloud tools for AI agents: file transfer, static site hosting, memory, handoff.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http transfer-mcp https://upload.83blue.com/mcp
# 2 — ask your agent for something these tools do
# share_text, share_file, share_conversation and 6 more
Transfer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
83All 1 server
83blue1 server
1 category
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 transfer-mcp https://upload.83blue.com/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 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
9 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.
Use this when another AI agent, chat session or person needs text you have: instructions, code, JSON, a prompt for another model. Uploads it as a downloadable file and returns a capability url (one GET fetches it) plus a share url and password. No account or API key needed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | The text to share |
| filename | string | no | File name for the download, e.g. instructions.md |
| expires_days | integer | no | Days until the file is deleted (1-180, default 30) |
| password | string | no | Optional custom password (8-64 chars); a strong one is generated when omitted |
Use this when another AI agent (a different machine, model or chat session) or a person needs access to one or more files. Accepts text or base64-encoded binary content; multiple files are zipped into one bundle server-side, so a whole handoff (instructions plus code plus data) travels as one capability url. For large files already on local disk, prefer the HTTP API (one curl command, up to 2 TB):
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | yes | — |
| bundle_name | string | no | Zip name used when more than one file is sent |
| expires_days | integer | no | Days until the file is deleted (1-180, default 30) |
| password | string | no | Optional custom password (8-64 chars); a strong one is generated when omitted |
Use this to hand your full working context to another AI: any provider, any model, any chat client. Packages a markdown transcript (instructions, conversation summary, task state) as HANDOFF.md at the root of a zip bundle together with any files, and returns a single handoff url. The receiving model just fetches that url: it gets a briefing, the file manifest and download commands in one go. Say t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| transcript | string | yes | Markdown briefing for the next agent: context, instructions, conversation summary, task state. Becomes HANDOFF.md at the bundle root. |
| files | array | no | Optional files the next agent needs alongside the transcript |
| title | string | no | Short name for the bundle, e.g. "auth refactor handoff" |
| expires_days | integer | no | Days until the file is deleted (1-180, default 30) |
| password | string | no | Optional custom password (8-64 chars); a strong one is generated when omitted |
Use this when you have been given an 83blue link and need the file. Accepts a capability url (https://upload.83blue.com/f/...) on its own, or a share url plus password. Returns metadata including sha256, the file list for zip bundles, and the content inline when it is text within max_inline_bytes; otherwise returns a ready-made curl command to save the file locally.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url_or_token | string | yes | Capability url (https://upload.83blue.com/f/TOKEN/KEY), share url (https://upload.83blue.com/d/TOKEN), or the bare token |
| password | string | no | Needed for share urls and bare tokens; not needed for capability urls |
| max_inline_bytes | integer | no | Inline text content up to this many bytes (max 1000000) |
Use this to put a static website you have built (HTML, CSS, JS, images, fonts) onto the public web in one call, with no signup, no account and no config. Give it the files (there must be an index.html at the root) and it returns a live https url, e.g. https://upload.83blue.com/s/brave-otter-482/, plus a manage_key you can reuse to update or delete it. Ideal when a person asks you to build them a w
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | yes | The site files. Must include an index.html at the root. |
| slug | string | no | Optional name for the site path (3-40 chars, a-z 0-9 and hyphens); it becomes /s/{name}/. A friendly one is generated when omitted. |
| title | string | no | Optional short label for your own reference |
| expires_days | integer | no | Days until the site is removed (1-30, default 30) |
| manage_key | string | no | Pass the manage_key from a previous deploy together with the same slug to update that site in place. |
Return the status, address, size and expiry of a site you deployed. Pass the url, host or slug.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | The site url (https://.../s/name/), path (/s/name) or bare name |
Remove a site you deployed. Needs the site url/host/slug and its manage_key (returned by deploy_site).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| site | string | yes | The site url, host or slug |
| manage_key | string | yes | The manage_key returned when the site was deployed |
Durable cross-session memory for AI agents: store notes, context, text or JSON now and recall it in a later session or from another machine by url. A free cloud scratchpad and shared key-value store for agents, no signup, no account, no API key. Also callable as save_memory, store_memory, save_note, stash. Returns a url; fetch it back later with recall.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| content | string | yes | The text or JSON to remember |
| filename | string | no | Optional label/key for this memory, e.g. project-notes.md |
| expires_days | integer | no | Days until the file is deleted (1-180, default 30) |
| password | string | no | Optional custom password (8-64 chars); a strong one is generated when omitted |
Fetch back durable memory, or any shared file/text, by its 83blue url or token (a capability url, or a share url plus password). Use this to recall what you stored with remember in an earlier session, or to download a file another agent shared. Also callable as get_memory, download_file, fetch_file, get_file.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url_or_token | string | yes | The 83blue url or token to recall or fetch |
| password | string | no | Needed for share urls; not needed for capability urls |
| max_inline_bytes | integer | no | Inline text content up to this many bytes |
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 Transfer 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 93 / 100
Release 1.0.0 · scanned 28 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 score93
Findings0 threat · 3 capability
Capabilitymoderate
Coveragemanifest
Verificationnot in this report
Surface digest2412350cc1169ab61507df89350fd763207646e2e4caef35f421214d903015e4
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| 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. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| share_text | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| share_file | external-sink | external-sink: keyword "curl", declares readOnlyHint: false, openWorldHint: true |
| share_conversation | untrusted-inputexternal-sink | untrusted-input: keyword "download"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| receive_file | external-sinkuntrusted-input | external-sink: keyword "curl"; untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| deploy_site | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| list_sites | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| delete_site | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| remember | untrusted-inputexternal-sink | untrusted-input: keyword "fetch"; external-sink: declares readOnlyHint: false, openWorldHint: true |
| recall | untrusted-input | untrusted-input: keyword "fetch", declares openWorldHint: true (interacts with entities outside the server) |
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.
flow-1
Untrusted input can drive an external action even though no sensitive source is exposed.
Supply chain and provenance
Integrityfirst-seen
Surface digest2412350cc1169ab6
Scanned2026-10-28
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.0.
1.0.0
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 Transfer 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.