postbox-tools
https://mcp.postboxservices.com
Registry code: 216e7af1a33c2091
Free email deliverability and security checks by Postbox Services: check whether a domain or IP is on an email blacklist (DNSBL), grade a domain's spoofing/BEC exposure (SPF, DKIM, DMARC), trace a URL's redirect chain, run a full deliverability/spam test on a real message, analyze a raw .eml, look up domain age and WHOIS, check a domain's BIMI record and logo, and grade a website's AI discoverability (robots.txt access for AI crawlers, sitemap, llms.txt). Each tool checks the exact target given and returns structured results plus a link to the full web report.
- endpoint
- https://mcp.postboxservices.com/mcp
- 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 postbox-tools live?
- Yes — it answered the hub's last check (checked 3h ago). It answered 100% of checks over the last 30 days.
- Is postbox-tools free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does postbox-tools have?
- 10 tools: create_mailtest, get_domain_age, check_ai_discoverability, check_bimi, trace_redirect, analyze_eml, whois_lookup, check_spoofability, ….
- Is postbox-tools 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.
90 days 99.7%· all time 99.7%
last good check
of 10 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- topic
- communication email
- used for
- check a domain against email blacklists
- grade domain spoofing exposure
- run an email deliverability test
- trace a url redirect chain
- look up domain whois and age
- takes → gives
- text → data
- tools
- 7 reads1 changes data
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
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.
create_mailtest changes data unknown never probed
Create a disposable test address for a full email deliverability audit (score /10: SPF, DKIM, DMARC + alignment, blacklists, reverse DNS, SpamAssassin content, Gmail/Yahoo bulk-sender compliance). The USER must then send an email from the system they want to test to the returned address, after which get_mailtest_result returns the score.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "properties": {} }arguments 5 linesget_domain_age reads unknown 13h ago
Get a domain's registration date and age (young domains have weak sending reputation).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "description": "Domain, e.g. example.com" } }, "additionalProperties": false }arguments 14 linescheck_ai_discoverability unknown 3h ago
Grade how discoverable a website is to AI answer engines (ChatGPT search, Perplexity, Claude, Google AI Overviews, Copilot and others) from its public files: robots.txt access for each major AI crawler (answer-engine vs training), sitemap.xml, plus llms.txt and ai.txt as informational signals. Returns an A-F grade, per-crawler access and findings.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "description": "Website domain to grade, e.g. example.com" } }, "additionalProperties": false }arguments 14 linescheck_bimi unknown 3h ago
Check a domain's BIMI setup: looks up the default._bimi TXT record, fetches the logo it points to (l=) and validates the SVG against the BIMI SVG Tiny Portable/Secure profile, and reports whether a certificate (a=, VMC or CMC) is referenced. Does not verify the certificate itself or the DMARC policy (BIMI also needs DMARC at enforcement - use check_spoofability for that).
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "description": "Domain to check, e.g. example.com" } }, "additionalProperties": false }arguments 14 linestrace_redirect reads unknown 3h ago
Follow a URL server-side through every HTTP redirect hop to its real final destination - per-hop status, IP, TLS and timing, plus phishing/deliverability flags (cross-domain jumps, https downgrades, meta/JS redirects). Fetching is SSRF-hardened (private ranges blocked, HTTPS-only, per-hop validation); how it works: https://redirect.postboxservices.com/
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "url" ], "properties": { "url": { "type": "string", "description": "Absolute http:// or https:// URL to trace" } }, "additionalProperties": false }arguments 14 linesanalyze_eml reads unknown 18h ago
Run a deliverability/content analysis on a raw RFC 822 email (.eml source: full headers + body). IMPORTANT LIMITS: with no live SMTP session, SPF, blacklist and reverse-DNS cannot be verified from a file - for the authoritative score use create_mailtest instead.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "eml" ], "properties": { "eml": { "type": "string", "description": "The complete raw email source (headers + body), as exported via \"Show original\" / \"Download message\"" } }, "additionalProperties": false }arguments 14 lineswhois_lookup reads unknown 18h ago
WHOIS summary for a domain: registrar, created/updated/expires dates, nameservers, DNSSEC, status flags.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "description": "Domain, e.g. example.com" } }, "additionalProperties": false }arguments 14 linescheck_spoofability reads unknown 13h ago
Grade how exposed a domain is to email spoofing and business email compromise, from its public DNS (SPF, DMARC policy strength, alignment, live lookalike domains). Returns an A-F grade with findings.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "domain" ], "properties": { "domain": { "type": "string", "description": "Domain to grade, e.g. example.com" } }, "additionalProperties": false }arguments 14 linescheck_blacklist reads unknown 18h ago
Check a domain against domain blacklists (Spamhaus DBL, SURBL, URIBL and others), or an IP address against 24 IP blacklists including Spamhaus ZEN, Barracuda and SpamCop. Checks the exact target given: domains are not resolved to IPs. Returns per-list listing status.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "target" ], "properties": { "target": { "type": "string", "description": "IPv4 address (checked against IP blacklists) or domain (checked against domain blacklists)" } }, "additionalProperties": false }arguments 14 linesget_mailtest_result reads unknown 13h ago
Fetch the score and breakdown of a mail test created with create_mailtest, once the user has sent their email to the disposable address.
{ "type": "object", "$schema": "http://json-schema.org/draft-07/schema#", "required": [ "id" ], "properties": { "id": { "type": "string", "description": "The test id returned by create_mailtest" } }, "additionalProperties": false }arguments 14 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id216e7af1a33c2091.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/216e7af1a33c2091/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/216e7af1a33c2091?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 1
- ok
- 1
- failed
- 0
- success rate
- 100%
- median latency
- 3,252ms
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
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.