org.filetourl/mcp
REMOTE · FILETOURL.ORG · SCANNED SEP 24
Upload a file and get a public shareable URL via API or MCP.
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 Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 608 tokens (~86/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "upload_chunk" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the org.filetourl/mcp server?
org.filetourl/mcp is a hosted endpoint at https://filetourl.org/api/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 · filetourl.org
claude mcp add --transport http org-filetourl-mcp 'https://filetourl.org/api/mcp'
{
"mcpServers": {
"org-filetourl-mcp": {
"url": "https://filetourl.org/api/mcp"
}
}
} {
"servers": {
"org-filetourl-mcp": {
"type": "http",
"url": "https://filetourl.org/api/mcp"
}
}
} [mcp_servers.org-filetourl-mcp] url = "https://filetourl.org/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"org-filetourl-mcp": {
"type": "remote",
"url": "https://filetourl.org/api/mcp",
"enabled": true
}
}
} openclaw mcp add org-filetourl-mcp --url 'https://filetourl.org/api/mcp' --transport streamable-http
mcp_servers:
org-filetourl-mcp:
url: "https://filetourl.org/api/mcp" {
"McpServers": {
"org-filetourl-mcp": {
"Transport": "http",
"Url": "https://filetourl.org/api/mcp"
}
}
} assistant mcp add org-filetourl-mcp -t streamable-http -u 'https://filetourl.org/api/mcp'
{
"mcpServers": {
"org-filetourl-mcp": {
"type": "http",
"url": "https://filetourl.org/api/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.
- 21 Sept 26 +1
- Stability: 0.97 → pass security
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −2
- Stability: pass → 0.87 functional
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 22 Aug 26 0
- TLS certificate: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.90 ▲ functional
- 18 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 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
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 24 Sept 2026 · Probed https://filetourl.org/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=filetourl.org | CN=WE1,O=Google Trust Services,C=US | 28 Jul 2026 | 26 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 6fc11838abf244a13a6711b8bbca6e0 |
| SANs: filetourl.org | ||||||
| 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 filetourl.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| filetourl.org. | 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; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://filetourl.org/api/mcp | Verified | 200 | |
| http (plaintext) | http://filetourl.org/api/mcp | HTTPS enforced | 301 | https://filetourl.org/api/mcp |
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 →
confirm_upload ~60
Optional. Confirm that the PUT to a create_upload_url upload_url finished, and get the final size and link back. The link also activates without this call, this just verifies it.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The file id returned by create_upload_url. |
No output schema declared.
No examples provided.
create_upload_url ~170
Preferred way to host a file. Reserves a link and returns a short-lived upload_url on filetourl.org itself, safe for AI agent sandboxes that only allow egress to trusted domains, since the upload never has to leave filetourl.org. Send the raw file bytes yourself with a single HTTP PUT to that URL (do not read the file into this conversation, and do not base64-encode it). The public_url returned works as soon as the PUT succeeds. Needs a FileToUrl Developer API key.
| Name | Type | Req | Description |
|---|---|---|---|
| content_type | string | – | Optional MIME type of the file. Send the same value as the PUT's Content-Type header. Guessed from file_name when omitted. |
| file_name | string | yes | Original file name (used for the stored filename and content-type hints). |
No output schema declared.
No examples provided.
finish_upload ~54
Complete a chunked upload after all chunks have been sent via upload_chunk. Assembles the file, uploads it, and returns the shareable URL.
| Name | Type | Req | Description |
|---|---|---|---|
| upload_id | string | yes | The upload_id returned by start_upload. |
No output schema declared.
No examples provided.
get_file_status ~64
Look up whether a link created earlier is still active. Reports 'pending' for a reserved upload whose bytes have not arrived yet, and 'expired' once its upload window has passed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The file id returned by upload_file or create_upload_url. |
No output schema declared.
No examples provided.
start_upload ~60
Begin a chunked upload for larger files. Returns an upload_id and recommended chunk size. Use this instead of upload_file for files over ~2MB.
| Name | Type | Req | Description |
|---|---|---|---|
| file_name | string | yes | Original file name (used for the stored filename and content-type hints). |
No output schema declared.
No examples provided.
upload_chunk ~106
Send one chunk of a file started with start_upload. Call repeatedly with increasing chunk_index (starting at 0) until the whole file is sent, then call finish_upload.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk_content | string | yes | This chunk's bytes, base64-encoded. Recommended ~1MB raw per chunk. |
| chunk_index | integer | yes | Zero-based index of this chunk. Chunks are reassembled in ascending order. |
| upload_id | string | yes | The upload_id returned by start_upload. |
No output schema declared.
No examples provided.
upload_file ~94
Host a small file by sending its bytes inline as base64. Prefer create_upload_url instead: inline base64 is slow and costly above roughly 100KB. For a user's own files only. Needs a FileToUrl Developer API key.
| Name | Type | Req | Description |
|---|---|---|---|
| file_content | string | yes | The file's contents, base64-encoded. |
| file_name | string | yes | Original file name (used for the stored filename and content-type hints). |
No output schema declared.
No examples provided.
What is the org.filetourl/mcp server?
org.filetourl/mcp is listed in the public MCP registry as org.filetourl/mcp. Upload a file and get a public shareable URL via API or MCP. This page covers its hosted endpoint (https://filetourl.org/api/mcp).
Is the org.filetourl/mcp server safe to use?
org.filetourl/mcp scores 79 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 org.filetourl/mcp server expose?
org.filetourl/mcp exposes 7 tools: create_upload_url, confirm_upload, upload_file, get_file_status, start_upload, and 2 more. Their descriptions and schemas cost roughly 608 tokens of context every time the server is loaded.
Does the org.filetourl/mcp server require authentication?
No. We connected to org.filetourl/mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the org.filetourl/mcp server still maintained?
org.filetourl/mcp is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.