File Relay
REMOTE · CODE.EASYLLMS.COM
Temporary file relay for AI agents: upload a generated file, get an expiring download link.
Available components
Last scanned (20 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Documents and Files
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 Security46
- 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_file). 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 668 tokens (~133/item across 5 items; 5 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 Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 6 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
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.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 25 Oct 26 60
First indexed and scored.
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 4 Nov 2026 · Probed https://code.easyllms.com/relay/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=easyllms.com | CN=WE1,O=Google Trust Services,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 7dda1e1e9f04c4a10ee47c60988ec8d0 |
| SANs: easyllms.com, *.easyllms.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of code.easyllms.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| easyllms.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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://code.easyllms.com/relay/mcp | Verified | 200 | |
| http (plaintext) | http://code.easyllms.com/relay/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 →
create_upload_link Create upload link ~193
Relay a file of any size up to 100 MB. Save the file to local disk first, call this with its path, then run the returned curl command in your shell to upload it. The download link works as soon as the upload finishes. Requires outbound network access to code.easyllms.com; if curl is blocked, ask the user to allow that domain in their sandbox network settings (on claude.ai: Settings > Capabilities > Code execution).
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | Optional MIME type; guessed from the extension otherwise. |
| filename | string | – | Optional name shown to the downloader; defaults to the file name in path. |
| path | string | yes | Local path of the file you saved, e.g. /tmp/report.pdf. Used to build the curl command. |
| ttl_hours | number | – | Hours until the download link expires. Default 24, maximum 168 (7 days). |
No output schema declared.
No examples provided.
delete_file Delete file ~50
Delete a relayed file before it expires. Requires the delete_token returned at upload.
| Name | Type | Req | Description |
|---|---|---|---|
| delete_token | string | yes | delete_token returned at upload. |
| id | string | yes | File id or download URL. |
No output schema declared.
No examples provided.
get_file_info Get file info ~49
Look up a relayed file by id or download URL: name, size, type, expiry and download link.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | File id or download URL returned by an upload tool. |
No output schema declared.
No examples provided.
read_file Read file ~66
Read a relayed file's content (up to 1 MB) so an agent can pick up a file someone else relayed. Text comes back as text, images as images, other files as base64.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | File id or download URL from this relay. |
No output schema declared.
No examples provided.
relay_attached_file Relay attached file ~86
ChatGPT only: relay a file from the conversation (the host passes it as a file reference) and get a temporary download link.
| Name | Type | Req | Description |
|---|---|---|---|
| file | object | yes | File reference provided by the host. |
| filename | string | – | Optional file name override. |
| ttl_hours | number | – | Hours until the download link expires. Default 24, maximum 168 (7 days). |
No output schema declared.
No examples provided.
How do I install the File Relay MCP server?
File Relay is a hosted endpoint at https://code.easyllms.com/relay/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 · code.easyllms.com
claude mcp add --transport http yjq001-file-relay 'https://code.easyllms.com/relay/mcp'
What is the File Relay MCP server?
File Relay is an MCP server listed in the public MCP registry as io.github.yjq001/file-relay. Temporary file relay for AI agents: upload a generated file, get an expiring download link. This page covers its hosted endpoint (https://code.easyllms.com/relay/mcp).
Is the File Relay MCP server safe to use?
File Relay scores 64 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 File Relay MCP server expose?
File Relay exposes 5 tools: create_upload_link, relay_attached_file, get_file_info, read_file, delete_file. Their descriptions and schemas cost roughly 444 tokens of context every time the server is loaded.
Does the File Relay MCP server require authentication?
No. We connected to File Relay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the File Relay MCP server still maintained?
File Relay is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.