Inbox Check — Email Deliverability Test
MCP server that runs email inbox placement tests across major providers for AI agents
- Pricing
- Freemium
- Platforms
- API, CLI, Web
- Runs
- Locally
- Version
- 0.1.2
- Listing updated
- today
Similar MCP servers
About Inbox Check — Email Deliverability Test
Inbox Check — Email Deliverability Test is a freemium MCP server for communication. It runs locally on your machine and is started by your AI client.
The README describes Inbox Check as a hosted service that sends a test email to seed mailboxes at nine providers, including Gmail, Outlook, Yahoo, iCloud, AOL, GMX, T-Online, Mail.ru and Yandex. The MCP server wraps its REST API so an agent can create a test, get the seed addresses, and read back where each message landed.
After the user approves a message, the sending itself happens through the user's own mail service; the server only creates the test and reports results. Results include folder placement such as Inbox, Spam, Promotions or Updates, plus SPF, DKIM and DMARC outcomes parsed from the Authentication-Results headers, and screenshots where providers expose them. The docs say results are polled by token and that a finished status alone does not prove inbox delivery.
The page describes a guest mode that needs no key for basic tests, with per-day and per-month limits on the signed-in Basic tier. It suits marketers, deliverability staff and developers checking campaign templates or authentication setup.
Install
Run in a terminal
claude mcp add inbox-check --env INBOX_CHECK_API_KEY='<INBOX_CHECK_API_KEY>' -- npx -y ldm-inbox-check-mcpAdd to claude_desktop_config.json
{
"mcpServers": {
"inbox-check": {
"command": "npx",
"args": [
"-y",
"ldm-inbox-check-mcp"
],
"env": {
"INBOX_CHECK_API_KEY": "<INBOX_CHECK_API_KEY>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"inbox-check": {
"command": "npx",
"args": [
"-y",
"ldm-inbox-check-mcp"
],
"env": {
"INBOX_CHECK_API_KEY": "<INBOX_CHECK_API_KEY>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"inbox-check": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"ldm-inbox-check-mcp"
],
"env": {
"INBOX_CHECK_API_KEY": "<INBOX_CHECK_API_KEY>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"inbox-check": {
"command": "npx",
"args": [
"-y",
"ldm-inbox-check-mcp"
],
"env": {
"INBOX_CHECK_API_KEY": "<INBOX_CHECK_API_KEY>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"inbox-check": {
"command": "npx",
"args": [
"-y",
"ldm-inbox-check-mcp"
],
"env": {
"INBOX_CHECK_API_KEY": "<INBOX_CHECK_API_KEY>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
INBOX_CHECK_API_KEYBearer API key for Inbox Check service (starts with icp_live_)RequiredINBOX_CHECK_BASE_URLOverride base URL for self-hosted deployments
Tools this server provides (5)
Taken from the project documentation; the running server may differ.
- inbox_check_create
- Create a placement test; returns seed addresses to send your email to.
- inbox_check_status
- Get per-provider placement, SPF/DKIM/DMARC, screenshots.
- inbox_check_list
- List recent tests with cursor pagination.
- inbox_check_delete
- Delete a test and its screenshots.
- inbox_check_me
- Inspect API key metadata, features, quota usage.
What it does
- Nine provider seed mailboxes
- Tests run against real seed accounts at Gmail, Outlook, Yahoo, iCloud, AOL, GMX, T-Online, Mail.ru and Yandex.
- Folder placement reporting
- Results show whether a message landed in Inbox, Spam, Promotions, Updates or other provider tabs.
- SPF, DKIM and DMARC checks
- Authentication outcomes are reported per delivery, parsed from message headers.
- Guest mode without a key
- Basic tools can be called at the MCP URL with no registration, according to the docs.
- Cursor-paginated test history
- An agent can list recent tests and page through them using cursors.
- Quota inspection
- The me tool returns key metadata, features and quota usage.
Good for
- Check whether a campaign draft reaches the inbox at Gmail and Outlook before sending
- Diagnose why a sending domain is landing in spam by reviewing authentication results
- Compare placement of old and new email templates across providers
- Verify that transactional emails such as password resets reach the inbox
Pricing
Freemium
Free guest tools; Basic signed-in tier with default daily and monthly limits; higher package on request.
Prices change. Check check.live-direct-marketing.online before you buy.
More servers for the same service
Inbox Check — Email Deliverability Test FAQ
Do I need an API key to use it?
The docs say free guest tools need no registration or key. Connecting with an invalid key returns a 401, so the key should be removed for guest mode. Managed operations such as account and monitoring use a key.
Does the server send the test email itself?
No. The docs say creating a test does not send email. The message must be sent through the user's own authorized mail service to the returned seed addresses, or the addresses are given to a person to send.
Which MCP transport does it use?
The hosted endpoint uses Streamable HTTP at the listed URL. The npm package ldm-inbox-check-mcp runs over stdio and needs the INBOX_CHECK_API_KEY environment variable.
What are the default usage limits?
The docs state Basic accounts get 100 checks per day and 1,000 per month by default, without screenshots. A free 500/5,000 package can be requested in Account and starts after approval.
Is Inbox Check — Email Deliverability Test free?
Inbox Check — Email Deliverability Test has a free plan, with paid plans for more usage or features.
How do I add Inbox Check — Email Deliverability Test to Claude Code?
Run this command in your terminal: claude mcp add inbox-check --env INBOX_CHECK_API_KEY='<INBOX_CHECK_API_KEY>' -- npx -y ldm-inbox-check-mcp
What are the best alternatives to Inbox Check — Email Deliverability Test?
The closest alternatives to Inbox Check — Email Deliverability Test are Email Spam Tester, Email List Validation Email Verification, MailTester Ninja, inboxmcp and WarmInboxes Free MCP.
Where this comes from
- Description: written from the project's README, the project's website and its MCP Registry entry.
- Install steps: from the official MCP Registry entry.
