mailslurp.com valid

MailSlurp

MailSlurp provides real email addresses, connected mailboxes, phone numbers, and APIs for software tests, automated workflows, and supervised AI agents. Use it to send and receive email or SMS, verify OTP and account flows, route inbound messages, process attachments, extract structured data, and measure email quality and deliverability.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-20T17:26:44.661Z. Cached copy · Source on mailslurp.com

# MailSlurp

> MailSlurp provides real email addresses, connected mailboxes, phone numbers, and APIs for software tests, automated workflows, and supervised AI agents. Use it to send and receive email or SMS, verify OTP and account flows, route inbound messages, process attachments, extract structured data, and measure email quality and deliverability.

## Canonical Locations

- Website: https://www.mailslurp.com/
- Dashboard: https://app.mailslurp.com/
- Documentation: https://www.mailslurp.com/docs/
- Agent and MCP guide: https://www.mailslurp.com/docs/agents/
- Quick start: https://www.mailslurp.com/docs/quick-start/
- API reference: https://www.mailslurp.com/docs/api/
- REST API base URL: https://api.mailslurp.com
- Hosted MCP endpoint: https://api.mailslurp.com/mcp
- OpenAPI JSON: https://api.mailslurp.com/v2/api-docs/
- Swagger UI: https://swagger.mailslurp.com/
- Postman collection: https://www.postman.com/mailslurp-api
- Documentation search: https://www.mailslurp.com/search/
- RSS feed: https://www.mailslurp.com/rss.xml

Use the OpenAPI document or an official SDK as the source of truth for request and response schemas. Do not invent endpoint parameters from examples.

## Choose How To Connect

### 1. MCP OAuth For An AI Client

Use MCP OAuth for Claude, ChatGPT, Cursor, or another remote MCP client that supports OAuth. This is the preferred interactive AI-agent connection because the user authorizes MailSlurp in the browser and does not copy a secret into the client.

1. Add `https://api.mailslurp.com/mcp` as a remote MCP server in the AI client.
2. Let the client use MCP discovery and start OAuth. Do not manually implement the authorization, registration, or token endpoints unless building an MCP client.
3. Ask the user to name the connection, choose the narrowest role, and select inbox IDs, inbox tags, or deliberate account-wide access.
4. After authorization, call `mailslurp.list_accessible_inboxes` before using an inbox or email ID.
5. Prefer search and wait tools over guessing resource IDs or repeatedly polling every message.

MCP OAuth authorizes the AI client to use MailSlurp. It is separate from Gmail or Outlook OAuth, which connects an existing mailbox to MailSlurp.

### 2. Scoped Agent Key

Use a scoped agent key for a custom service, background worker, server-to-server integration, or MCP client that accepts a manually configured header.

- Create one in the dashboard: https://app.mailslurp.com/agents/keys/new
- Or create one with `POST /account/agent-api-keys` using an authorized account key.
- Send the returned raw key as `x-api-key` to the hosted MCP endpoint or Agent REST API.
- Store it in a secret manager. The raw value is only shown at creation time.
- Keep separate keys for agents, tenants, environments, and independently revocable workflows.

A normal account API key is intentionally not an agent MCP credential. Create a dedicated agent key when calling MCP agent tools.

### 3. Standard REST API Or Official SDK

Use
…

Related sites

Find similar publishers by meaning →

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=mailslurp.com · GET /v1/domain/mailslurp.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for mailslurp.com:
1. POST https://agentwebmap.com/v1/sites/mailslurp.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://mailslurp.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/mailslurp.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/mailslurp.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.