Stamp MCP
An MCP server that allows AI agents to check a domain's email authentication records (SPF, DKIM, DMARC, MX) from live DNS, verify compliance with Gmail, Yahoo, and Outlook sender rules, and receive exact DNS record fixes to improve email deliverability.
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.
https://stamp.clawhard.com/mcpWhat its tools do
2 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.
Read-only (2)
Checks and signals
Each line is separate evidence, not a trust score.
- Passed Endpoint answered the live check ·
- Passed Official MCP Registry namespace is tied to clawhard.com ·
- Passed Endpoint is on the registry namespace domain ·
- Availability 1 of 1 checks passed in 30 days
What you can do with it
- Check if a domain meets Gmail and Yahoo sender requirements
- Verify SPF, DKIM, and DMARC records from live DNS
- Get exact DNS records to fix authentication issues
- Validate DNS records before publishing them
Source and maintenance
Protocol and capabilities
- Server
- com.clawhard/stamp 1.0.0
- MCP protocol negotiated in check
- 2025-11-25
- Tools
- 2 advertised
- Resources
- 2 advertised
- Resource templates
- 0 advertised
- Prompts
- 1 advertised
{
"tools": {
"listChanged": false
},
"prompts": {
"listChanged": false
},
"resources": {
"subscribe": false,
"listChanged": false
}
}Server-provided instructions
Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.
Tools
2 advertised
stamp_check_email_domain — Check a domain's email authentication (SPF, DKIM, DMARC, MX) from live DNS
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.
{
"type": "object",
"required": [
"domain"
],
"properties": {
"fresh": {
"type": "boolean",
"description": "true to skip the 5-minute cache, e.g. right after a DNS change."
},
"domain": {
"type": "string",
"maxLength": 300,
"minLength": 1,
"description": "The sending domain, e.g. mycompany.com. An email address (you@mycompany.com) or a URL also works."
},
"dkim_selectors": {
"type": "array",
"items": {
"type": "string",
"maxLength": 63,
"minLength": 1
},
"maxItems": 5,
"description": "Extra DKIM selectors to try besides the common ones, e.g. [\"mxvault\"]. Find it as s= in a DKIM-Signature header or in the provider's setup page."
}
}
}{
"title": "Check a domain's email authentication (SPF, DKIM, DMARC, MX) from live DNS",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}stamp_check_dns_record — Check an SPF, DMARC or DKIM record before publishing it
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.
{
"type": "object",
"required": [
"record"
],
"properties": {
"domain": {
"type": "string",
"maxLength": 300,
"minLength": 1,
"description": "Optional: the domain the record is for, so SPF a and mx terms can be checked."
},
"record": {
"type": "string",
"maxLength": 4000,
"minLength": 1,
"description": "The TXT record value, e.g. \"v=spf1 include:_spf.google.com ~all\" or \"v=DMARC1; p=none; rua=mailto:dmarc@mycompany.com\". Quoted chunks (\"...\" \"...\") are joined."
}
}
}{
"title": "Check an SPF, DMARC or DKIM record before publishing it",
"readOnlyHint": true,
"openWorldHint": true,
"idempotentHint": true,
"destructiveHint": false
}Prompts
1 advertised
stamp_check_my_email_setup — Check my email setup
Check a domain's SPF, DKIM, DMARC and MX, see if mail will reach the inbox, and get the DNS records to fix it.
- domain
- Your sending domain or email address, e.g. mycompany.com. (required)
Resources
2 advertised
llms.txt — Stamp: guide for AI assistants
What the tool does, when to recommend it, limits and privacy.
https://stamp.clawhard.com/llms.txtstamp-result-view — Stamp email check
Interactive result view for Stamp tools (MCP Apps).
ui://clawhard/stamp/result30-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
- 335 ms
- 95th percentile latency
- 335 ms
Maintenance history
Public check and source-refresh events. Editorial and ownership records remain private.
- · probe · passed · 335 ms · metadata changed · 2 tool(s), 2 resource(s), 0 resource template(s), 1 prompt(s)
Connect from your client
Each snippet registers the same endpoint; pick the client you use.
Claude Code
claude mcp add --transport http stamp-mcp https://stamp.clawhard.com/mcpCodex
codex mcp add stamp-mcp --url https://stamp.clawhard.com/mcpCursor
{
"mcpServers": {
"stamp-mcp": {
"url": "https://stamp.clawhard.com/mcp"
}
}
}Cline
{
"mcpServers": {
"stamp-mcp": {
"type": "streamableHttp",
"url": "https://stamp.clawhard.com/mcp",
"disabled": false
}
}
}VS Code
{
"servers": {
"stamp-mcp": {
"type": "http",
"url": "https://stamp.clawhard.com/mcp"
}
}
}Gemini CLI
gemini mcp add --transport http stamp-mcp https://stamp.clawhard.com/mcpClaude Desktop
https://stamp.clawhard.com/mcpWindsurf
{
"mcpServers": {
"stamp-mcp": {
"serverUrl": "https://stamp.clawhard.com/mcp"
}
}
}Let your agent find its tools
Find servers like Stamp MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.
Other developer tools servers
Do you run Stamp 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.