# Faxbeep (remote · faxbeep.com)

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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `faxbeep.com`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep.md), [page](https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep)

## Channel facts

- Endpoint: `https://faxbeep.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## 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.

### Claude

```bash
claude mcp add --transport http com-faxbeep-faxbeep 'https://faxbeep.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-faxbeep-faxbeep": {
      "url": "https://faxbeep.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-faxbeep-faxbeep": {
      "type": "http",
      "url": "https://faxbeep.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-faxbeep-faxbeep]
url = "https://faxbeep.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-faxbeep-faxbeep": {
      "type": "remote",
      "url": "https://faxbeep.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-faxbeep-faxbeep --url 'https://faxbeep.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-faxbeep-faxbeep:
    url: "https://faxbeep.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-faxbeep-faxbeep": {
      "Transport": "http",
      "Url": "https://faxbeep.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-faxbeep-faxbeep -t streamable-http -u 'https://faxbeep.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-faxbeep-faxbeep": {
      "type": "http",
      "url": "https://faxbeep.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 76, +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.

### 2026-11-18 (score 75, +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.

### 2026-11-16 (score 74, +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.

### 2026-11-14 (score 73, +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.

### 2026-11-12 (score 72, +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.

### 2026-11-10 (score 71, +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.

### 2026-11-07 (score 70, +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.

### 2026-11-06 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (3)

### `get_test_numbers` (~274 tokens)

Get the test numbers

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.

### `list_test_faxes` (~627 tokens)

List received test faxes

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.

Input parameters:

- `from` (string|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…
- `limit` (integer|null): The most faxes to return, from 1 to 100. Default: 20.
- `page_count` (integer|null): Only faxes with this number of pages.
- `since` (string|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…

### `get_test_fax` (~285 tokens)

Get a test fax

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).

Input parameters:

- `fax` (string, required): The slug of the fax (for example fax_1a2b3c4d), or the URL of its page on faxbeep.com (view_url).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70
- 2026-11-08: 70
- 2026-11-07: 70
- 2026-11-06: 69
- 2026-11-05: 69

## 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.

## Links

- Remote endpoint: https://faxbeep.com/mcp
- Repository: https://github.com/faxbeep/faxbeep-mcp
- Website: https://faxbeep.com/test-fax-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep.json
- HTML version of this page: https://verifymcp.io/servers/com-faxbeep-faxbeep/faxbeep
