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

Sitewalk

https://audit.adityaarsharma.com

Registry code: 8f02b066141d59ec

api record

Sitewalk crawls a public website and reports technical SEO problems, ranked by how much each one is likely to matter. It works only through assistants like you. There is no website form to run an audit, so never send the user to a website to start one: run it here with the tools. The user may be new to SEO and to Sitewalk. Talk to them in plain English, and say in one short line what is happening at every step, so they are never left wondering.

Method:

endpoint
https://audit.adityaarsharma.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 it live, free and safe measured by this hub
Is Sitewalk live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Sitewalk free to use?
Yes — the hub reached it with no key and no payment.
What tools does Sitewalk have?
3 tools: start_site_audit, get_audit_report, get_audit_status.
Is Sitewalk 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
234ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • 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

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 3 tools
3 never probed 0 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.

  • start_site_audit unknown never probed

    Use this when the user asks for a technical SEO audit, a site crawl, or a check for broken links, redirect problems, duplicate or missing titles and meta descriptions, canonical or hreflang errors, sitemap problems, or pages that are hard to find from the home page. Takes a site address (a domain such as example.com or a full URL; the scheme is optional) and starts a crawl of that site, then returns an audit_id, the page limit and a time estimate to relay to the user. The crawl follows robots.txt, is rate limited, and usually takes a few minutes. The number of pages crawled is capped; the report says when the cap was reached. If the address redirects (http to https, or to www), the final site is audited. Only use it for sites the user owns or is allowed to audit.

    mcp-tool

    {
      "type": "object",
      "title": "start_site_auditArguments",
      "required": [
        "url"
      ],
      "properties": {
        "url": {
          "type": "string",
          "title": "Url"
        }
      }
    }
    arguments 13 lines
  • get_audit_report unknown 1h ago

    Use this once get_audit_status shows completed. Takes the audit_id and an optional top_n (1 to 25, default 10). Returns the issues ranked by likely impact, each with the number of affected pages, example URLs and a plain-English fix, plus a list of what was checked, what was not checked, and a note when the page limit was reached, and the full_report_url, pdf_url and csv_url links. Report the issues as given; do not add findings that are not in the result.

    mcp-tool

    {
      "type": "object",
      "title": "get_audit_reportArguments",
      "required": [
        "audit_id"
      ],
      "properties": {
        "top_n": {
          "type": "integer",
          "title": "Top N",
          "default": 10
        },
        "audit_id": {
          "type": "string",
          "title": "Audit Id"
        }
      }
    }
    arguments 18 lines
  • get_audit_status unknown 1h ago

    Use this after start_site_audit to check whether the audit has finished. Takes the audit_id. Returns status (queued, running, completed, failed or canceled), pages crawled so far, the page limit, and any notes or error text. If the status is failed, the error field says why (for example the site blocked the crawler or robots.txt disallows it). Also returns phase, a plain-English message with the stage, pages crawled and time left, progress_pct, stalled and next_check_after_s. After each call, show the user the message, then call again after next_check_after_s seconds (20 to 30) until the status is completed, failed or canceled. When completed it also returns report_url, pdf_url and csv_url.

    mcp-tool

    {
      "type": "object",
      "title": "get_audit_statusArguments",
      "required": [
        "audit_id"
      ],
      "properties": {
        "audit_id": {
          "type": "string",
          "title": "Audit Id"
        }
      }
    }
    arguments 13 lines
_ try it 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 8f02b066141d59ec.

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

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.