ohfax
Registry code: 7fc4489b2d991175
Outbound US/CA fax for agents: quote PDF, pay via MPP, get delivery receipt.
from a public catalogue that lists it, not from the operator
- endpoint
- https://app.ohfax.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 ohfax live?
- Yes — it answered the hub's last check (checked 6h ago). It answered 99% of checks over the last 30 days.
- Is ohfax free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ohfax have?
- 4 tools: get_fax_receipt, get_fax_status, quote_fax, send_fax.
- Is ohfax 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 99.3%· all time 99.3%
last good check
of 4 tools
- degraded → live
- live → degraded· timeout after 20000ms
- down → live
- topic
- communication
- used for
- send a fax to the us or canada
- get a price quote for a fax
- check fax delivery status
- get a fax delivery receipt
- takes → gives
- documents → data
- tools
- 3 reads1 sends messages
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_receipt reads unknown 24h ago
Verifiable delivery receipt for a completed fax. Available once the fax has reached a final state. Use this to prove the workflow finished.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "fax_id" ], "properties": { "fax_id": { "type": "string" } } }arguments 12 linesget_fax_status reads unknown 24h ago
Current delivery state of a fax: awaiting_payment, paid, submitted, sending, delivered, or failed. Failed faxes include a reason you can act on.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "fax_id" ], "properties": { "fax_id": { "type": "string" } } }arguments 12 linesquote_fax reads unknown 24h ago
Returns the price: $2.00 per fax by card for up to 100 pages (flat, no per-page charge); prepaid balance or MPP stablecoin: $0.02 per page. Also validates the number and PDF and returns a quote_id and payment link. Free; sends nothing. Call before send_fax.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "to" ], "properties": { "to": { "type": "string", "description": "Destination fax number. US and Canada only." }, "document_url": { "type": "string", "description": "Publicly reachable URL of a PDF." }, "document_base64": { "type": "string", "description": "Base64-encoded PDF, as an alternative to document_url." } } }arguments 21 linessend_fax sends messages unknown never probed
Returns the authorization instructions for sending a previously quoted fax. THIS ACTION COSTS MONEY AND CANNOT BE UNDONE: paying the returned link transmits a real document to a real fax machine. This tool itself does not charge you — it returns the price and a payment link, and the fax is only sent once you deliberately pay that link. Confirm the cost is acceptable before paying.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "quote_id" ], "properties": { "quote_id": { "type": "string", "description": "A quote_id from quote_fax." } } }arguments 13 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 id7fc4489b2d991175.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7fc4489b2d991175/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7fc4489b2d991175?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.