Unstable preview. Pages, data and API fields can change or break without notice, so please don't rely on this for anything critical yet. See what has changed.
Agent Service Directory
Menu

io.github.faxforagents/faxforagents-mcp

MCP server · mcp.faxforagents.com · found in a public list · checked since 2026-10-31

Live, handshake completed · latest check

As JSON

Sends and receives faxes with approvals, delivery evidence and field extraction.

Our summary of what its own text says it does: automated, not reviewed by a person (placement-ai/6). What this means

Placed in Send faxes: Send and receive faxes, and look up fax line data.

https://mcp.faxforagents.com/mcp/ MCP endpoint (Streamable HTTP)

The name is the registry's label, not ours. Not reviewed by a person.

Our checks

An unpaid request daily, from eastern North America

Last 1 checks, oldest to newest; room for 29 more

1 passed, 0 failed, 29 not run.

Passed, 30 daysshort history1 of 1 run
Checks missed0in 30 days
Response, latest1051 mswhole handshake
Scheduledailyset by usage; rule below
Checked since2026-10-31under 1 day
Freshnessfreshagainst its schedule

Checked daily. Daily: 5 to 99 payers, and every new service until it has been probed 3 times.

Response times

WindowChecksTimeoutsMedian90th95th99thFastestSlowest
24 hourssince 2026-10-3110——————
7 dayssince 2026-10-3110——————
30 dayssince 2026-10-3110——————

Milliseconds, from eastern North America, timing the whole MCP handshake (initialize to the tools/list answer). Timeouts count at the 10000 ms limit. A dash means too few checks for that figure. As of . Definitions and method.

Details

Tools listed by the server

cancel_faxevaluate_fax_policyextract_fax_dataget_fax_balanceget_fax_capabilitiesget_fax_statusget_guidelist_faxeslist_inboxprepare_faxpreview_faxquote_faxread_inbound_faxrequest_human_reviewsend_approved_fax

Tools
15
This list since
2026-10-31
First listed to us
2026-10-31
List changes, 90 days
0

Names as the server reported them at our latest completed handshake (mcp-handshake/2); a listed tool is not a tested one. Definitions

Access

Our latest check
Nothing asked
Stated
not stated
Payment model
not known
Currency
not known

"Nothing asked" describes one plain request, not every operation. Statements are claims, not our measurements. Definitions

Interface it declares

Protocol
MCP 2025-06-18
Capabilities
promptsresourcestools
Transports
streamable-http

As its initialize reply stated it at our check on (mcp-handshake/2): a claim, not tested. Definitions

Calls it declares

  • get_guide section → ok message error_code details untrusted
  • get_fax_capabilities → ok message error_code details untrusted
  • prepare_fax text markdown html upload_id filename → ok message error_code details untrusted
  • preview_fax document_id* → ok message error_code details untrusted
  • quote_fax document_id* to* cover → ok message error_code details untrusted
  • send_approved_fax quote_id* approval_id idempotency_key client_reference → ok message error_code details untrusted
  • get_fax_status fax_id* → ok message error_code details untrusted
  • list_faxes state limit cursor → ok message error_code details untrusted
  • get_fax_balance → ok message error_code details untrusted
  • cancel_fax fax_id* → ok message error_code details untrusted
  • request_human_review message* quote_id fax_id → ok message error_code details untrusted
  • evaluate_fax_policy quote_id document_id to → ok message error_code details untrusted

From the tool list it returned to our check (request-shape/2). * marks a required parameter; after → the fields it says it returns. What it declares, not that a call works.

Listing

In the capability tree: Messaging and communication / Send faxes (primary). Placed by three checks by a small AI model: placed, found blind from its tasks, and verified against its own text (placement-ai/6, tree/3) on 2026-10-31. Wrong place? Tell us.

In the directory: meets our listing criteria (listing-criteria/6): ✓ says what it does; ✓ its latest check passed.

Recent probes

WhenResultTime to headers

cloudflare:MIA		 Live, handshake completed HTTP 200 1051 ms

What these figures do not show

  • A passing check means the server completed the MCP handshake with us (initialize, then tools/list, with no credentials; mcp-handshake/2) or asked for credentials first (HTTP 401). It does not show that the server's tools work or what they return. Tool names are as the server listed them.
  • Listed in the Official MCP Registry; this data comes from the Official MCP Registry. Its listing's description is not republished.
  • Limited evidence: monitored for under 1 day (less than 30).

Something wrong here?

Operate this service and want it reviewed, corrected or removed? Email hello@agentservicedirectory.com or use the opt-out page. A wrong place in the tree? Tell us.

Machine-readable: /api/v1/services/cand_1b08dce101b693e1