Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Faxbeep

REMOTE · FAXBEEP.COM

Test fax numbers for AI agents. Send a test fax or scan-to-email, then read what Faxbeep received.

Available components

+3 this week 76 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Communication

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1617 tokens (~539/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 10 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://faxbeep.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=faxbeep.com CN=WE1,O=Google Trust Services,C=US 27 Oct 2026 25 Jan 2027 ECDSA 256 ECDSA-SHA256 33efde7b35c258080e109ea3cff81c5c
SANs: faxbeep.com, *.faxbeep.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of faxbeep.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
faxbeep.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options SAMEORIGIN

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://faxbeep.com/mcp Verified 200
http (plaintext) http://faxbeep.com/mcp HTTPS enforced 301 https://faxbeep.com/mcp
MCP tools · 3 exposed · ~1,186 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_test_fax ~285

Get one test fax by its slug (fax_ and 8 characters from 0-9 and a-f, for example fax_1a2b3c4d) or by the URL of its page on faxbeep.com (view_url, with or without a language prefix such as /de). The result is the fax object, the same as an item of list_test_faxes, and after it an image of page 1 when one can be read. A client can draw that image very small. In a chat that shows images, also show thumbnail_url as an image in your answer. Give view_url for the full page. A fax that is not found gives an error result: a new fax can take a while to appear, and a fax that is still processing is not found yet. A fax that was removed, by request or after 30 days, gives the error result "This fax was removed, or it is older than 30 days." Its files are deleted, so it cannot be read again. For a sample answer, use fax_example (a published sample fax) or fax_example_removed (the answer for a removed fax).

NameTypeReqDescription
faxstringyesThe slug of the fax (for example fax_1a2b3c4d), or the URL of its page on faxbeep.com (view_url).

No output schema declared.

No examples provided.

get_test_numbers ~274

Get the Faxbeep test fax numbers, the test email addresses and the limits. Call this first, before the person sends a test. Each item of "numbers" is a test fax number: "local_format" is the number to dial inside its country, "international_format" from any other country. The person sends a fax to it from a fax machine or a fax service. Each item of "email_addresses" takes an email with one PDF, TIFF or JPEG attachment, for a scan-to-email or Internet fax test. "email_addresses" is left out while the email test is off. Every test that Faxbeep receives is public on faxbeep.com for 30 days. Tell the person not to send a private document. "limits" has the limits of the email test: "email_max_message_bytes" is the size of the whole email, and email encoding adds about a third, so the attachment can be about three quarters of it. "troubleshooting_url" is the docs page with each refusal message of the email test and its fix. "now" is the server time. Use it as "since" of list_test_faxes: call this tool, or take "now" from your last result, just before the person sends the test. Do not use your own clock.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_test_faxes ~627

List the test faxes that Faxbeep received and published, newest first. The list is public and holds the tests of everyone. Each item of "faxes" is a fax object: slug, source ("phone" or "email"), from (the sender, masked as on faxbeep.com, or null), received_at, page_count, file_size, pdf_url, thumbnail_url and view_url (the page of the fax on faxbeep.com). In the result, "since" is the start time that was used, and "now" is the server time. The result holds at most "limit" faxes (20 when not given), newest first, with no paging. When "faxes" has "limit" items, there can be more: narrow the list with from, page_count or a since closer to the test. Set "since" to the "now" value that get_test_numbers or list_test_faxes returned just before the person sent the test, and keep it fixed while you poll. Do not use your own clock. Do not move since to the newest received_at: a long fax can appear after a newer, shorter one. Without "since", the list covers the last 24 hours. A match by time, sender or page count narrows the candidates. It does not prove that a fax is the person's, because other people send tests at the same time. Show the person the view_url so they can check the page. In a chat that shows images, also show thumbnail_url as an image in your answer. An empty list is a normal answer while a fax is on its way. A new fax usually appears within a minute after the call ends or the email is sent; a few take longer. Wait about 30 seconds between calls, and stop after about 10 minutes. A fax is public for 30 days, then it is removed. For a sample answer, set from to FAXBEEP-EXAMPLE: the result is the sample fax fax_example, whatever since says. The sample has a fixed date in the past, older than 30 days, and it stays available.

NameTypeReqDescription
fromstring|null–Only faxes from this sender: the full fax number (for example +15555550123) or station ID of the sending machine, or the sender address of an email test. Not the masked value of a result. The whole v…
limitinteger|null–The most faxes to return, from 1 to 100. Default: 20.
page_countinteger|null–Only faxes with this number of pages.
sincestring|null–Only faxes received after this time, in ISO 8601 with an offset. Use the "now" value of get_test_numbers or of a list_test_faxes result, taken just before the person sends the test, not your own cloc…

No output schema declared.

No examples provided.

Install

How do I install the Faxbeep MCP server?

Faxbeep is a hosted endpoint at https://faxbeep.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · faxbeep.com

# add to Claude Code
claude mcp add --transport http com-faxbeep-faxbeep 'https://faxbeep.com/mcp'
Common questions

What is the Faxbeep MCP server?

Faxbeep is an MCP server listed in the public MCP registry as com.faxbeep/faxbeep. Test fax numbers for AI agents. Send a test fax or scan-to-email, then read what Faxbeep received. This page covers its hosted endpoint (https://faxbeep.com/mcp).

Is the Faxbeep MCP server safe to use?

Faxbeep scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Faxbeep MCP server expose?

Faxbeep exposes 3 tools: get_test_numbers, list_test_faxes, get_test_fax. Their descriptions and schemas cost roughly 1,186 tokens of context every time the server is loaded.

Does the Faxbeep MCP server require authentication?

No. We connected to Faxbeep without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Faxbeep MCP server still maintained?

Faxbeep is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Faxbeep MCP server?

VerifyMCP ran 13 checks on Faxbeep, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.