Sitewalk

com.adityaarsharma.audit/sitewalkVersion 1.0.0

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

Status

Responds187 msNov 14, 2026, 13:45 UTCAnswered our handshake without sign-in.

Registry data may be out of date

We could not refresh it, so this page shows the last copy.

Last checked: Nov 14, 2026, 13:45 UTC
Latency: 187 ms
Remotes responding: 1 of 1
Sign-in: No sign-in
Hosting: EU hosting detected (detected, not a legal statement)
Registry data as of: Nov 14, 2026, 22:14 UTC

Data from the official MCP Registry, checked by run.zero. How we check

Connect

Streamable HTTP

https://audit.adityaarsharma.com/mcpResponds187 msNov 14, 2026, 13:45 UTC

No sign-in

Claude Code

claude mcp add --transport http sitewalk https://audit.adityaarsharma.com/mcp

Claude Desktop and claude.ai

1
2
3

Settings > Connectors > Add custom connector
Name: sitewalk
Remote MCP server URL: https://audit.adityaarsharma.com/mcp

Cursor

{
  "mcpServers": {
    "sitewalk": {
      "url": "https://audit.adityaarsharma.com/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"sitewalk","type":"http","url":"https://audit.adityaarsharma.com/mcp"}'

Built your own server? run.zero hosts MCP servers on European infrastructure.

Host your own MCP server on run.zero

Tools

6 tools

Tools of Sitewalk
	Description		Read-only	Idempotent	Open world
`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.	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.	No	Yes	Not declared	No
`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.	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.	No	Yes	Not declared	No
`list_monitored_sites`Use this when the user asks which sites Sitewalk is monitoring, how often, or when the next check is. Returns each monitored site, its frequency, whether it is paused and the date of the next check. Needs a signed-in Sitewalk account.	Use this when the user asks which sites Sitewalk is monitoring, how often, or when the next check is. Returns each monitored site, its frequency, whether it is paused and the date of the next check. Needs a signed-in Sitewalk account.	No	Yes	Not declared	No
`monitor_site`Use this when the user wants Sitewalk to keep watching a website: check it regularly, re-audit it every day, week or month, or tell them when something breaks. Takes the site address and an optional frequency: daily, weekly or monthly (default monthly). Sitewalk audits the site again on that schedule and emails the user only when something changed: a different health score, new issues, or the site could not be checked. Asking again for the same site changes its frequency. The result says when the next check runs, or why the frequency is not available and which one is. Needs a signed-in Sitewalk account. Only use it for sites the user owns or is allowed to audit.	Use this when the user wants Sitewalk to keep watching a website: check it regularly, re-audit it every day, week or month, or tell them when something breaks. Takes the site address and an optional frequency: daily, weekly or monthly (default monthly). Sitewalk audits the site again on that schedule and emails the user only when something changed: a different health score, new issues, or the site could not be checked. Asking again for the same site changes its frequency. The result says when the next check runs, or why the frequency is not available and which one is. Needs a signed-in Sitewalk account. Only use it for sites the user owns or is allowed to audit.	Yes	No	Not declared	Yes
`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.	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.	No	No	Not declared	Yes
`stop_monitoring`Use this when the user wants Sitewalk to stop checking a site on a schedule. Takes the site address. Deletes that site's monitoring schedule; past audits and reports stay in the account. Needs a signed-in Sitewalk account.	Use this when the user wants Sitewalk to stop checking a site on a schedule. Takes the site address. Deletes that site's monitoring schedule; past audits and reports stay in the account. Needs a signed-in Sitewalk account.	Yes	No	Not declared	No

Details

Registry status: Active
Published: Nov 3, 2026
Updated: Nov 3, 2026
Website: https://audit.adityaarsharma.com/⁠ (opens in a new tab)
Repository: Not given
Categories (suggested): Data and analyticsSuggested categories are assigned automatically from the registry text and may be wrong. Verified operators can correct them.
GDPR: Not declared

Are you the operator? Claim this listing