3LT Mail & Fax
Server Details
Letters + faxes for AI assistants in one MCP service. Letters from $1.97 all-in; faxes from $0.57.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- Repository
- 3LGroupTechnology/3lt-letter-mail
- GitHub Stars
- 0
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 7 tools
The set splits into fax and letter workflows with parallel tools: create_fax_draft/approve_fax/send_fax/get_fax_status versus draft_letter/request_send/send_status. Descriptions clarify that request_send handles mailing and send_fax handles fax transmission, but the generic names send_status and request_send still overlap conceptually with get_fax_status and send_fax. An agent must learn the asymmetric mapping rather than relying on names alone.
All names are snake_case and mostly verb_noun, but the convention is inconsistent across the two workflows. Fax tools use create_fax_draft, approve_fax, send_fax, get_fax_status; letter tools use draft_letter and request_send/send_status, where send_status omits the resource and request_send names an action rather than an object. These deviations are readable but not predictable.
Seven tools is appropriate for covering two channels (fax and letter) plus approval and status checks. Each tool has a distinct role, though the set could arguably consolidate status tools if the workflows were unified. It is neither thin nor heavy.
The main lifecycles are covered: fax draft → approve → send → status, and letter draft → request_send → send_status. Minor gaps exist around cancellation, listing drafts, or editing an existing draft, but core send-and-track operations are present without obvious dead ends.
Available Tools
7 toolsapprove_faxApprove a FaxAIdempotentInspect
Approve a fax DRAFT so it can be transmitted. The content is re-screened at approval time. Only the key that created the fax can approve it. Nothing is transmitted by this call — send_fax does that.
Inputs: fax_id (required), api_key (required). Returns: object
create_fax_draftDraft a FaxAInspect
Create a fax DRAFT: validates the recipient number, counts the PDF's pages, screens its text, and returns a price quote (Phaxio per-page cost x pages + the flat $1.00 service fee). This NEVER transmits anything — call approve_fax, then send_fax.
Inputs: api_key (required), pdf_path (required), to_number (required), description. Returns: object
draft_letterDraft a LetterAInspect
Create a letter DRAFT: verifies the recipient address with PostGrid, screens content, and returns a price quote. This NEVER mails anything.
Pass EITHER html (letter body as an HTML string) OR pdf_path (path to a PDF file on the server). PDF text is extracted for screening; if extraction fails the draft is kept but flagged needs_review.
Inputs: to (required), api_key (required), from_address (required), html, +5 more. Returns: object
get_fax_statusCheck Fax StatusARead-onlyIdempotentInspect
Check a fax: lifecycle status (DRAFT/APPROVED/SENT/FAILED), page count, quote, and — once sent — the live delivery status from Phaxio.
Inputs: fax_id (required), api_key (required). Returns: object
request_sendRequest Letter SendADestructiveInspect
Request that a draft be mailed.
approval-tier keys: creates a PENDING request and returns a one-tap Allow/Deny approval_url for the human. Nothing is mailed until Allow. on_command keys: may auto-send inside guardrails (spend caps, content screening, anomaly detection); anything outside them stays PENDING.
Inputs: api_key (required), draft_id (required). Returns: object
send_faxSend a FaxADestructiveIdempotentInspect
Transmit an APPROVED fax via Phaxio. Refuses drafts that were never approved and faxes that were already sent — a fax can be transmitted exactly once.
Inputs: fax_id (required), api_key (required). Returns: object
send_statusCheck Letter Send StatusAInspect
Check a send request: status (PENDING/SENT/REJECTED/FAILED), the key's trust tier and tier decision, approval state (+approval_url while pending), and billing state (Stripe charge id when billed).
Inputs: api_key (required), request_id (required). Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Fax API and MCP server for AI agents. Fax US and Canada, pay per request with x402. No account.
Send real faxes from AI assistants. Pay per fax ($1 + $0.25/page), no account or API key.
Send real faxes worldwide from your AI assistant. Prepaid, no subscription, PDF send report.
Send real faxes from AI assistants: PDF to any fax number, delivery status, pages left.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to prepare, price, review, pay for, and send real physical letters and postcards via a hosted MCP server.-
- AlicenseNot gradedqualityBmaintenanceHosted remote MCP server that lets AI agents compose, price, send, and track real physical letters worldwide.1MIT
- AlicenseBqualityBmaintenanceOfficial mailbox.bot MCP server for AI agents. Send letters, certified mail and postcards, and give an agent its own street address + postal mailbox number. Agent receiving virtual mailboxes with a real street address are live now at $15/mo in Manhattan Beach, CA. Sandbox keys, approval controls, tracking and webhooks.55119 npm2MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that lets AI agents create reviewable physical mail drafts, validate quotes, and pay for postage via MPP or x402 protocols.2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.