com.clawhard/stamp

endpoint

https://stamp.clawhard.com/mcp

door code

ce4be8836975153d

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 com.clawhard/stamp live?

Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.

Is com.clawhard/stamp free to use?

Yes — the hub reached it with no key and no payment.

What tools does com.clawhard/stamp have?

2 tools: stamp_check_email_domain, stamp_check_dns_record.

Is com.clawhard/stamp 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.

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.

• stamp_check_email_domain unknown never probed

  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.

  mcp-tool

  12345678910111213141516171819202122232425262728

  {
    "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 ([email protected]) 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."
      }
    }
  }

  arguments 28 lines copy
• stamp_check_dns_record unknown 2h ago

  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.

  mcp-tool

  1234567891011121314151617181920

  {
    "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:[email protected]\". Quoted chunks (\"...\" \"...\") are joined."
      }
    }
  }

  arguments 20 lines copy

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

1 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.

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

• mcp.clawhard.com com.clawhard/studio mcp · 30 tools
• clawhard.com com.clawhard/studio mcp · 28 tools
• swatch.clawhard.com com.clawhard/swatch mcp · 6 tools
• mend.clawhard.com com.clawhard/mend mcp · 4 tools
• meridian.clawhard.com com.clawhard/meridian mcp · 4 tools
• doorman.clawhard.com com.clawhard/doorman mcp · 3 tools
• aitab.clawhard.com com.clawhard/aitab mcp · 2 tools
• deadbolt.clawhard.com com.clawhard/deadbolt mcp · 2 tools

8 more sit on this domain. All of them.