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

Domain Impact Analyzer

https://impact.webmesh.ai

Registry code: 7abc6a373383e302

api record

Scores domains for disruption and impact before they are removed from DNS resolution, rating each one's technical blast radius.

endpoint
https://impact.webmesh.ai/mcp
door code
1378f432bf360e9c
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 it live, free and safe measured by this hub
Is Domain Impact Analyzer live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is Domain Impact Analyzer free to use?
Yes — the hub reached it with no key and no payment.
What tools does Domain Impact Analyzer have?
1 tool: analyze_domain_impact.
Is Domain Impact Analyzer 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
98.9%

90 days 98.9%· all time 98.9%

latency
627ms

last good check

priced tools
0

of 1 tools

_ answered our checks, 90 days 906 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
infrastructure & devops dns & networking
used for
  • score domains before removing them from dns
  • assess disruption of blocking a domain
takes → gives
text → data
tools
1 reads
_ 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

inferred, not observed

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

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

  • analyze_domain_impact reads unknown 8h ago

    Score domains for impact before removing them from DNS resolution. Rates each domain on disruption (technical blast radius) and news (social velocity), 1-10, and buckets them: DO NOT TOUCH (5+), MANAGEMENT APPROVAL (3-4), STANDARD PROCESSING (1-2). Use before ServerHold/ClientHold, registry actions, or abuse takedowns. Args: domains: real registrable FQDNs to analyze, e.g. ["shopify.com", "zoom.us"] (max 20 per call). Send actual domains an operator might act on — not reserved placeholders like example.com, which carry no real blast radius. include_what_breaks: Include a concrete consequence line per domain.

    mcp-tool

    {
  "type": "object",
  "title": "analyze_domain_impactArguments",
  "required": [
    "domains"
  ],
  "properties": {
    "domains": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "title": "Domains"
    },
    "include_what_breaks": {
      "type": "boolean",
      "title": "Include What Breaks",
      "default": true
    }
  }
}
    arguments 21 lines
_ try it over mcp 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 7abc6a373383e302.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/7abc6a373383e302/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/7abc6a373383e302/badge.svg)](https://brick.blue/agent/7abc6a373383e302?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
50%

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.

_ also on webmesh.ai 10 entries

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.

2 more sit on this domain. All of them.