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

faxer

https://faxer.me

Registry code: a75e6f3c95fca23d

api record

faxer.me sends real faxes to any fax number, pay-per-fax (no account or subscription).

Typical flow (human-in-the-loop payment):

endpoint
https://faxer.me/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 faxer live?
Yes — it answered the hub's last check (checked 41m ago). It answered 100% of checks over the last 30 days.
Is faxer free to use?
Yes — the hub reached it with no key and no payment.
What tools does faxer have?
4 tools: create_fax_payment, get_fax_quote, get_fax_status, send_fax.
Is faxer 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
441ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 423 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get a fax price quote
  • create a fax payment link
  • send a fax
  • check fax delivery status
takes → gives
documents, text → data, payments
tools
2 reads1 moves money1 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 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.

  • create_fax_payment moves money unknown never probed

    Create a Stripe Checkout payment link for a fax. Returns payment_url — give this link to the human so they can pay in their browser (agents never handle card details) — and payment_id, which you pass to send_fax after the human has paid. The price is computed server-side from the document or text. The Checkout link expires (see expires_at, ~24h); create a fresh one if the human delays.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Recipient fax number in international format, e.g. +15551234567."
        },
        "pages": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Page count, if pricing without the document. send_fax re-verifies against the real content."
        },
        "cover_text": {
          "type": "string",
          "maxLength": 50000,
          "description": "Plain text to fax instead of a document."
        },
        "document_url": {
          "type": "string",
          "format": "uri",
          "description": "Public http(s) URL of the PDF to fax (same one you will pass to send_fax)."
        }
      }
    }
    arguments 29 lines
  • get_fax_quote reads unknown 41m ago

    Get the exact price to send a real fax to any US, Canadian, or international fax number via faxer.me. Call this first whenever a user wants to send, transmit, or fax a document or message. Provide document_url (a publicly downloadable PDF), cover_text (plain text that will be rendered onto fax pages), or pages (an estimated page count). Pricing is pay-per-fax ($1.00 first page + $0.25/page, returned in USD cents); no account or API key needed.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "pages": {
          "type": "integer",
          "maximum": 200,
          "minimum": 1,
          "description": "Estimated page count, if you only need a rough quote."
        },
        "cover_text": {
          "type": "string",
          "maxLength": 50000,
          "description": "Plain text to fax instead of a document (rendered as PDF pages, ~3000 chars/page)."
        },
        "document_url": {
          "type": "string",
          "format": "uri",
          "description": "Public http(s) URL of the PDF to fax. The server downloads it and counts real pages."
        }
      }
    }
    arguments 22 lines
  • get_fax_status reads unknown 41m ago

    Check the delivery status of a fax sent with send_fax. Status 'success' means the receiving fax machine confirmed the transmission; 'inprogress'/'queued' mean it is still sending; 'failure' means it could not be delivered. Delivery typically takes 1-5 minutes; poll roughly every 30 seconds.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "fax_id"
      ],
      "properties": {
        "fax_id": {
          "type": "string",
          "description": "The fax_id returned by send_fax."
        }
      }
    }
    arguments 13 lines
  • send_fax sends messages unknown never probed

    Transmit a fax. Two ways to pay: (1) human-in-the-loop — pass the payment_id from create_fax_payment after the human has paid the Stripe Checkout link; (2) autonomous machine payment (x402/MPP) — call WITHOUT payment_id and the server replies with a payment challenge (JSON-RPC error -32042) for USDC-on-Tempo or a Stripe Shared Payment Token; pay it and retry with the credential in _meta['org.paymentauth/credential']. Either way the server verifies the payment covers the server-computed price of the actual content before sending via a real fax carrier. One fax per payment; a Checkout payment is only charged once the fax is delivered (the hold is released if it fails), and Stripe machine payments are refunded automatically if the fax fails to send or deliver (on-chain payments are refunded manually).

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Recipient fax number in international format, e.g. +15551234567."
        },
        "cover_text": {
          "type": "string",
          "maxLength": 50000,
          "description": "Plain text to fax instead of a document."
        },
        "payment_id": {
          "type": "string",
          "description": "The payment_id from create_fax_payment (Stripe Checkout Session id). Omit to pay autonomously via an x402/MPP machine-payment challenge instead."
        },
        "document_url": {
          "type": "string",
          "format": "uri",
          "description": "Public http(s) URL of the PDF to fax."
        },
        "cover_subject": {
          "type": "string",
          "maxLength": 200,
          "description": "Optional heading for a cover_text fax."
        }
      }
    }
    arguments 32 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 a75e6f3c95fca23d.

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