Koskamo

echo.email MCP

An official Model Context Protocol server provided by echo.email that enables AI agents to automate email deliverability testing. Agents can create temporary test addresses, send emails to them, and retrieve detailed reports on authentication (SPF, DKIM, DMARC), delivery status, and spam scoring without requiring API keys or user signup.

Visit echo.email

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.

echo.email MCP logo, by echo.emailVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by echo.email
MCP endpoint (Streamable HTTP)
https://mcp.echo.email/mcp
Vendor documentation

What you can do with it

  • Create a temporary email address for testing
  • Wait for and retrieve email deliverability reports
  • Check SPF, DKIM, DMARC, and TLS compliance

Source and maintenance

Vendor evidenceRegistry 1.1.0
mcp-registry: email.echo/deliverability@1.1.0Project website

Protocol and capabilities

Server
echo.email 1.1.0
MCP protocol
2025-06-18
Tools
3 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.

Create a test address, send one email to it, then wait for the report.

Tools

3 advertised

create_test_address — Create test address
Advertised by the server during the last successful anonymous check.

Create a temporary echo.email address. Send one email to it from the system under test, then call wait_for_report with the returned token and key. The address dies after 10 minutes without a wait_for_report call and accepts one message.

create_test_address input schema
{
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
wait_for_report — Wait for report
Advertised by the server during the last successful anonymous check.

Wait up to timeout_s seconds (max 50) for the email sent to a test address to be analysed. Returns status waiting or received (call again), or done with a digest: score, SPF, DKIM, DMARC, TLS, IPv6 and the failing sender requirements.

wait_for_report input schema
{
  "type": "object",
  "required": [
    "token",
    "key"
  ],
  "properties": {
    "key": {
      "type": "string",
      "description": "Key from create_test_address"
    },
    "token": {
      "type": "string",
      "description": "Token from create_test_address (the address local part)"
    },
    "timeout_s": {
      "type": "number",
      "default": 45,
      "maximum": 50,
      "minimum": 1
    }
  }
}
get_report — Get report
Advertised by the server during the last successful anonymous check.

Fetch a finished report as JSON: the digest plus every check (SPF trace, DKIM, DMARC, BIMI, TLS, IPv6, images, links, unsubscribe, headers, DNS log).

get_report input schema
{
  "type": "object",
  "required": [
    "report_id"
  ],
  "properties": {
    "report_id": {
      "type": "string"
    }
  }
}

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
507 ms
95th percentile latency
507 ms

Maintenance history

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

  • · probe · passed · 507 ms · metadata changed · 3 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 echo-email-mcp https://mcp.echo.email/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 echo-email-mcp --url https://mcp.echo.email/mcp

Cursor

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

Cline

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

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start echo-email-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "echo-email-mcp": {
      "type": "http",
      "url": "https://mcp.echo.email/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 echo-email-mcp https://mcp.echo.email/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "echo-email-mcp": {
      "url": "https://mcp.echo.email/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": {
    "echo-email-mcp": {
      "serverUrl": "https://mcp.echo.email/mcp"
    }
  }
}

Let your agent find its tools

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

Connect Koskamo Explore workflows
See all 6,828

Do you run echo.email 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