Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.83blue.upload/transfer

REMOTE · UPLOAD.83BLUE.COM · SCANNED AUG 8

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

58 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security51
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · upload.83blue.com

# add to Claude Code
claude mcp add --transport http com-83blue-upload-transfer https://upload.83blue.com/mcp
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-83blue-upload-transfer --url https://upload.83blue.com/mcp --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-83blue-upload-transfer:
    url: "https://upload.83blue.com/mcp"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 8 Aug 26 58

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 8 Aug 2026 · Probed https://upload.83blue.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=upload.83blue.com CN=YR1,O=Let's Encrypt,C=US 9 Jul 2026 7 Oct 2026 RSA 2048 SHA256-RSA 561d1a5e982dc1208a16eb7fdefe79f4f2c
SANs: upload.83blue.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f
DNSSEC insecure

Validation of upload.83blue.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
83blue.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://upload.83blue.com/mcp Verified 200
http (plaintext) http://upload.83blue.com/mcp Inconclusive 405
MCP tools · 4 exposed · ~723 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
receive_file ~178

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.

NameTypeReqDescription
max_inline_bytesintegerInline text content up to this many bytes (max 1000000)
passwordstringNeeded for share urls and bare tokens; not needed for capability urls
url_or_tokenstringyesCapability url (https://upload.83blue.com/f/TOKEN/KEY), share url (https://upload.83blue.com/d/TOKEN), or the bare token

No output schema declared.

No examples provided.

share_conversation ~226

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."

NameTypeReqDescription
expires_daysintegerDays until the file is deleted (1-180, default 30)
filesarrayOptional files the next agent needs alongside the transcript
passwordstringOptional custom password (8-64 chars); a strong one is generated when omitted
titlestringShort name for the bundle, e.g. "auth refactor handoff"
transcriptstringyesMarkdown briefing for the next agent: context, instructions, conversation summary, task state. Becomes HANDOFF.md at the bundle root.

No output schema declared.

No examples provided.

share_file ~176

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

NameTypeReqDescription
bundle_namestringZip name used when more than one file is sent
expires_daysintegerDays until the file is deleted (1-180, default 30)
filesarrayyes
passwordstringOptional custom password (8-64 chars); a strong one is generated when omitted

No output schema declared.

No examples provided.

share_text ~143

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.

NameTypeReqDescription
contentstringyesThe text to share
expires_daysintegerDays until the file is deleted (1-180, default 30)
filenamestringFile name for the download, e.g. instructions.md
passwordstringOptional custom password (8-64 chars); a strong one is generated when omitted

No output schema declared.

No examples provided.