MailDignity

npx add-mcp 'https://maildignity.com/mcp'

maildignity.

Playground Pricing Extensions API/MCP docs

Sign in

DOCUMENTATION / V1[ API ]

Human standards.
Machine-readable.

One email in. One structured verdict out.
Built to fit the workflow you already use.

→ Create an API key in your dashboard. Keys start with md_live_. Each call uses one check from your monthly quota.

Request Response Verdicts Integrations Errors & quota

POST /api/public/v1/check

Send the email text with your key in the Authorization header. Optionally add the prospect’s name, company and role.

email_textrequiredThe email to evaluate.

prospectoptionalRecipient name, company and role.

modeoptional"full" (default): verdict, exact snippets and rewrites. "fast": verdict and flagged rules only, for big batches.

A verdict with receipts.

Each issue has an exact snippet, severity, reason and a short rewrite. On REVIEW, repaired_body is the full email with the rewrites applied, ready to send. It is null on PASS and FAIL.

{
  "verdict": "REVIEW",
  "summary": "Friendly, but asks for a fixed call slot.",
  "issues": [
    {
      "rule": "asymmetric_ask",
      "severity": "medium",
      "snippet": "Can we jump on a 30-minute call Tuesday?",
      "reason": "Asks a stranger for a fixed block of time.",
      "rewrite": "Happy to send a short overview if useful."
    }
  ],
  "repaired_body": "Hi Stefan, … Happy to send a short overview if useful."
}

Three verdicts. No drama.

[PASS] Send the original.

[REVIEW] Send repaired_body.

[FAIL] Hold it for a human.

Ten boundaries are checked: asymmetric asks, guilt-trip follow-ups, fake familiarity (including fake “Re:” / “Fwd:”), unsolicited diagnosis, homework, generic flattery, bait and switch, cognitive overload, hostility and privacy intrusion.

Plug it into your stack.

Pick your tool. Every recipe does the same thing: check the draft, then route by verdict.

ClayHTTP API columnMakeHTTP modulen8nHTTP Request nodeZapierWebhooks by ZapierPythonrequestscURLTerminal

1. In your table, add a column → “HTTP API”.
2. Method POST, paste the URL, add the two headers below.
3. In the body, insert your email column with “/”.
4. Map verdict and repaired_body to new columns, then send the right one to Instantly, Smartlead or your sequencer.

Clay

Method: POST
URL: https://maildignity.com/api/public/v1/check

Headers
  Authorization: Bearer md_live_…
  Content-Type: application/json

Body
{
  "email_text": "/Email Draft",
  "mode": "full"
}

Formula column "Email to send"
{{verdict}} == "REVIEW" ? {{repaired_body}} : {{Email Draft}}
(skip rows where verdict is FAIL)

Starting from a webhook (a CRM, a form, Clay’s “Send to webhook”)? Catch it in Make, n8n or Zapier, call MailDignity, then route. The API answers right away, so no callback is needed.

Use it from your AI assistant.

Claude, ChatGPT, Cursor and other MCP clients can check drafts directly. Add a custom connector with this address, then sign in and click Allow. No API key to copy.

https://maildignity.com/mcp

The assistant gets one tool, check_email: verdict, flagged lines and the corrected email. Each check uses one credit from your account and shows up under “AI assistants” in your usage charts. Email text is never stored. You can revoke access anytime from the assistant.

Errors and quota.

200okVerdict returned. X-Checks-Remaining shows checks left this month.

400bad requestMissing or empty email_text.

401unauthorizedMissing, wrong or revoked key.

402quotaMonthly checks used up. Upgrade or wait for the reset.

429rate limitMax 10 requests per second per key. Wait for the Retry-After seconds and retry.

Try a demo audit

maildignity.Less noise. More human.

Documentation Free tools Privacy Terms Support© 2026 MailDignity