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

FetchPan

https://fetchpan.com

Registry code: 0a7e7a73b0bcb9fa

api record

FetchPan opens download links from file hosts (Rapidgator, Katfile, ...) and Chinese cloud

drives (Baidu Netdisk, Quark, PikPak, ...) and returns a direct download URL.

endpoint
https://fetchpan.com/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 FetchPan live?
Yes — it answered the hub's last check (checked 10h ago). It answered 100% of checks over the last 30 days.
Is FetchPan free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does FetchPan have?
9 tools: check_link, start_download, get_job, get_download_link, download, create_payment_link, list_packages, list_supported_sites, ….
Is FetchPan 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 100%· all time 100%

latency
857ms

last good check

priced tools
0

of 9 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 9 tools
2 open1 auth-required 6 never probed 3 of 9 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.

  • list_packages open 10h ago

    Traffic packs that can be bought (code, size in bytes, price in USDT).

    mcp-tool

    {
      "type": "object",
      "title": "list_packagesArguments",
      "properties": {}
    }
    arguments 5 lines
  • list_supported_sites open 10h ago

    List the sites FetchPan can download from, with live status (working, slow, down). `main_sites` are the big ones (Baidu, Quark, Rapidgator ...). `file_hosts` are the other file hosts. `free` tells whether a free download is possible there or only a paid one.

    mcp-tool

    {
      "type": "object",
      "title": "list_supported_sitesArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_account auth-required 10h ago

    The account behind the token: email, traffic balance in bytes, free files per day, and the last downloads.

    mcp-tool

    {
      "type": "object",
      "title": "get_accountArguments",
      "properties": {}
    }
    arguments 5 lines
  • check_link unknown never probed

    Is this link from a site FetchPan supports, and is that site working right now? Does not use any quota. Call it before `download` when you are not sure.

    mcp-tool

    {
      "type": "object",
      "title": "check_linkArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url",
          "description": "The link the user wants to download"
        }
      }
    }
    arguments 14 lines
  • start_download unknown never probed

    Start fetching a link. Returns a job id; poll it with `get_job`. Uses no free file yet.

    mcp-tool

    {
      "type": "object",
      "title": "start_downloadArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url",
          "description": "Share or file link from a supported site"
        },
        "password": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Password",
          "default": null,
          "description": "Extraction code / password, if the share has one"
        }
      }
    }
    arguments 27 lines
  • get_job unknown never probed

    Status of a job: queued, running, succeeded or failed. When it has succeeded it also says whether a free download is possible (`free`) and what a fast one would cost in traffic bytes (`fast`).

    mcp-tool

    {
      "type": "object",
      "title": "get_jobArguments",
      "required": [
        "job_id"
      ],
      "properties": {
        "job_id": {
          "type": "string",
          "title": "Job Id",
          "description": "Job id from start_download or download"
        }
      }
    }
    arguments 14 lines
  • get_download_link unknown never probed

    Get the download URL of a succeeded job. A free link uses one of the account's free files for the day; a fast link uses traffic from the account balance. Asking again for the same job and tier returns the same link.

    mcp-tool

    {
      "type": "object",
      "title": "get_download_linkArguments",
      "required": [
        "job_id"
      ],
      "properties": {
        "tier": {
          "type": "string",
          "title": "Tier",
          "default": "free",
          "description": "\"free\" (limited per day and speed) or \"fast\" (uses traffic balance)"
        },
        "job_id": {
          "type": "string",
          "title": "Job Id",
          "description": "A succeeded job"
        }
      }
    }
    arguments 20 lines
  • download unknown never probed

    Fetch a link and return a download URL, in one call. Waits up to `wait_seconds` for the file to be ready. If it is not ready yet, the result has status "running" and a `job_id`: call `get_job`, then `get_download_link`.

    mcp-tool

    {
      "type": "object",
      "title": "downloadArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url",
          "description": "Share or file link from a supported site"
        },
        "tier": {
          "type": "string",
          "title": "Tier",
          "default": "free",
          "description": "\"free\" or \"fast\""
        },
        "password": {
          "anyOf": [
            {
              "type": "string"
            },
            {
              "type": "null"
            }
          ],
          "title": "Password",
          "default": null,
          "description": "Extraction code / password, if any"
        },
        "wait_seconds": {
          "type": "integer",
          "title": "Wait Seconds",
          "default": 45,
          "maximum": 90,
          "minimum": 0,
          "description": "How long to wait for the file to be ready"
        }
      }
    }
    arguments 41 lines
  • create_payment_link unknown never probed

    Create a payment page for a traffic pack and return its URL. Give the URL to the user: only a person can pay it. Nothing is charged by calling this.

    mcp-tool

    {
      "type": "object",
      "title": "create_payment_linkArguments",
      "required": [
        "package_code"
      ],
      "properties": {
        "package_code": {
          "type": "string",
          "title": "Package Code",
          "description": "A code from list_packages"
        }
      }
    }
    arguments 14 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 0a7e7a73b0bcb9fa.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0a7e7a73b0bcb9fa/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/0a7e7a73b0bcb9fa/badge.svg)](https://brick.blue/agent/0a7e7a73b0bcb9fa?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.