mcpbeat Sign in

Sitewalk MCP Server

by adityaarsharma-audit Your server? Claim it
answering

Sitewalk is answering right now. Last checked 6 min ago. It exposes 3 tools.

Technical SEO audits from ChatGPT or the web: health score, prioritised fixes, CSV and PDF reports.

Uptime history 5 days of history
5 days agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
33 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 6

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 4 November 2026. No other catalogue keeps this.

7 Nov a tool description was rewritten get_audit_status
4 Nov a tool description was rewritten4 times that day start_site_audit
4 Nov a tool changed the parameters it asks for start_site_audit
and 3 more, back to 4 November 2026

Nothing serious here today

Today is the operative word: we check Sitewalk every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

run in your terminal
claude mcp add sitewalk --transport http https://audit.adityaarsharma.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://audit.adityaarsharma.com/mcp
~/.codex/config.toml
[mcp_servers.sitewalk]
url = "https://audit.adityaarsharma.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "sitewalk": {
      "url": "https://audit.adityaarsharma.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "sitewalk": {
      "type": "http",
      "url": "https://audit.adityaarsharma.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

audit
get_audit_report
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.
get_audit_status
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. A big audit can take 20 to 60 minutes, so keep calling for as long as the status is running or queued. When completed it also returns report_url, pdf_url and csv_url.
start
start_site_audit
Use this when the user asks for a technical SEO audit, a site crawl or an SEO health check of a website, or for broken links, redirect chains, duplicate or missing titles and meta descriptions, canonical, noindex or hreflang problems, sitemap errors, pages that are hard to find from the home page, or whether robots.txt or meta robots tags keep search engines out of pages. 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 takes a few minutes for a small site and longer for a large one. 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. Do not use it for backlinks, keyword rankings, Google Search Console or analytics data, or writing content: Sitewalk does not measure those. Optional render_scripts (true or false, default false): set it to true only when the user asks for the pages to be read after their scripts have run, as a browser shows them. The server decides whether that is possible for this site and says in the result how the pages were read; report that line as given. Leave it out otherwise. To read a finished audit, use get_audit_report instead.

Endpoints

URLTransportStateLatencyChecked
https://audit.adityaarsharma.com/mcp streamable-http answering 22 ms 6 min ago

Alternatives to Sitewalk

same job, measured the same way
Crawlie
by crawlie

Technical SEO + GEO (AI-search) site audits: hosted crawls, prioritized fixes, report diffs.

answering
SEOReport
by seoreport

Run full technical SEO audits of any website from your AI agent and get structured findings back.

answering
SeoAiX SEO Audit
by seoaix

Free SEO & AI-search (AEO) audits for any site or Shopify store, with emailed weekly score reports.

12 tools answering
S
Speedvault
by speedvault

Run web performance audits, get code-level fixes, crawl for SEO, and read real-user Core Web Vitals.

49 installs/wk local only
Persqo
by persqo

AI personas test your site like real users and return scored reports with fix prompts.

answering
SecScan
by secscan

Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.

12 tools answering
PaidHelm for Google Ads
by paidhelm

Google Ads reports, audits, negatives, bidding and campaign builds from Claude, ChatGPT or Cursor.

answering
Google CrUX MCP
by a1-x-tech

Real-user Core Web Vitals from the Chrome UX Report (CrUX) API for any origin or URL.

527 installs/wk local only

Sitewalk — questions

Answers built from our own checks of this server.

What can Sitewalk do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_audit_report, get_audit_status, start_site_audit. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Sitewalk working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 33 ms. The bar chart above shows every period we have measured.
How do I connect Sitewalk?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Sitewalk need an API key?
No. Sitewalk completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Sitewalk?
It answers our handshake in 33 ms on average, which is faster than 99% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.