_ registry / mcp streamable-http · checked 2h ago

filetourl

https://filetourl.org

Registry code: 7395a5984bac5606

api record

Upload a file and get a public shareable URL via API or MCP.

from a public catalogue that lists it, not from the operator

endpoint
https://filetourl.org/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is filetourl live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is filetourl free to use?
Not measured yet.
What tools does filetourl have?
7 tools: start_upload, confirm_upload, get_file_status, create_upload_url, upload_file, upload_chunk, finish_upload.
Is filetourl safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.6%· all time 99.6%

latency
408ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 281 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • upload a file and get a public link
  • upload a large file in chunks
  • check if a file link is active
takes → gives
documents, images → web pages, data
tools
1 reads6 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
7 never probed 0 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • start_upload changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "file_name"
      ],
      "properties": {
        "file_name": {
          "type": "string",
          "description": "Original file name (used for the stored filename and content-type hints)."
        }
      }
    }
    arguments 12 lines
  • confirm_upload changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The file id returned by create_upload_url."
        }
      }
    }
    arguments 12 lines
  • get_file_status reads unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "id"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "The file id returned by upload_file or create_upload_url."
        }
      }
    }
    arguments 12 lines
  • create_upload_url changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "file_name"
      ],
      "properties": {
        "file_name": {
          "type": "string",
          "description": "Original file name (used for the stored filename and content-type hints)."
        },
        "content_type": {
          "type": "string",
          "description": "Optional MIME type of the file. Send the same value as the PUT's Content-Type header. Guessed from file_name when omitted."
        }
      }
    }
    arguments 16 lines
  • upload_file changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "file_content",
        "file_name"
      ],
      "properties": {
        "file_name": {
          "type": "string",
          "description": "Original file name (used for the stored filename and content-type hints)."
        },
        "file_content": {
          "type": "string",
          "description": "The file's contents, base64-encoded."
        }
      }
    }
    arguments 17 lines
  • upload_chunk changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "upload_id",
        "chunk_index",
        "chunk_content"
      ],
      "properties": {
        "upload_id": {
          "type": "string",
          "description": "The upload_id returned by start_upload."
        },
        "chunk_index": {
          "type": "integer",
          "description": "Zero-based index of this chunk. Chunks are reassembled in ascending order."
        },
        "chunk_content": {
          "type": "string",
          "description": "This chunk's bytes, base64-encoded. Recommended ~1MB raw per chunk."
        }
      }
    }
    arguments 22 lines
  • finish_upload changes data unknown never probed

    Complete a chunked upload after all chunks have been sent via upload_chunk. Assembles the file, uploads it, and returns the shareable URL.

    mcp-tool

    {
      "type": "object",
      "required": [
        "upload_id"
      ],
      "properties": {
        "upload_id": {
          "type": "string",
          "description": "The upload_id returned by start_upload."
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 7395a5984bac5606.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7395a5984bac5606/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/7395a5984bac5606/badge.svg)](https://brick.blue/agent/7395a5984bac5606?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.