faxdrop-mcp
Related Servers
Alternatives to faxdrop-mcp
- AlicenseAqualityBmaintenanceMercury Banking MCP server with full Invoicing API support. Read accounts/transactions and create/manage recurring invoices via Model Context Protocol.39246 npm4MIT
Related Servers

faxforagents-mcpofficial
AlicenseAqualityBmaintenanceEnables AI agents to prepare, preview, quote, and send approved faxes, track delivery and evidence, read inbound faxes, extract data, and request human approvals through a fax API.171,891 npmMIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to send free and paid faxes to US and Canada numbers, check fax status, and purchase prepaid credits, all without leaving the chat.MIT

ictfax-mcpofficial
AlicenseAqualityBmaintenanceEnables AI assistants to list and track fax transmissions, and, when write access is enabled, upload documents and send faxes through ICTFax.246 npm19MIT- AlicenseNot gradedqualityBmaintenanceEnables an AI assistant to prepare and send a fax by returning a link where the user previews the document, pays per fax in the browser, and attaches any needed file, with tools for checking fax delivery status and listing supported formats. Requires no account, API key, or subscription, and nothing is sent or charged until the person pays.MIT
- AlicenseNot gradedqualityDmaintenanceSend, receive, and verify faxes from AI assistants and agents via the Model Context Protocol.59 npmMIT

SigPen MCP serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI assistants to draft, fill in, upload, and prepare documents for e-signature, while requiring explicit user approval before anything is sent.MIT
TDQS
Scored across 3 tools
The three tools target clearly distinct actions: sending (faxdrop_send_fax), checking outcome (faxdrop_get_fax_status), and pre-approving a recipient (faxdrop_pair_number). Descriptions explicitly cross-reference each other and warn when *not* to use a tool, leaving no realistic misselection path.
All names use the same faxdrop_<verb>_<object> snake_case pattern (send_fax, get_fax_status, pair_number). No mixed conventions or vague verbs.
Three tools is exactly the surface needed for a narrow fax-sending domain: send, poll, and whitelist. Each earns its place and there is no padding.
Core lifecycle (send → poll to terminal state) plus recipient pre-approval is covered. Minor gaps exist in adjacent operations such as cancelling a queued fax, listing sent history, or checking account balance, but agents can work around these.