_ registry / mcp http-sse · checked 1h ago

mailsecuritytools

https://api.mailsecuritytools.com

Registry code: 876d375b40d49af8

api record

Mail Security Tools: check a domain's email security. check_domain_email_security (free) returns MX, SPF, DMARC and DKIM. email_security_score ($0.01) grades it 0-100. email_fix_plan ($1) returns the exact DNS records to publish. check_email_address ($0.01) checks one address. Payment is x402 USDC on Base in _meta['x402/payment']; invalid or failed calls are not charged. Daily monitoring: InboxGuards (inboxguards.com).

endpoint
https://api.mailsecuritytools.com/mcp
protocol
http-sse ·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 it live, free and safe measured by this hub
Is mailsecuritytools live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mailsecuritytools free to use?
Yes — the hub reached it with no key and no payment.
What tools does mailsecuritytools have?
5 tools: check_domain_email_security, email_security_score, check_email_address, email_fix_plan, pricing.
Is mailsecuritytools 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.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
351ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address also stands behind 9 other origins: the chain figures are the gateway's, not this listing's alone. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
3

distinct

settlements
64

last 2026-10-14

received on chain
1.905 USDC

concentrated, shared-payto

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

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.

  • pricing open 1h ago

    Free. Prices of the paid tools, payment network and receiving address.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {}
}
    arguments 5 lines
  • check_domain_email_security unknown never probed

    Free. Look up a domain's MX, SPF (record, DNS lookup count, all qualifier), DMARC (policy, rua) and DKIM (common selectors, key size) from live DNS and list issues. No payment.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 320,
      "minLength": 3,
      "description": "Domain, e.g. example.com (an email or URL on it also works)"
    }
  }
}
    arguments 15 lines
  • email_security_score unknown never probed

    Grade a domain's email security 0-100 (A-F): SPF 30, DMARC 40, DKIM 25, MX 5, from live DNS, with findings and the top 3 fixes. Read-only. Costs $0.01 USDC via x402; errors are not charged.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 320,
      "minLength": 3,
      "description": "Domain, e.g. example.com (an email or URL on it also works)"
    }
  }
}
    arguments 15 lines
  • check_email_address unknown never probed

    Check one email address: syntax, MX / null MX, disposable domain, role account, free provider; verdict ok / risky / undeliverable. No SMTP probe. Costs $0.01 USDC via x402; errors are not charged.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "email"
  ],
  "properties": {
    "email": {
      "type": "string",
      "maxLength": 320,
      "minLength": 3,
      "description": "Email address"
    }
  }
}
    arguments 15 lines
  • email_fix_plan unknown never probed

    Email security fix plan for one domain: the exact SPF, DKIM and DMARC records to publish (create / replace / keep, name, value, why), in order, with click-path steps for the domain's DNS host and a staged DMARC rollout. Non-sending domains get a lock-down set. Costs $1 USDC via x402; errors are not charged.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "domain"
  ],
  "properties": {
    "domain": {
      "type": "string",
      "maxLength": 320,
      "minLength": 3,
      "description": "Domain, e.g. example.com (an email or URL on it also works)"
    }
  }
}
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 876d375b40d49af8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/876d375b40d49af8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/876d375b40d49af8/badge.svg)](https://brick.blue/agent/876d375b40d49af8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

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

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

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