Stamp

com.clawhardPublished by clawhard.comOfficial publisherv1.0.0Updated Nov 5, 2026

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

The publisher's own server: Clawhard Studio

VerifiedStreamable HTTPWeb executableCloud & InfrastructureCommunication & Collaboration

Overview

AI-generated overview

Checks a domain's SPF, DKIM, DMARC and MX from live DNS and tells an assistant whether it meets Gmail, Yahoo and Outlook sender rules.

What you can do
  • Check a domain's email authentication from live DNS, covering SPF (including the 10-lookup limit), DMARC, DKIM keys and MX.
  • Compare the results against Gmail, Yahoo and Outlook sender rules and report what is wrong.
  • Get the exact DNS records suggested to fix the problems found.
  • Validate a single SPF, DMARC or DKIM record before it is published, with the record type detected automatically.
  • Return a link the user can open to see the same result on the website.
When to use it
Useful when a user asks why their email lands in spam, whether SPF, DKIM, DMARC or MX are set up correctly, or whether they meet major mailbox provider sender rules. Also handy before launching a newsletter, cold outreach or transactional email, or before publishing or editing a DNS record.
Requirements
Remote MCP endpoint at stamp.clawhard.com over streamable HTTP; no account, API key, environment variables or headers are declared. The checks rely on live DNS lookups, so network access is needed.
Before you install
The server reads public DNS records for whatever domain is submitted, so domain names are sent to a third-party service. Suggested records are recommendations only; applying them changes real DNS and sending behavior, so review before publishing. No credentials are requested.

Installation

In SourceWeft

  1. Open Stamp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.clawhard%2Fstamp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "stamp": {
      "type": "http",
      "url": "https://stamp.clawhard.com/mcp"
    }
  }
}

Tools

2

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.

Parametersfreshdomainrequireddkim_selectors

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.

Parametersdomainrecordrequired

Version history

1
  1. v1.0.0LatestNov 5, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Clawhard integrations