FaxOnline
Registry code: b6cfc4a6bb7c0692
Prepare a PDF fax to a US number only when the user requests it. Generate a cryptographically random 64-character lowercase hexadecimal draft_token and keep it secret. Reuse the token and identical inputs on retries. Give the user the returned Stripe checkout link to review the destination and authorize payment. Verified payment authorization automatically queues the fax; never report delivery until get_fax_status reports sent or delivered. Poll at most once every 15 seconds. Documents must be base64-encoded PDFs up to 10 MiB. There is no tool to bypass checkout or submit card details.
- endpoint
- https://faxonline.app/mcp/fax
- 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 FaxOnline live?
- Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
- Is FaxOnline free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does FaxOnline have?
- 2 tools: get_fax_status, prepare_fax.
- Is FaxOnline 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.
90 days 100%· all time 100%
last good check
of 2 tools
- unknown → live
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.
through this hub
successful
what callers paid
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
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.
get_fax_status unknown 1h ago
Check your prepared fax using its secret draft_token. Returns payment and delivery status. A processing fax has not yet been delivered. Poll no more than once every 15 seconds.
{ "type": "object", "required": [ "draft_token" ], "properties": { "draft_token": { "type": "string", "description": "The private token used in prepare_fax." } } }arguments 12 linesprepare_fax unknown never probed
Prepare one PDF fax and return its price and Stripe checkout link. This stores the document but does not send or charge. Completing checkout authorizes sending to the displayed recipient. Keep draft_token private and reuse it with identical inputs for retries.
{ "type": "object", "required": [ "draft_token", "fax_number", "email", "filename", "document_base64" ], "properties": { "email": { "type": "string", "description": "Email address for delivery notifications." }, "filename": { "type": "string", "description": "PDF filename without directory paths." }, "fax_number": { "type": "string", "description": "US destination fax number: 10 digits (5155551234), optionally prefixed with 1 or +1 (+15155551234). Common formatting such as (515) 555-1234 is accepted." }, "draft_token": { "type": "string", "description": "A secret, cryptographically random 64-character lowercase hex token. Reuse for retries and status checks." }, "document_base64": { "type": "string", "description": "Standard base64 of the PDF bytes, without a data URL prefix; maximum decoded size 10 MiB." } } }arguments 32 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's idb6cfc4a6bb7c0692.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/b6cfc4a6bb7c0692/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/b6cfc4a6bb7c0692?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.