_ registry / mcp + a2a streamable-http · checked 1h ago

inboxguard

https://inboxguard.io

Registry code: 760c5aa1f98c8500

api record

InboxGuard tools cover deliverability scanning AND the authenticated product end to end. Deliverability scanning: scan_domain (renders an interactive scorecard ui://inboxguard/scan-result), get_deliverability_score, check_blocklists, analyze_headers (re-verify SPF/DKIM/DMARC/ARC on a raw email), scan_domains_batch + get_scan_job (async batch of up to 50). Every tools/call requires an API-key bearer token — for a keyless one-off scan, POST to the REST endpoint /scan-domain (5/hour per IP). With an API key, scans run at the org's plan tier and auto-track the domain; account tools: list_domains,…

endpoint
https://mcp.inboxguard.io/mcp
door code
92ad8acf571de49e
protocol
streamable-http ·0.3
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 inboxguard live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is inboxguard free to use?
Not anonymously — it asks for a key or a login before it will serve. Whether that key costs anything is the operator's plan to say: the hub measured the door, not the pricing.
What tools does inboxguard have?
2 tools: Scan domain deliverability, Read DMARC aggregate reports.
Is inboxguard 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
99.9%

90 days 99.3%· all time 99.4%

latency
719ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1692 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • degraded → live
_ what it is for
topic
communication email
used for
  • scan a domain for email deliverability
  • check domain blocklists
  • analyze email headers
  • apply dns fixes for email authentication
  • monitor sender reputation
takes → gives
text → data
_ usage and payments 30 days

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.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 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.

  • scan-domain unknown never probed

    Run a full SPF/DKIM/DMARC/MTA-STS/TLS-RPT/BIMI/blocklist scan for a domain and return a 0–100 score with per-check findings.

    emaildeliverabilitydmarcspfdkimdns

  • dmarc-reports unknown never probed

    Summarize ingested DMARC aggregate (RUA) reports by source IP and authentication result.

    dmarcreportingemail

_ try it over a2a 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 760c5aa1f98c8500.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/760c5aa1f98c8500/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/760c5aa1f98c8500/badge.svg)](https://brick.blue/agent/760c5aa1f98c8500?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 knowoff the mcp door
card completeness
100%

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.