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.

MailBots

REMOTE · API.MAILBOTS.TOP

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

Available components

+4 this week 83 Trust /100

Last scanned (12 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Testing and QA

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 Security89
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management47
  • Stability observed for 14 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 15 Nov 26 +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.

  • 12 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.

  • 11 Nov 26 +1
    • 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 security
    • Schema quality: pass → fail ▼ functional
    • Schema quality: good → excellent functional
  • 9 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.

  • 8 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://api.mailbots.top/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mailbots.top CN=WE1,O=Google Trust Services,C=US 12 Nov 2026 10 Feb 2027 ECDSA 256 ECDSA-SHA256 67933ef82b2115270e1961e292a46987
SANs: mailbots.top, api.mailbots.top, *.api.mailbots.top
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 api.mailbots.top. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
top. DS published 41508 13 Verified
mailbots.top. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Challenged, unverified

The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.

Result Challenged, unverified
Enforced On tool calls
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy default-src 'self'; script-src 'self'; style-src 'self'; img-src 'self' data:; connect-src 'self'; font-src 'self'; frame-ancestors 'none'; base-uri 'self'; form-action 'self'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Protected resource metadata

Retrieved No
Problem No resource metadata

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.mailbots.top/v1/mcp Verified 200
http (plaintext) http://api.mailbots.top/v1/mcp HTTPS enforced 301 https://api.mailbots.top/v1/mcp
MCP tools · 4 exposed · ~373 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_latest_otp ~128

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.

NameTypeReqDescription
sincestring–Optional ISO 8601 time. Ignore messages received before it, e.g. the moment the test started.
tostringyesFull recipient address, e.g. signup-42@otp.example.com. Case-insensitive.

No output schema declared.

No examples provided.

get_message ~88

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.

NameTypeReqDescription
idstringyesMessage id from list_messages or get_latest_otp.

No output schema declared.

No examples provided.

list_domains ~57

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_messages ~100

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.

NameTypeReqDescription
limitinteger–How many messages to return (default 10).
tostring–Full recipient address, e.g. signup-42@otp.example.com. Case-insensitive.

No output schema declared.

No examples provided.

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.

remote · api.mailbots.top

# add to Claude Code
claude mcp add --transport http top-mailbots-mailbots 'https://api.mailbots.top/v1/mcp'
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.