_ registry / mcp streamable-http · checked 8m ago

SendThisFax

https://www.sendthisfax.com

Registry code: 1c5426f828f44c21

api record

Send real faxes to institutions (EU-focused). There is no MCP upload tool: the PDF goes up as an HTTP multipart POST to https://www.sendthisfax.com/api/upload (see the send_fax tool description), so you need the file itself and an HTTP client outside MCP. If your environment cannot make that upload, tell the user instead of retrying. Never invent a fax_public_id; use the one the upload returns. Flow: 1) upload the PDF, 2) call send_fax, 3) have the user pay the returned checkout_url, 4) poll get_fax_status until delivered or failed. Failed faxes are auto-refunded. With a prepaid API key on…

endpoint
https://www.sendthisfax.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 SendThisFax live?
Yes — it answered the hub's last check (checked 8m ago). It answered 100% of checks over the last 30 days.
Is SendThisFax free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does SendThisFax have?
4 tools: get_price, get_fax_status, send_fax, check_balance.
Is SendThisFax 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
99.6%

90 days 99.5%· all time 99.5%

latency
556ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 399 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • send a fax to an institution
  • get a fax price quote
  • check fax delivery status
  • check prepaid fax balance
takes → gives
documents, data → data
tools
3 reads1 sends messages
_ 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 4 tools
1 auth-required 3 never probed 1 of 4 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.

  • check_balance reads auth-required 14h ago

    Get the prepaid credit balance of the API key used to authenticate this MCP connection. Requires a bearer API key (stf_live_...). Buy or top up credits at https://www.sendthisfax.com/en/credits — credits never expire and failed faxes are re-credited automatically.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_price reads unknown 14h ago

    Get the price quote in euro cents for sending a fax. Pricing: 5.00 EUR for up to 5 pages, plus 0.50 EUR per extra page, plus VAT based on the payer's billing country (0% VAT outside the EU).

    mcp-tool

    {
      "type": "object",
      "required": [
        "page_count",
        "billing_country"
      ],
      "properties": {
        "page_count": {
          "type": "integer",
          "maximum": 1000,
          "minimum": 1,
          "description": "Number of pages in the PDF"
        },
        "billing_country": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "ISO 3166-1 alpha-2 country code of the payer (e.g. DE, FR, NL)"
        }
      }
    }
    arguments 20 lines
  • get_fax_status reads unknown 14h ago

    Get the current status of a fax. Poll this after send_fax until a terminal state. Fax lifecycle: draft (uploaded, not submitted) -> pending (submitted, awaiting payment) -> sending -> delivered | failed. Payment lifecycle: unpaid -> verifying/open (checkout in progress) -> paid | failed | canceled | expired. A fax that fails after payment is refunded automatically to the payer.

    mcp-tool

    {
      "type": "object",
      "required": [
        "fax_id"
      ],
      "properties": {
        "fax_id": {
          "type": "string",
          "pattern": "^fax_",
          "description": "The fax public id (fax_...) returned by the upload"
        }
      }
    }
    arguments 13 lines
  • send_fax sends messages unknown never probed

    Submit an uploaded PDF for faxing. Step 1 (before this tool): upload the PDF over plain HTTP multipart, using any HTTP client you have — shell, JavaScript fetch with FormData, Python, etc.: curl -F "[email protected]" https://www.sendthisfax.com/api/upload fetch("https://www.sendthisfax.com/api/upload", {method: "POST", body: formDataWithFile}) The response contains fax_public_id and page_count. PDFs must be unencrypted, at most 50 MB and 1000 pages. Step 2: call this tool with the fax_public_id and the recipient fax number. Two modes: - With an API key (Authorization: Bearer stf_live_... on this MCP connection): the fax price is debited from the prepaid credit balance and sending starts immediately — no checkout, no browser. sender_email and billing_country are optional (they default to the key's records). Buy credits at https://www.sendthisfax.com/en/credits. - Without an API key: sender_email and billing_country are REQUIRED and the tool returns a checkout_url the USER must pay in a browser; the fax is sent automatically once paid. In both modes, poll get_fax_status until status reaches "delivered" or "failed" (failures after payment are auto-refunded). For integration testing, +19898989898 is the designated test recipient number.

    mcp-tool

    {
      "type": "object",
      "required": [
        "fax_public_id",
        "recipient_number"
      ],
      "properties": {
        "locale": {
          "enum": [
            "en",
            "de",
            "fr",
            "nl",
            "es",
            "it"
          ],
          "type": "string",
          "description": "Language for emails and the checkout page (default: en)"
        },
        "sender_email": {
          "type": "string",
          "format": "email",
          "description": "Payer email for the receipt and delivery notification. Required without an API key; defaults to the key's email otherwise."
        },
        "fax_public_id": {
          "type": "string",
          "pattern": "^fax_",
          "description": "The fax public id (fax_...) from the upload step"
        },
        "billing_country": {
          "type": "string",
          "pattern": "^[A-Za-z]{2}$",
          "description": "ISO 3166-1 alpha-2 country of the payer, determines VAT. Required without an API key; fixed by the key's first purchase otherwise."
        },
        "recipient_number": {
          "type": "string",
          "pattern": "^\\+[1-9][0-9]{6,14}$",
          "description": "Recipient fax number in E.164 format, e.g. +49301234567"
        }
      }
    }
    arguments 41 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 1c5426f828f44c21.

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

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.