# com.83blue.upload/transfer (remote · upload.83blue.com)

Free no-signup file transfer between AI agents. Share files or whole conversation handoffs by url.

- Trust score: 58/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-08

## Components

- remote · `upload.83blue.com`: 58/100 (this document), [markdown](https://verifymcp.io/servers/com-83blue-upload-transfer/upload.md), [page](https://verifymcp.io/servers/com-83blue-upload-transfer/upload)

## Channel facts

- Endpoint: `https://upload.83blue.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-08.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 883 tokens (~220/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http com-83blue-upload-transfer https://upload.83blue.com/mcp
```

### Codex

```toml
[mcp_servers.com-83blue-upload-transfer]
url = "https://upload.83blue.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-83blue-upload-transfer": {
      "type": "remote",
      "url": "https://upload.83blue.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-83blue-upload-transfer --url https://upload.83blue.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-83blue-upload-transfer:
    url: "https://upload.83blue.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-83blue-upload-transfer": {
      "type": "http",
      "url": "https://upload.83blue.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-08 (score 58)

First indexed and scored.

## MCP tools (4)

### `share_text` (~143 tokens)

Share text with another agent or person

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.

Input parameters:

- `content` (string, required): The text to share
- `expires_days` (integer): Days until the file is deleted (1-180, default 30)
- `filename` (string): File name for the download, e.g. instructions.md
- `password` (string): Optional custom password (8-64 chars); a strong one is generated when omitted

### `share_file` (~176 tokens)

Share one or more files with another agent

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 1 TB): https://upload.83blue.com/docs

Input parameters:

- `bundle_name` (string): Zip name used when more than one file is sent
- `expires_days` (integer): Days until the file is deleted (1-180, default 30)
- `files` (array, required)
- `password` (string): Optional custom password (8-64 chars); a strong one is generated when omitted

### `share_conversation` (~226 tokens)

Hand a whole conversation to another model

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 to the next agent: "Fetch this url to pick up where I left off."

Input parameters:

- `expires_days` (integer): Days until the file is deleted (1-180, default 30)
- `files` (array): Optional files the next agent needs alongside the transcript
- `password` (string): Optional custom password (8-64 chars); a strong one is generated when omitted
- `title` (string): Short name for the bundle, e.g. "auth refactor handoff"
- `transcript` (string, required): Markdown briefing for the next agent: context, instructions, conversation summary, task state. Becomes HANDOFF.md at the bundle root.

### `receive_file` (~178 tokens)

Receive a file another agent shared

Use this when you have been given an 83blue transfer 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.

Input parameters:

- `max_inline_bytes` (integer): Inline text content up to this many bytes (max 1000000)
- `password` (string): Needed for share urls and bare tokens; not needed for capability urls
- `url_or_token` (string, required): Capability url (https://upload.83blue.com/f/TOKEN/KEY), share url (https://upload.83blue.com/d/TOKEN), or the bare token

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-83blue-upload-transfer/upload#diagnostics

## Score history

- 2026-08-08: 58

## Links

- Remote endpoint: https://upload.83blue.com/mcp
- Website: https://upload.83blue.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-83blue-upload-transfer/upload.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-83blue-upload-transfer/upload.json
- HTML version of this page: https://verifymcp.io/servers/com-83blue-upload-transfer/upload