# MailBots (remote · api.mailbots.top)

Read verification codes (OTP) and test email sent to your catch-all test hostnames.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `api.mailbots.top`: 83/100 (this document), [markdown](https://verifymcp.io/servers/top-mailbots-mailbots/v1-mcp.md), [page](https://verifymcp.io/servers/top-mailbots-mailbots/v1-mcp)

## Channel facts

- Endpoint: `https://api.mailbots.top/v1/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.0.0`

## 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**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 79/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 505 tokens (~126/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the MailBots MCP server?

MailBots is a hosted endpoint at https://api.mailbots.top/v1/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 top-mailbots-mailbots 'https://api.mailbots.top/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "top-mailbots-mailbots": {
      "url": "https://api.mailbots.top/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "top-mailbots-mailbots": {
      "type": "http",
      "url": "https://api.mailbots.top/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.top-mailbots-mailbots]
url = "https://api.mailbots.top/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "top-mailbots-mailbots": {
      "type": "remote",
      "url": "https://api.mailbots.top/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add top-mailbots-mailbots --url 'https://api.mailbots.top/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  top-mailbots-mailbots:
    url: "https://api.mailbots.top/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "top-mailbots-mailbots": {
      "Transport": "http",
      "Url": "https://api.mailbots.top/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add top-mailbots-mailbots -t streamable-http -u 'https://api.mailbots.top/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "top-mailbots-mailbots": {
      "type": "http",
      "url": "https://api.mailbots.top/v1/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-21 (score 83, +1)

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

### 2026-11-19 (score 82, +1)

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

### 2026-11-17 (score 81, +1)

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

### 2026-11-15 (score 80, +1)

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

### 2026-11-12 (score 79, +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-11 (score 78, +1)

- [security] Tool “get_latest_otp” rewrote its description, which is the text the model reads
- [security] Tool “get_message” rewrote its description, which is the text the model reads
- [security] Tool “list_domains” rewrote its description, which is the text the model reads
- [security] Tool “list_messages” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: good → excellent

### 2026-11-09 (score 77, +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-08 (score 76, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (4)

### `list_domains` (~57 tokens)

List receiving hostnames

List the hostnames this API key can receive mail on. Call it first to build a test address: any address at a hostname with receiving=true reaches the inbox. Returns each hostname with its status, and trialEndsAt for a trial hostname.

### `get_latest_otp` (~128 tokens)

Get the latest verification code

Get the newest message sent to one address and the verification code (OTP) extracted from it. Returns found=false while nothing has arrived: wait about 5 seconds and call it again. When the message has no code, such as a verification link, otp is null; call get_message with message.id to read the body.

Input parameters:

- `since` (string): Optional ISO 8601 time. Ignore messages received before it, e.g. the moment the test started.
- `to` (string, required): Full recipient address, e.g. signup-42@otp.example.com. Case-insensitive.

### `list_messages` (~100 tokens)

List recent messages

List recent messages, newest first, optionally only those sent to one address. Returns the id, sender, subject, extracted code and times of each message, not the body; expired messages are left out. Call get_message with an id to read one.

Input parameters:

- `limit` (integer): How many messages to return (default 10).
- `to` (string): Full recipient address, e.g. signup-42@otp.example.com. Case-insensitive.

### `get_message` (~88 tokens)

Read one message

Read one message by id, with its plain-text body (up to 20,000 characters), for verification links or anything the otp field misses. Returns an error when no message has that id, which also happens once the message expires: after 24 hours on the trial and 72 hours on paid plans.

Input parameters:

- `id` (string, required): Message id from list_messages or get_latest_otp.

## Diagnostics

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

## Score history

- 2026-11-21: 83
- 2026-11-20: 82
- 2026-11-19: 82
- 2026-11-18: 81
- 2026-11-17: 81
- 2026-11-16: 80
- 2026-11-15: 80
- 2026-11-14: 79
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 78
- 2026-11-10: 77
- 2026-11-09: 77
- 2026-11-08: 76
- 2026-11-07: 76

## Common questions

### What is the MailBots MCP server?

MailBots is an MCP server listed in the public MCP registry as top.mailbots/mailbots. Read verification codes (OTP) and test email sent to your catch-all test hostnames. This page covers its hosted endpoint (https://api.mailbots.top/v1/mcp).

### Is the MailBots MCP server safe to use?

MailBots scores 83 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 MailBots MCP server expose?

MailBots exposes 4 tools: list_domains, get_latest_otp, list_messages, get_message. Their descriptions and schemas cost roughly 373 tokens of context every time the server is loaded.

### Does the MailBots MCP server require authentication?

Yes. MailBots asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the MailBots MCP server still maintained?

MailBots 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 MailBots MCP server?

VerifyMCP ran 13 checks on MailBots, 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://api.mailbots.top/v1/mcp
- Authorisation metadata: https://api.mailbots.top/.well-known/oauth-protected-resource/v1/mcp
- Website: https://mailbots.top/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/top-mailbots-mailbots/v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/top-mailbots-mailbots/v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/top-mailbots-mailbots/v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/top-mailbots-mailbots/v1-mcp
