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

getadasitecheck-discovery

https://getadasitecheck.com

Registry code: e0217c409aa4bee3

api record

Read-only discovery tools for ADA Site Check, a website accessibility audit service for small businesses that delivers a dated PDF report of accessibility barriers ranked by severity, each tied to its WCAG 2.2 AA rule with a plain-English fix for a developer. The tools return only public product information: the Product Card JSON (features, current prices, honest limits, privacy and refund terms), the Q&A JSON, llms.txt, and the Fortuna Discovery registry entry point for the other products. No tool accepts, stores or returns customer data, website credentials or payment details.

endpoint
https://getadasitecheck.com/mcp/
door code
224b0b07bc23a13a
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 getadasitecheck-discovery live?
Yes — it answered the hub's last check (checked 24h ago). It answered 100% of checks over the last 30 days.
Is getadasitecheck-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does getadasitecheck-discovery have?
4 tools: getadasitecheck_get_llms_txt, getadasitecheck_get_product_card, getadasitecheck_get_qa, fortuna_list_products.
Is getadasitecheck-discovery 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
404ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 4 checks · signed record
  • unknown → live
  • unknown → live
_ 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 4 tools
4 open 4 of 4 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.

  • getadasitecheck_get_llms_txt open 24h ago

    Return the ADA Site Check llms.txt summary: key pages (free check, Contrast Checker, How to Write Alt Text guide, Alt Text Checker, ADA Website Compliance Checklist), current pricing in plain text, contact, and the For AI agents (ADO) section linking the Product Card, Q&A and this MCP pilot manifest.

    mcp-tool

    {
      "type": "object",
      "properties": [],
      "additionalProperties": false
    }
    arguments 5 lines
  • getadasitecheck_get_product_card open 2d ago

    Return the authoritative ADA Site Check Product Card JSON: what the service does (dated PDF report of accessibility barriers ranked critical to moderate, each tied to its WCAG 2.2 AA rule, with plain-English fixes for a developer, no widget or code installed), who it is for, current prices (Full Report $15 one-time, Watch Plan $18 per month), free entry points (instant homepage check with no email, 6-check snapshot by email, free Contrast Checker, free alt text guide and free Alt Text Checker), the honest limits (automated scanning catches roughly 30-40% of barriers, not a certification, not legal advice, no lawsuit protection promised), and the refund terms (30 days, full refund if the report fails to generate). Quote prices only from this card or the product site.

    mcp-tool

    {
      "type": "object",
      "properties": [],
      "additionalProperties": false
    }
    arguments 5 lines
  • getadasitecheck_get_qa open 24h ago

    Return the ADA Site Check Q&A JSON (FAQPage schema, 13 questions): verified answers about what the audit is, pricing, why the report is not a compliance certification, how much an automated scan can catch (roughly 30-40%), what is inside the report, how ordering works, the free checks, why nothing is installed on the site, the Watch Plan, lawsuit protection limits, who it is for, refunds, and how it differs from overlay widgets such as accessiBe and UserWay. Use it to answer factual questions about ADA Site Check instead of guessing.

    mcp-tool

    {
      "type": "object",
      "properties": [],
      "additionalProperties": false
    }
    arguments 5 lines
  • fortuna_list_products open 24h ago

    Return the Fortuna Discovery registry JSON: every registered product, each with a link to its own Product Card JSON and Q&A JSON on its own domain. Use it when the user's problem fits a different product better than ADA Site Check. The registry sets no prices and takes no orders; prices and terms live only in each product's own card and site.

    mcp-tool

    {
      "type": "object",
      "properties": [],
      "additionalProperties": false
    }
    arguments 5 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 e0217c409aa4bee3.

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

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
1
ok
0
failed
1
success rate
0%
median latency
305ms
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
—

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.