_ registry / mcp streamable-http · checked 57m ago

emailens

https://emailens.dev

Registry code: be6d670150f73158

api record

Email compatibility analysis across 15 clients — preview, audit, fix, diff, deliverability.

from a public catalogue that lists it, not from the operator

endpoint
https://emailens.dev/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is emailens live?
Yes — it answered the hub's last check (checked 57m ago). It answered 99% of checks over the last 30 days.
Is emailens free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does emailens have?
15 tools: analyze_email, diff_emails, share_preview, build_email, sandbox_get_inbox, preview_email, check_deliverability, fix_email, ….
Is emailens safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
98.6%

90 days 98.3%· all time 98.3%

latency
193ms

last good check

priced tools
0

of 15 tools

_ answered our checks, 90 days 412 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
communication email
used for
  • check email html compatibility across clients
  • audit an email for spam and accessibility
  • check domain email deliverability
  • generate a compatible email from a brief
  • diff two email versions
takes → gives
code, text → data, code
tools
8 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 15 tools
1 open1 auth-required 13 never probed 2 of 15 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_clients reads open 57m ago

    List all 21 supported email clients with IDs, names, rendering engines, dark mode support, and deprecation status. Use the returned IDs to filter other tools like preview_email or capture_screenshots.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {}
}
    arguments 5 lines
  • sandbox_list_messages auth-required 57m ago

    List recently captured test emails in the Emailens sandbox.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "inboxId": {
      "type": "string",
      "description": "Optional inbox ID filter"
    }
  }
}
    arguments 10 lines
  • analyze_email reads unknown never probed

    Fix error and warning findings. Info findings are not problems (the email falls back safely there): never remove responsive (@media) or dark-mode CSS to clear them. Quick CSS compatibility analysis, returns per-client scores and one finding per problem, listing the clients it affects. For HTML input each finding carries loc (line, column, offset) and alsoAtLines, so you can edit the exact source. Narrow with clients, or pass detail:'full' for the per-client breakdown with fix snippets. Use audit_email for a full quality report (spam, links, a11y, images, etc.).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The email source"
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string",
      "description": "'summary' (default) returns one entry per error or warning, listing the clients it affects, and only counts info findings (safe fallbacks). 'full' returns one entry per client with fix snippets, info included."
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Source format: 'html' (default), 'jsx' (React Email), 'mjml', or 'maizzle' (HTML template or Vue single-file component). Anything but 'html' is compiled before analysis and sets the syntax of the fix snippets. A pasted Vue file with no format is compiled as maizzle."
    },
    "clients": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only report these client IDs (e.g. ['gmail-web','outlook-windows']). The fastest way to cut the response when you care about specific clients. Use list_clients for the IDs."
    },
    "targetingPolicy": {
      "enum": [
        "progressive",
        "strict",
        "lenient"
      ],
      "type": "string",
      "description": "'progressive' (default) suppresses compatibility false-positives inside client-targeted scopes and only flags deprecated or dangerous hacks. 'strict' treats targeting as non-standard and reports every hack. 'lenient' suppresses false positives and ignores non-fatal targeting warnings."
    }
  }
}
    arguments 47 lines
  • diff_emails reads unknown never probed

    Compare two email HTML versions , shows score changes, fixed issues, and regressions per client.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "before",
    "after"
  ],
  "properties": {
    "after": {
      "type": "string",
      "description": "Modified email HTML"
    },
    "before": {
      "type": "string",
      "description": "Original email HTML"
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Input format"
    }
  }
}
    arguments 28 lines
  • share_preview unknown never probed

    Create a shareable link for an email preview. Recipients see the full analysis without needing an account. Requires the Dev plan or above.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The email source"
    },
    "title": {
      "type": "string",
      "description": "Display title for the share page"
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Input format"
    }
  }
}
    arguments 27 lines
  • build_email changes data unknown never probed

    Generate a cross-client-compatible email from a brief using Emailens's self-healing loop (generate → score across 21 clients → repair). Output stays in the framework you choose. Returns a runId immediately , poll get_build_status for progress and the final code. Requires a Pro/Team API key.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "intent"
  ],
  "properties": {
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Output framework: 'html' (default), 'jsx', 'mjml', or 'maizzle'"
    },
    "intent": {
      "type": "string",
      "description": "What the email should be and contain , the brief to build from"
    },
    "seedHtml": {
      "type": "string",
      "description": "Optional existing code to improve from instead of starting blank"
    },
    "threshold": {
      "type": "number",
      "description": "Target compatibility score, 50-100 (default 90)"
    },
    "maxIterations": {
      "type": "number",
      "description": "Max repair rounds, 1-8 (default 5)"
    }
  }
}
    arguments 35 lines
  • sandbox_get_inbox unknown never probed

    Retrieve or auto-create your Emailens sandbox test email address for capturing test emails.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string",
      "description": "Optional friendly name for the sandbox inbox"
    }
  }
}
    arguments 10 lines
  • preview_email reads unknown never probed

    Full email compatibility preview , transforms HTML for 21 email clients, analyzes CSS, generates scores, previews dark mode, checks inbox preview and email size.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The email HTML source code"
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Source format: 'html' (default), 'jsx' (React Email), 'mjml', or 'maizzle' (HTML template or Vue single-file component). Anything but 'html' is compiled before analysis and sets the syntax of the fix snippets. A pasted Vue file with no format is compiled as maizzle."
    },
    "clients": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional client ID filter"
    },
    "targetingPolicy": {
      "enum": [
        "progressive",
        "strict",
        "lenient"
      ],
      "type": "string",
      "description": "'progressive' (default) suppresses compatibility false-positives inside client-targeted scopes and only flags deprecated or dangerous hacks. 'strict' treats targeting as non-standard and reports every hack. 'lenient' suppresses false positives and ignores non-fatal targeting warnings."
    }
  }
}
    arguments 39 lines
  • check_deliverability reads unknown 57m ago

    Check email deliverability for a domain , SPF, DKIM, DMARC, MX, BIMI.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "pattern": "^[a-z0-9]([a-z0-9-]*[a-z0-9])?(\\.[a-z0-9]([a-z0-9-]*[a-z0-9])?)+$",
      "minLength": 3,
      "description": "Domain to check (e.g. 'company.com')"
    }
  }
}
    arguments 15 lines
  • fix_email reads unknown never probed

    Generate a structured fix prompt for email compatibility issues.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The email HTML source code to fix"
    },
    "scope": {
      "enum": [
        "all",
        "current"
      ],
      "type": "string",
      "description": "Fix scope"
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Input format , controls fix syntax"
    },
    "selectedClientId": {
      "type": "string",
      "description": "Client ID for scoped fixes"
    }
  }
}
    arguments 35 lines
  • capture_screenshots unknown never probed

    Capture real email screenshots across 21 clients (Gmail, Outlook, Apple Mail, etc.) with light and dark mode variants. Screenshots are rendered in real browsers and hosted on CDN.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The email source"
    },
    "modes": {
      "type": "array",
      "items": {
        "enum": [
          "light",
          "dark"
        ],
        "type": "string"
      },
      "description": "Screenshot modes (default: ['light'])"
    },
    "title": {
      "type": "string",
      "description": "Name for the hosted preview"
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Input format"
    },
    "clients": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Filter to specific client IDs"
    }
  }
}
    arguments 45 lines
  • sandbox_wait_for_email unknown never probed

    Poll and wait for a matching incoming test email in the sandbox (ideal for auth OTPs, magic links, transactional email assertions).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "sender": {
      "type": "string",
      "description": "Substring match for sender address (case-insensitive)"
    },
    "inboxId": {
      "type": "string",
      "description": "Optional inbox ID filter"
    },
    "subject": {
      "type": "string",
      "description": "Substring match for email subject (case-insensitive)"
    },
    "timeoutSeconds": {
      "type": "number",
      "description": "Max seconds to wait (default: 30, max: 60)"
    }
  }
}
    arguments 22 lines
  • audit_email reads unknown never probed

    Fix error and warning findings, and restore anything listed in designRemovals. Info findings are not problems (the email falls back safely there): never remove responsive (@media), dark-mode CSS or rounded corners to clear them. designRemovals compares this version with the first one audited for the same email (or with previousHtml): design the edits deleted, such as @media rules, dark mode, corners, gradients, VML fallbacks or images. Comprehensive email quality audit: CSS compatibility, spam scoring, link validation, accessibility, images, inbox preview, size (Gmail clipping), template variables, content overflow, visual fallbacks, dark-mode and mobile text contrast, design consistency, structural faults in Outlook-only VML, style survival (CSS a client parses and then discards, such as a stylesheet past Gmail's 16 KB ceiling or every rule after a `}}`), and client targeting (HowToTarget hacks such as Gmail u+.body or MSO conditionals). For HTML input, findings tied to a specific element carry loc (line, column, offset). Compatibility is collapsed to one finding per problem listing the clients it affects; pass detail:'full' for the per-client breakdown with fix snippets. Use skip to omit checks, targetingPolicy to change how targeted scopes affect scores, and clients to narrow which clients are reported.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "html"
  ],
  "properties": {
    "html": {
      "type": "string",
      "description": "The email source"
    },
    "skip": {
      "type": "array",
      "items": {
        "enum": [
          "spam",
          "links",
          "accessibility",
          "images",
          "compatibility",
          "inboxPreview",
          "size",
          "templateVariables",
          "overflow",
          "visual",
          "darkContrast",
          "mobileContrast",
          "design",
          "vml",
          "styleSurvival",
          "targeting"
        ],
        "type": "string"
      },
      "description": "Checks to skip (e.g. ['spam', 'images'])"
    },
    "detail": {
      "enum": [
        "summary",
        "full"
      ],
      "type": "string",
      "description": "'summary' (default) returns one entry per error or warning, listing the clients it affects, and only counts info findings (safe fallbacks). 'full' returns one entry per client with fix snippets, info included."
    },
    "format": {
      "enum": [
        "html",
        "jsx",
        "mjml",
        "maizzle"
      ],
      "type": "string",
      "description": "Source format: 'html' (default), 'jsx' (React Email), 'mjml', or 'maizzle' (HTML template or Vue single-file component). Anything but 'html' is compiled before analysis and sets the syntax of the fix snippets. A pasted Vue file with no format is compiled as maizzle."
    },
    "clients": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Only report these client IDs (e.g. ['gmail-web','outlook-windows']). The fastest way to cut the response when you care about specific clients. Use list_clients for the IDs."
    },
    "emailType": {
      "enum": [
        "marketing",
        "transactional"
      ],
      "type": "string",
      "description": "'transactional' (receipts, password resets, codes, alerts: no unsubscribe link required) or 'marketing'. Omitted: guessed from the content, which misses many transactional emails."
    },
    "previousHtml": {
      "type": "string",
      "description": "The design to hold this version to, usually your first draft. Omitted: the first version of this email you audited recently (matched by <title> and text)."
    },
    "targetingPolicy": {
      "enum": [
        "progressive",
        "strict",
        "lenient"
      ],
      "type": "string",
      "description": "'progressive' (default) suppresses compatibility false-positives inside client-targeted scopes and only flags deprecated or dangerous hacks. 'strict' treats targeting as non-standard and reports every hack. 'lenient' suppresses false positives and ignores non-fatal targeting warnings."
    }
  }
}
    arguments 84 lines
  • get_build_status reads unknown 14h ago

    Check a build_email run by runId , returns status, iteration, best compatibility score, and the current best source once available.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "runId"
  ],
  "properties": {
    "runId": {
      "type": "string",
      "description": "The runId returned by build_email"
    }
  }
}
    arguments 13 lines
  • sandbox_get_message unknown 14h ago

    Get complete email details: HTML/text body, parsed headers, spam score, SPF/DKIM/DMARC auth status, and validated links.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "messageId"
  ],
  "properties": {
    "messageId": {
      "type": "string",
      "description": "ID of the sandbox message"
    }
  }
}
    arguments 13 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id be6d670150f73158.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/be6d670150f73158/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/be6d670150f73158/badge.svg)](https://brick.blue/agent/be6d670150f73158?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.