mcpbeat Sign in

Stamp MCP Server

by clawhard Your server? Claim it
answering

Stamp is answering right now. Last checked 12 min ago. It exposes 2 tools.

Check a domain's SPF, DKIM, DMARC and MX from live DNS, the Gmail/Yahoo rules, and fix records.

Uptime history 63 hours of history
63 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
115 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Stamp every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 12 min ago.

run in your terminal
claude mcp add stamp --transport http https://stamp.clawhard.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://stamp.clawhard.com/mcp
~/.codex/config.toml
[mcp_servers.stamp]
url = "https://stamp.clawhard.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "stamp": {
      "url": "https://stamp.clawhard.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "stamp": {
      "type": "http",
      "url": "https://stamp.clawhard.com/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

stamp
stamp_check_dns_record
Use when you or the user are about to publish or edit an SPF, DMARC or DKIM TXT record, for example after writing a new SPF record that adds a sending service, or when the user pastes a record and asks "is this right?". Detects the record type. SPF: syntax per RFC 7208, every include and redirect followed live in DNS and counted against the 10-lookup limit, void lookups, loops, the final all; returns a lookup tree. DMARC: RFC 7489 tags and values (p, sp, pct, rua/ruf, adkim/aspf, fo). DKIM: key type and RSA key size read from the key, revoked (empty p=) or truncated keys. Returns valid true/false, errors, warnings and where to publish it. Pass domain so a/mx terms without a value can be resolved.
stamp_check_email_domain
Use when the user asks why their email goes to spam, whether their domain is set up to send email, or before they launch a newsletter, cold outreach, transactional email or a new sending service, e.g. "why are my emails going to spam?", "is my SPF/DKIM/DMARC right?", "do I meet Gmail and Yahoo's sender requirements?" or "I added SendGrid, did I break SPF?". Reads public DNS (DNS-over-HTTPS) and checks: SPF (exactly one record, every include followed and DNS lookups counted per RFC 7208 against the limit of 10, void lookups, loops, +all/?all, ptr), DMARC (RFC 7489 syntax, policy, pct, alignment, inherited from the parent domain, and whether an external report address authorized it), DKIM (17 common selectors plus any you pass; key type and RSA key size read from the key, revoked or broken keys), and MX (provider, null MX). Returns a grade A-F, a verdict, each check with status pass/warn/fail/info, whether the Gmail, Yahoo and Outlook.com sender rules are met, and copy-ready DNS records to fix problems (e.g. one merged SPF record, a starter DMARC record). Use the real result instead of guessing from memory; DNS cannot list DKIM selectors, so if none is found ask for the provider's selector (the s= value in a DKIM-Signature header) and check again. Accepts a domain, an email address or a URL. Results are cached for 5 minutes; pass fresh=true right after the user changes DNS.

Endpoints

URLTransportStateLatencyChecked
https://stamp.clawhard.com/mcp streamable-http answering 91 ms 12 min ago

Alternatives to Stamp

same job, measured the same way
ARC-Relay Email
by arc-relay

Checks any domain's DMARC, SPF, MX and DKIM setup, scores it 0-100, and ranks the fixes.

6 tools answering
MX Verdict
by mxverdict

Free, read-only email and DNS checks: SPF, DKIM, DMARC, MX, DNS records, blocklists, domain health.

7 tools answering
Email Deliverability Checker
by kryptoscan

Check SPF, DKIM, DMARC, blocklists, reverse DNS and email headers against Gmail/Yahoo sender rules.

3 tools answering
MailVakt
by mailvakt

Use when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it.

8 tools answering
Deliverability Doctor
by integrity-os

Check if a domain can be email-spoofed: SPF, DMARC, DKIM, MX graded from public DNS. Authless.

2 tools answering
DnsGuard
by workers-mike-tusa-dnsguard

Check a domain's email authentication: SPF, DKIM, DMARC, BIMI, MX, MTA-STS, TLS-RPT. Score + fixes.

1 tools answering
DNS Lookup — Bulk SPF, DKIM, DMARC & Mail Policy Findings
by kriton-dev

Check DNS records and email authentication (SPF, DKIM, DMARC) for domains, as findings by severity

answering
Email Deliverability
by inboxguard

Scan and fix a domain's email deliverability (SPF, DKIM, DMARC, MTA-STS, BIMI, DNS blocklists).

28 tools answering

Stamp — questions

Answers built from our own checks of this server.

What can Stamp do?
It exposes 2 tools, read directly from the server on our last check. Among them: stamp_check_dns_record, stamp_check_email_domain. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Stamp working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 115 ms. The bar chart above shows every period we have measured.
How do I connect Stamp?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Stamp need an API key?
No. Stamp completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Stamp?
It answers our handshake in 115 ms on average, which is faster than 90% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.