com.83blue.upload/agent-cloud-tools
REMOTE · UPLOAD.83BLUE.COM · SCANNED SEP 28
Free no-signup cloud tools for AI agents: file transfer, static site hosting, memory, handoff.
Available components
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 → Why this is hard to score →
Endpoint Security51
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_site). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1727 tokens (~191/item across 9 items; 9 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.83blue.upload/agent-cloud-tools MCP server?
com.83blue.upload/agent-cloud-tools is a hosted endpoint at https://upload.83blue.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · upload.83blue.com
claude mcp add --transport http com-83blue-upload-agent-cloud-tools 'https://upload.83blue.com/mcp'
{
"mcpServers": {
"com-83blue-upload-agent-cloud-tools": {
"url": "https://upload.83blue.com/mcp"
}
}
} {
"servers": {
"com-83blue-upload-agent-cloud-tools": {
"type": "http",
"url": "https://upload.83blue.com/mcp"
}
}
} [mcp_servers.com-83blue-upload-agent-cloud-tools] url = "https://upload.83blue.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-83blue-upload-agent-cloud-tools": {
"type": "remote",
"url": "https://upload.83blue.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-83blue-upload-agent-cloud-tools --url 'https://upload.83blue.com/mcp' --transport streamable-http
mcp_servers:
com-83blue-upload-agent-cloud-tools:
url: "https://upload.83blue.com/mcp" {
"McpServers": {
"com-83blue-upload-agent-cloud-tools": {
"Transport": "http",
"Url": "https://upload.83blue.com/mcp"
}
}
} assistant mcp add com-83blue-upload-agent-cloud-tools -t streamable-http -u 'https://upload.83blue.com/mcp'
{
"mcpServers": {
"com-83blue-upload-agent-cloud-tools": {
"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.
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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
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 28 Sept 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 | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 5e42e67cfbef0b1499af2a991d661b40f89 |
| 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
delete_site Take down a hosted site ~63
Remove a site you deployed. Needs the site url/host/slug and its manage_key (returned by deploy_site).
| Name | Type | Req | Description |
|---|---|---|---|
| manage_key | string | yes | The manage_key returned when the site was deployed |
| site | string | yes | The site url, host or slug |
No output schema declared.
No examples provided.
deploy_site Publish a static website to a live public url ~346
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 website, landing page, demo, prototype or report and wants to see it live. IMPORTANT: the site is served from a subfolder, so use RELATIVE asset paths only (href="style.css", src="img/logo.png"), never root-absolute paths like "/style.css" which would break. Sites are served as pure static files (server-side code is never executed) and auto-expire after 30 days unless renewed. Each file is text or base64. Total site up to 50 MB, 300 files.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_days | integer | – | Days until the site is removed (1-30, default 30) |
| files | array | yes | The site files. Must include an index.html at the root. |
| manage_key | string | – | Pass the manage_key from a previous deploy together with the same slug to update that site in place. |
| slug | string | – | 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 | – | Optional short label for your own reference |
No output schema declared.
No examples provided.
list_sites Look up a hosted site ~58
Return the status, address, size and expiry of a site you deployed. Pass the url, host or slug.
| Name | Type | Req | Description |
|---|---|---|---|
| site | string | yes | The site url (https://.../s/name/), path (/s/name) or bare name |
No output schema declared.
No examples provided.
recall Recall something you stored earlier, or fetch any 83blue url ~130
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.
| Name | Type | Req | Description |
|---|---|---|---|
| max_inline_bytes | integer | – | Inline text content up to this many bytes |
| password | string | – | Needed for share urls; not needed for capability urls |
| url_or_token | string | yes | The 83blue url or token to recall or fetch |
No output schema declared.
No examples provided.
receive_file Receive a file another agent shared ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Capability 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.
remember Remember text, notes or JSON for a future session (durable agent memory) ~165
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The text or JSON to remember |
| expires_days | integer | – | Days until the file is deleted (1-180, default 30) |
| filename | string | – | Optional label/key for this memory, e.g. project-notes.md |
| password | string | – | Optional custom password (8-64 chars); a strong one is generated when omitted |
No output schema declared.
No examples provided.
share_conversation Hand a whole conversation to another model ~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."
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Markdown 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 Share one or more files with another agent ~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 2 TB): https://upload.83blue.com/docs
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| password | string | – | Optional custom password (8-64 chars); a strong one is generated when omitted |
No output schema declared.
No examples provided.
share_text Share text with another agent or person ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | 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 |
No output schema declared.
No examples provided.
What is the com.83blue.upload/agent-cloud-tools MCP server?
com.83blue.upload/agent-cloud-tools is an MCP server listed in the public MCP registry as com.83blue.upload/agent-cloud-tools. Free no-signup cloud tools for AI agents: file transfer, static site hosting, memory, handoff. This page covers its hosted endpoint (https://upload.83blue.com/mcp).
Is the com.83blue.upload/agent-cloud-tools MCP server safe to use?
com.83blue.upload/agent-cloud-tools scores 68 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.83blue.upload/agent-cloud-tools MCP server expose?
com.83blue.upload/agent-cloud-tools exposes 9 tools: share_text, share_file, share_conversation, receive_file, deploy_site, and 4 more. Their descriptions and schemas cost roughly 1,484 tokens of context every time the server is loaded.
Does the com.83blue.upload/agent-cloud-tools MCP server require authentication?
No. We connected to com.83blue.upload/agent-cloud-tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.83blue.upload/agent-cloud-tools MCP server still maintained?
com.83blue.upload/agent-cloud-tools is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.