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

Black Water Window Cleaning Public Site Directory

https://blackwaterwindowcleaning.com

Registry code: dbe829da8b53a9da

api record

Residential and commercial window cleaning across Gulf Shores, Orange Beach, Foley, Elberta, and Pensacola. Text or upload photos for an owner-reviewed written estimate.

endpoint
https://blackwaterwindowcleaning.com/mcp
door code
7de6dd65d3c9cdab
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 Black Water Window Cleaning Public Site Directory live?
Yes — it answered the hub's last check (checked 6h ago). It answered 95% of checks over the last 30 days.
Is Black Water Window Cleaning Public Site Directory free to use?
Yes — the hub reached it with no key and no payment.
What tools does Black Water Window Cleaning Public Site Directory have?
3 tools: search_pages, read_page, site_info.
Is Black Water Window Cleaning Public Site Directory 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
94.6%

90 days 98.5%· all time 98.5%

latency
123ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 805 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
knowledge & reference documentation & docs search
used for
  • search a window cleaning company's pages
  • read a website page as markdown
  • get company site information
takes → gives
text → web pages, 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 3 tools
1 open 2 never probed 1 of 3 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.

  • site_info open 28d ago

    What Black Water Window Cleaning (blackwaterwindowcleaning.com) is, with links to its sitemap, docs, contact and every discovery document.

    mcp-tool

    {
  "type": "object",
  "properties": {},
  "additionalProperties": false
}
    arguments 5 lines
  • search_pages unknown 28d ago

    Find pages on blackwaterwindowcleaning.com by words in their URL path (sitemap search). Returns URLs with a match score.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20,
      "maximum": 50,
      "minimum": 1
    },
    "query": {
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 18 lines
  • read_page unknown 28d ago

    Read one https://blackwaterwindowcleaning.com page as Markdown (Cloudflare Markdown for Agents) or stripped text, up to 40,000 characters.

    mcp-tool

    {
  "type": "object",
  "required": [
    "url"
  ],
  "properties": {
    "url": {
      "type": "string",
      "format": "uri"
    }
  },
  "additionalProperties": false
}
    arguments 13 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 agent card — 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 dbe829da8b53a9da.

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

How much of the published card is filled in. Not a judgement of the agent — a measure of what it told the world about itself.

spec deviations
1

Places where the published card departs from the specification. Recorded rather than hidden, and counted against every agent the same way.

  • no usable endpoint declared
_ 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.