Koskamo

MailBots MCP

The MailBots MCP server enables AI agents to read verification codes (OTP) and test emails received on catch-all hostnames. It provides read-only tools to list domains, retrieve the latest OTP, list messages, and fetch message bodies, facilitating automated testing of signup and login flows without sending or modifying data.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

MailBots MCP logo, by MailBotsVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-07Operated by MailBots
You need:Start the free trial or choose a plancreate an API keyA key with messages:read and domains:read covers every tool
MCP endpoint (Streamable HTTP)
https://api.mailbots.top/v1/mcp
Vendor documentation

What its tools do

4 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

4 of 4 have a description · 4 of 4 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Passed Official MCP Registry namespace is tied to mailbots.top ·
  • Passed Endpoint is on the registry namespace domain ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Fetch verification codes for automated signup flows
  • List available test email domains
  • Retrieve recent messages and their content
  • Read specific message bodies for magic links

Source and maintenance

Vendor evidenceRegistry 1.0.0

Protocol and capabilities

Server
mailbots 1.0.0
MCP protocol negotiated in check
2025-06-18
Tools
4 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

MailBots receives email for end-to-end tests on catch-all hostnames: every address under a hostname reaches the inbox. Tool calls need a MailBots API key (Authorization: Bearer mb_live_…) from a trial or paid plan. Use a fresh address per test run, such as signup-<run id>@<hostname> (call list_domains for the hostnames). After the app under test sends its email, call get_latest_otp with that address. Delivery usually takes a few seconds; if no message has arrived yet, wait about 5 seconds and call it again. Only test applications you own or are authorized to test.

Tools

4 advertised

list_domains — List receiving hostnames
Advertised by the server during the last successful anonymous check.
Advertised read-only

List the hostnames this API key can receive mail on, with their status. Any address at an active hostname reaches the inbox.

list_domains input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
list_domains annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_latest_otp — Get the latest verification code
Advertised by the server during the last successful anonymous check.
Advertised read-only

Return the newest message sent to an address and the verification code (OTP) extracted from it. Returns found=false when nothing has arrived yet; wait a few seconds and retry.

get_latest_otp input schema
{
  "type": "object",
  "required": [
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Full recipient address, e.g. signup-42@otp.example.com. Case-insensitive."
    },
    "since": {
      "type": "string",
      "description": "Optional ISO 8601 time. Ignore messages received before it, e.g. the moment the test started."
    }
  },
  "additionalProperties": false
}
get_latest_otp annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
list_messages — List recent messages
Advertised by the server during the last successful anonymous check.
Advertised read-only

List recent messages, newest first, optionally only those sent to one address. Returns metadata and the OTP, not the body.

list_messages input schema
{
  "type": "object",
  "properties": {
    "to": {
      "type": "string",
      "description": "Full recipient address, e.g. signup-42@otp.example.com. Case-insensitive."
    },
    "limit": {
      "type": "integer",
      "maximum": 50,
      "minimum": 1,
      "description": "How many messages to return (default 10)."
    }
  },
  "additionalProperties": false
}
list_messages annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}
get_message — Read one message
Advertised by the server during the last successful anonymous check.
Advertised read-only

Return one message by id, including its plain-text body (truncated to 20,000 characters).

get_message input schema
{
  "type": "object",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "description": "Message id from list_messages or get_latest_otp."
    }
  },
  "additionalProperties": false
}
get_message annotations
{
  "readOnlyHint": true,
  "openWorldHint": false
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
200 ms
95th percentile latency
200 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 200 ms · metadata changed · 4 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http mailbots-mcp https://api.mailbots.top/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add mailbots-mcp --url https://api.mailbots.top/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable mailbots-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "mailbots-mcp": {
      "url": "https://api.mailbots.top/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "mailbots-mcp": {
      "type": "streamableHttp",
      "url": "https://api.mailbots.top/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start mailbots-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "mailbots-mcp": {
      "type": "http",
      "url": "https://api.mailbots.top/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http mailbots-mcp https://api.mailbots.top/v1/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.mailbots.top/v1/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "mailbots-mcp": {
      "serverUrl": "https://api.mailbots.top/v1/mcp"
    }
  }
}

Let your agent find its tools

Find servers like MailBots MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run MailBots MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing