Skip to content

Sitewalk MCP server

com.adityaarsharma.audit/sitewalkaudit.adityaarsharma.comstreamable-httpv1.0.1Scanned

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

6 tools: 2 can delete or cancel things, 1 change things and 3 only read.

Tools: 2 delete, 0 irreversible, 1 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Sitewalk MCP server can do

The Sitewalk MCP server is published by audit.adityaarsharma.com, a domain the MCP Registry verified. It has 6 tools. It can delete or cancel things (2 tools: monitor_site and stop_monitoring) and create or change data (1 tool: start_site_audit). 3 tools only read.

2 tools bring in text other people can write (start_site_audit and monitor_site); 1 tool can send data out of your system (start_site_audit).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Deletes or cancels 2Claude Code: deny
  • monitor_siteUse 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: true
  • stop_monitoringUse this when the user wants Sitewalk to stop checking a site on a schedule.No findings

    Why it is in this group

    • The name "stop_monitoring" says "stop": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • openWorldHint: false
Changes things 1Claude Code: ask
  • start_site_auditUse 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 …Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "start_site_audit" says "start": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "crawl": it reads web pages, which anyone can write.
    • outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: true
Only reads 3Show 3 read-only tools
  • get_audit_reportUse this once get_audit_status shows completed.No findings

    Why it is in this group

    • The name "get_audit_report" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_audit_statusUse this after start_site_audit to check whether the audit has finished.No findings

    Why it is in this group

    • The name "get_audit_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • list_monitored_sitesUse this when the user asks which sites Sitewalk is monitoring, how often, or when the next check is.No findings

    Why it is in this group

    • The name "list_monitored_sites" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:22 UTC, unchanged since Nov 18, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://audit.adityaarsharma.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://audit.adityaarsharma.com/
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (2 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://audit.adityaarsharma.com/mcp: tools/list returned 6 tools to an anonymous client, including monitor_site (destructive), stop_monitoring (destructive), start_site_audit (write)

    What this check looks for

Posture changes

  1. Nov 18, 2026
    • Tools that change things, listed without credentials: 1 to 3

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 3.View diff
    • Tools that change things, listed without credentials: 1 to 3
  2. Tools3 added, 2 changed.+3 added~2 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__sitewalk__get_audit_status",
      "mcp__sitewalk__get_audit_report",
      "mcp__sitewalk__list_monitored_sites"
    ],
    "ask": [
      "mcp__sitewalk__start_site_audit"
    ],
    "deny": [
      "mcp__sitewalk__monitor_site",
      "mcp__sitewalk__stop_monitoring"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as sitewalk. Review it before you use it.

Capability tags behind 2 rules
  • mcp__sitewalk__start_site_audit untrusted-input, outbound
  • mcp__sitewalk__monitor_site untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.adityaarsharma.audit/sitewalk/verify?hash=9aa5d00c2597545293d907dc0e3bd6dbbab8c262c6c9d39452d92eb06d468563" | jq -e '.changed == false'

Pinned hash 9aa5d00c2597, from Nov 17, 2026, 04:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.adityaarsharma.audit/sitewalk/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.adityaarsharma.audit/sitewalk
[![Anlyon Radar](https://radar.anlyon.com/badge/com.adityaarsharma.audit/sitewalk.svg)](https://radar.anlyon.com/servers/com.adityaarsharma.audit/sitewalk)

Source: MCP Registry. Synced Nov 17, 2026, 04:17 UTC.

Sitewalk MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Sitewalk MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Sitewalk MCP server delete data?

Yes. 2 tools can delete, cancel or revoke something: monitor_site and stop_monitoring.

Can the Sitewalk MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Sitewalk MCP server have?

6 tools: 2 destructive, 1 write, 3 read. monitor_site, stop_monitoring, start_site_audit, get_audit_status, get_audit_report and list_monitored_sites.

Does the Sitewalk MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Sitewalk MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): start_site_audit.

Has the Sitewalk MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.