A TypeScript implementation of a simple MCP server that exposes datetime information to agentic systems and chat REPLs
Faxforagents is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Send and receive faxes from an AI agent: exact quotes, human approvals, delivery evidence, sandbox.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user faxforagents-mcp '--' npx -y faxforagents-mcp
# 2 — ask your agent for something these tools do
# get_guide, get_fax_capabilities, prepare_fax and 13 more
Remote: no sign-in · Package: optional API key.
Faxforagents costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one can run either way — at an address its publisher runs, or as a process under your own user, with your files and your network — and this marketplace is in the path of neither.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user faxforagents-mcp '--' npx -y faxforagents-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Its publisher also runs it at https://mcp.faxforagents.com/mcp/: nothing to start on your machine, and this marketplace is not in the path.
claude mcp add --scope user --transport http faxforagents-mcp https://mcp.faxforagents.com/mcp/Nothing is required, but it can take FAXFORAGENTS_API_KEY (Your Fax for Agents API key (ffa_test_... for the sandbox, ffa_live_... for the carrier). Created at https://app.faxforagents.com. The server starts without it and every tool then explains how to get one.) if you want to set it. Its publisher says some of its tools need it, and the rest work without.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
16 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
The manual for Fax for Agents: how it works, the send flow, fax states, error codes,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| section | yes | — |
The account-level view behind your key: limits, routes, formats, prices and the key's scopes. Facts
No parameter schema on file.
Create a document to fax from text, Markdown or HTML, or register a completed REST upload
| Parameter | Type | Required | Notes |
|---|---|---|---|
| text | yes | — | |
| markdown | yes | — | |
| html | yes | — | |
| upload_id | yes | — | |
| filename | yes | — |
Fetch a prepared document by id, the ids prepare_fax returns: page count, sha256, validation warnings
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document_id | string | yes | — |
Exact price for one document to one E.164 destination; the cover sheet (to_name, from_name, subject,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| document_id | string | yes | — |
| to | string | yes | — |
| cover | object | no | — |
Queue a quoted fax. A quote with authorization_required=false sends as is; otherwise pass the approval_id of an approved request bound to this quote (request_human_review), or send under a delegated policy that allows it. Repeat with the same idempotency_key to get the same fax back. The answer is…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | — |
| approval_id | yes | — | |
| idempotency_key | yes | — | |
| client_reference | yes | — |
The state of one fax and its attempts: queued, active, delivered, partial, failed or unknown. Once the fax is delivered or partial this is the one place for the carrier's delivery evidence (remote station id, pages, timestamps, provider reference) on fax.evidence and on each attempt. The evidence…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fax_id | string | yes | — |
Sent faxes of your organization, newest first, optionally by state; pages continue with cursor.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| state | yes | — | |
| limit | integer | no | — |
| cursor | yes | — |
Available and held wallet balance of this key's environment, in USD micro-units. Read-only.
No parameter schema on file.
Cancel a fax while it is queued; best effort once it is sending. Never a recall of pages already sent.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| fax_id | string | yes | — |
With quote_id: ask a person to approve that quoted send, as a pending approval request bound to the quote (document sha256, destination, sender, amount, expiry) that mails the organization. Without quote_id: ask a person for help when you are stuck or a received fax asks for something, as a help…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| message | string | yes | — |
| quote_id | yes | — | |
| fax_id | yes | — |
The state of one request made with request_human_review. For an approval request: pending, approved,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| review_request_id | string | yes | — |
Received faxes, newest first, metadata only (sender header, pages, status). Scope: inbox:read.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | — |
| cursor | yes | — |
One received fax: its metadata, document reference and, when an extraction exists, its text. The
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_id | string | yes | — |
Read a received fax (inbox_item_id) or a document (document_id) with OCR and, with a schema (a JSON
| Parameter | Type | Required | Notes |
|---|---|---|---|
| inbox_item_id | yes | — | |
| document_id | yes | — | |
| schema | object | no | — |
| strong_model_if_below | number | no | — |
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Faxforagents or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (15 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_guide | no tags | |
| get_fax_capabilities | no tags | |
| prepare_fax | state-write | state-write: declares readOnlyHint: false |
| get_fax_document | no tags | |
| quote_fax | state-write | state-write: declares readOnlyHint: false |
| send_approved_fax | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_fax_status | no tags | |
| list_faxes | no tags | |
| get_fax_balance | no tags | |
| cancel_fax | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| request_human_review | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| get_review_status | no tags | |
| list_inbox | no tags | |
| read_inbound_fax | no tags | |
| extract_fax_data | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.4.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
No release note was published with this version.
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Faxforagents can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.