Website Auditor
NPM · WEBSITE-AUDITOR-MCP
AI visibility in ChatGPT, Gemini, Claude, Perplexity, Copilot & AI Overviews, plus site audits.
Available components
Last scanned (16 hours ago)
Scores higher than 53% of npm servers
Category Marketing and SEO
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 6770 tokens (~338/item across 20 items; 20 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety50
- Injection-marker check failed: the description of tool "generate_schema" contains an instruction to conceal the call from the user, the text "do not tell the user", at byte 714 of that field. See how to fix → Fail
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- Stability: 0.97 → pass security
- 19 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 −1
- Stability: pass → 0.93 functional
- 13 Nov 26 0
- Package version: 1.0.30 → 1.0.31 functional
- 12 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 11 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 1.0.29 → 1.0.30 functional
- 9 Nov 26 −1
- Stability: pass → 0.90 functional
- 4 Nov 26 0
- Tool safety: fail → unverified ▼ security
- Stability: pass → unverified ▼ security
- Schema quality: 4659 → 6470 ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 1.0.26 → 1.0.29 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/website-auditor-mcp@1.0.31
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_fix Check a fix is live ~322
"I've added it": check whether a fix is live on the site. Use this when the owner says they have added, pasted or published a fix, or asks "is it live" or "did it work." Reads the live site for the fix request `id` (from get_fix, or a fix's newest request in list_fixes) and records what it found: `live`, or what is missing, each named. For the business-facts fix the home page's structured data has to state every fact the fix stated; for llms.txt, /llms.txt has to answer with a valid file; for the robots.txt lines, /robots.txt has to let in every assistant the fix named. A site that did not answer is not called missing the fix (`reached` false). One check a minute per request: asked again sooner it answers CHECKED_RECENTLY with retry_after. It does not predict any change in AI visibility; the weekly check observes that. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| id | string | yes | The fix request's id: `request.id` from the fix as served, or a fix's newest `request.id` in the site's fix list. |
| Name | Type | Req | Description |
|---|---|---|---|
| check | object | yes | – |
| domain | string | yes | – |
| live | boolean | yes | – |
| message | string | yes | – |
| request | object | yes | – |
No examples provided.
check_upgrade_status Check upgrade status ~152
Check the caller's own Website Auditor subscription standing. Use this when someone asks "am I on Pro," "which plan am I on," "is my trial still active," "when does my subscription renew/end," "why is this tool locked," or before suggesting an upgrade. Works with any valid API key and consumes no audit quota. Returns the tier (none/free/pro; every paid plan, Agency and Enterprise included, is pro), the plan (pro, agency or enterprise) when there is a live subscription, raw subscription status, period end, whether the subscription is set to cancel, the upgrade URL, and a plain-language summary — including what starting Pro requires (a payment method and accepting the Terms).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| cancel_at_period_end | boolean | yes | – |
| current_period_end | string|null | yes | – |
| message | string | yes | – |
| plan | string | – | Which paid plan the live subscription is for; absent when there is none, or the API did not say. |
| status | string | yes | Raw subscription status: active, trialing, canceled, none, … |
| tier | string | yes | "none" | "free" | "pro". Every paid plan, Agency and Enterprise included, is "pro" here; `plan` names it. |
| upgrade_url | string | yes | – |
No examples provided.
compare_competitors Compare against competitors ~318
Compare a website's AI visibility head-to-head against named competitors. Use this when someone asks "how do I stack up against X and Y," "who does ChatGPT recommend instead of me," or wants a competitive AI-visibility view. Returns each competitor's score and where they appear that the site does not. Each competitor not already cached costs one audit against your daily quota; if the quota can't cover every competitor, it ranks the ones it could audit and returns a `quota` summary plus a `skipped` list naming the rest — it never drops competitors silently or invents scores. If the quota is already exhausted it returns an over-quota error with the reset time. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| business_location | string | – | Optional. The market to compare within, e.g. "Chiang Mai, Thailand". Applied to the site AND every competitor, because a comparison asks about one market — scoring one locally and the others globally… |
| competitors | array | yes | Competitor domains to compare against. |
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | – | – |
| gaps | array | yes | Engines where a competitor appears in AI answers and this site does not. |
| market | string|null | yes | The market every audit in this comparison was scored in, or null when each domain's own location was detected. |
| quota | object | yes | – |
| ranking | array | yes | – |
| recommendation_gap | object | – | How far behind the competitor you trail most the site is, each side as a share of its own answers, compared on the assistants that answered for both. Present only when both audits recorded stances; i… |
| skipped | array | yes | – |
| summary | string | yes | – |
No examples provided.
confirm_facts Confirm business facts ~379
Confirm the business facts a site's fixes are written from, as the site's owner confirms them. Use this only after showing the owner the facts get_fix_facts or get_fix returned (the confirm block, with the business `name`) and getting their own confirmation or corrections: never confirm facts on the owner's behalf, and never without asking them. `facts` is the owner's answers, keyed by each fact's `fact` in the confirm block (the business name under "name"); `seen` is sent back exactly as it was handed out, unchanged, and the confirmation is refused without it. Returns status "confirmed" with the confirmed block and its new `seen`. When the site's facts changed since they were shown, nothing is confirmed (status "facts_changed", with the facts as they are now): read them again with get_fix_facts and show the owner before confirming. With status "facts_not_read" the site has not been read yet and there is nothing to confirm. Confirmations are capped over any 24 hours (TOO_MANY_CONFIRMATIONS, with retry_after). Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| facts | object | yes | The owner's answers, keyed by each fact's `fact` in the confirm block (the business name under "name"). A fact left out or empty is not confirmed. |
| seen | object | yes | Exactly the `seen` that came with the facts shown to the owner, unchanged. Without it, or with it changed, nothing is confirmed. |
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | object | – | The confirm block: each fact with what the site says and what the owner confirmed. |
| domain | string | yes | – |
| message | string | yes | – |
| seen | – | – | Present when confirmed: what the block shows now, for a later correction; null when the facts cannot be confirmed again now. |
| status | string | yes | "confirmed"; "facts_changed": nothing confirmed, the site's facts changed since they were shown (`confirm` is the block as it is now); "facts_not_read": nothing confirmed, the site has not been read… |
No examples provided.
generate_schema Generate JSON-LD schema ~311
Generate structured data (JSON-LD schema) tailored to a website, to improve how AI assistants and search engines understand it. Use this when someone asks for "schema," "structured data," "JSON-LD," or wants the actual markup to implement a recommendation. Returns a DRAFT, not finished markup: every name field arrives as a placeholder — "Your Business Name" on the business types, and on a Product the product's own name and brand as "Your Product Name" and "Brand Name" — that the owner must replace with real names confirmed with them, never guessed from the domain or copied from an audit. `placement_notes` says what to replace first, then where to embed the finished snippet, so relay the whole ask and do not tell the user to paste the draft as returned. For a finished fix written from the owner's confirmed facts, with paste steps for their site's platform, use get_fix ("Get this fix") instead: its requests are recorded. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| type | string | – | Schema type; "auto" (also the default when omitted) does not detect anything — it returns an Organization draft. |
| Name | Type | Req | Description |
|---|---|---|---|
| jsonld | – | – | The JSON-LD draft (object or array). NOT ready to paste: every name field arrives as a placeholder — "Your Business Name" on the business types, and on a Product the product's own name and brand as "… |
| placement_notes | string | yes | What to replace in the draft first — each name placeholder, confirmed with the owner — then where to embed the finished snippet, e.g. "in the <head> of every page". Relay the whole string, in that or… |
No examples provided.
get_ai_visibility Check AI visibility ~659
Check how visible a website is to AI assistants right now. Use this whenever someone asks "does ChatGPT/Perplexity/Claude/Gemini/Copilot recommend this business," "is my site showing up in AI answers," "what's my AI visibility / GEO score," or wants a quick read on whether an AI assistant would surface a given domain. Returns an overall AI-visibility score (0–100), a per-engine breakdown (ChatGPT, Perplexity, Claude, Gemini, Microsoft Copilot, Google AI Overviews), and the top competitor appearing in place of the site. When the audit recorded citations, `sources` lists the documents the assistants actually read, ranked by cross-engine agreement, each marked `yours`, `competitor` or `third_party` — treat `competitor` rows as context, not as placement targets; `sources: null` means the recorded answers cited nothing attributable, and an absent key means citations were not recorded for this audit. The result also includes trend data: 7- and 30-day score movement computed from the domain's stored snapshot history, for the question this audit asked, ending at the snapshot this audit stored; when it stored no measured snapshot, `trend` is null and `trend_note` says why. The result can also carry `places`: up to 10 per-area results, each asked as if from that neighborhood or town and measured separately from the citywide score, not as a breakdown of it. `named: null` (`state` `not_measured` or `not_measured_this_week`) means that area was not measured (yet, or this week), which is not zero and not evidence the business is missing there; `partial: true` means only part of the answers were measured; `places_not_shown` counts reported areas left out of the list. One sentence per area is already in `summary`; an absent `places` means no area results are shown for this run, not a failure. If `name_warning` is present, the business name behind the score could not be verified — relay that caveat rather than presenting the score as settled fact, and offer to re-run with an explic…
| Name | Type | Req | Description |
|---|---|---|---|
| business_location | string | – | Optional. The city the business trades in, e.g. "Hilo, HI". Leave it out and the audit detects it; when nothing is detectable the questions widen to the country or drop the place entirely, which is r… |
| business_name | string | – | Optional. The business's real name, if you know it. Leave it out and the audit detects the name from the site and flags it when unverified — a guessed name is scored as if confirmed, so supply one on… |
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| appears_by_engine | object | yes | Whether the site appeared at all on each engine. Distinct from the scores: an engine can have appearances yet a low score, or the reverse. NULL when the engine was not scored — false would assert it… |
| by_engine | object | yes | Per-engine AI-visibility score, 0–100. NULL means the engine was not scored — see engine_status for which of the two reasons. A null is NOT a zero: zero means the engine answered and never named the… |
| coverage_note | string | – | Present exactly when an engine was asked and did not answer. Relay it: the score covers fewer engines than the run asked (four on a free audit, six on a paid one). |
| dashboard | object | – | – |
| engine_status | object | yes | Why each engine's score is what it is. 'scored' — the engine answered and the number is a measurement. 'unanswered' — it was asked and returned nothing, so there is no score; do not report it as 0. '… |
| name_source | string | – | "detected" | "user_supplied" | "domain_fallback". |
| name_verified | boolean | – | – |
| name_warning | string | – | Set ONLY when the business name behind the score could not be verified. The score is computed from queries built around that name, so relay this caveat rather than presenting the score as settled. |
| next_steps | array | – | Free audits only: what this result found that another tool can act on, as plain facts with the tool's name. |
| places | array | – | Results asked as if from each neighborhood or town, measured separately from the citywide score (not a breakdown of it). Present only when the report holds them; absent means no area results, not a f… |
| places_not_shown | integer | – | How many of the report's places are not in `places` (unreadable or inconsistent, or past the caps); capped at 99, so 99 means 99 or more; present only when some are left out. |
| questions_asked | array | – | The questions put to the assistants for this score, when the report recorded them. |
| recommendation_gap | object | – | How far behind the top beatable rival the site is, in the answers that recommend it. Present only when measured; its sentence is also in summary. |
| score | number | yes | Overall AI-visibility score, 0–100. |
| sources | – | – | – |
| stance_counts | object | – | How many answers recommended, mentioned or cautioned against the site. Present when recorded. |
| summary | string | yes | – |
| top_competitor | string|null | yes | The competitor appearing in place of the site, if any. |
| trend | – | yes | Pro only; null when unavailable — trend_note says why. |
| trend_note | string | – | Present exactly when trend is null: the reason. |
No examples provided.
get_benchmark Benchmark vs industry/geo ~163
Benchmark a website's AI visibility against its industry and location. Use this when someone asks "how do I compare to others in my space," "is this a good score for my industry," or wants percentile/peer context rather than an absolute number. Backed by aggregated audit data. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| geo | string | – | Optional location override. |
| industry | string | – | Optional industry override. |
| Name | Type | Req | Description |
|---|---|---|---|
| peer_median | number | yes | – |
| percentile | number | yes | The domain's percentile within its industry/geo peer set, 0–100. |
| position_summary | string | yes | – |
| sample_size | number | yes | How many peers the percentile and median are computed over. |
No examples provided.
get_changes What changed in AI visibility ~414
Report what changed in a website's AI-visibility score, only between two snapshots that asked the same question. Use this when someone asks "did anything change," "what's different this week/month," or "did my AI visibility drop." The domain need not be tracked: history accrues from any audit of it, tracked or not — track_site adds the weekly re-audits to the series, it is not a precondition, so do not track a site just to answer a change question. Returns the change in the overall score and the per-engine score changes, for engines measured both times — the overall only when the same engines answered both snapshots, otherwise it is null with an overall_note naming which answered each, and the per-engine changes stand alone; a summary says the change in plain sentences; competitor_changes, new_issues and resolved_issues are always empty, since snapshots record neither competitors nor audit issues. A change is only ever measured between two snapshots that asked the same question (the same business name, market and queries); when there is no such pair it says why instead of giving a number, with the date the series re-baselined when it did. The series is the measured weekly re-audits and any audit that asked the same question as the newest recorded one, while it has no gap longer than four weeks and a day from the newest weekly re-audit that recorded its question, through each later snapshot of the series (weekly re-audits included, recorded or not), to the newest measured snapshot; otherwise every measured snapshot. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| since | string | – | Optional ISO date or "last_check". |
| Name | Type | Req | Description |
|---|---|---|---|
| competitor_changes | array | yes | Always empty: AI-visibility snapshots record no competitors. Kept for clients that read it. |
| engine_changes | array | yes | – |
| from_captured_at | string | – | When the earlier snapshot compared was captured. |
| new_issues | array | yes | Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it. |
| note | string | – | Present when skipped_snapshots is above 0, when the two snapshots compared were answered by different engines, when newer measured snapshots were left out of the series, or when newer weekly re-audit… |
| overall_note | string | – | Present exactly when score_delta is null: the two snapshots were answered by different engines, and which answered each. Relay it — a null delta for this reason must not read like a null for want of… |
| resolved_issues | array | yes | Always empty: AI-visibility snapshots record no audit issues. Kept for clients that read it. |
| score_delta | number|null | yes | Only ever between two snapshots that asked the same question AND were answered by the same engines. When there is no such pair, including a re-baseline after the business name, market or queries chan… |
| skipped_snapshots | number | – | Snapshots passed over because they asked a different question (another business name, market or queries) or do not record what they asked. |
| summary | string | – | The change in plain sentences, built from this result's two snapshots and any newer run the comparison leaves out: the overall scores and move, each assistant that moved, those newer runs, and what P… |
| to_captured_at | string | – | When the later one was. |
No examples provided.
get_fix Get this fix ~534
"Get this fix": a site fix served finished, with paste steps for the platform the site runs on: the business-facts structured data and the llms.txt are written from the facts its owner confirmed; the robots.txt lines from what the newest audit found blocked. Use this when someone asks to "get this fix," "do it for me," "give me the structured data / llms.txt / robots.txt lines to paste," or wants a fix done rather than described. Returns status "served" with the request (its `id` is what check_fix checks) and the fix: each block ready to copy, the steps for the site's platform (or the `platform` given), and `copy_all`, the prompt and every block in one paste, where the steps carry a prompt for the agent that edits the site. Each call is recorded as a request for the fix. When the newest audit found nothing for the fix to change (for robots_txt, no AI assistant blocked), it returns status "nothing_to_fix" and records nothing. Nothing that states the owner's facts is served before the owner has confirmed them: then it returns status "confirm_first" with the `reason`, the confirm block and `seen` — show the owner those facts, and once they confirm or correct them, call confirm_facts with `seen` unchanged and ask again. With reason "facts_not_read" the site has not been read yet, so there is nothing to confirm until its next weekly check. It answers only for a site the account tracks. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| kind | string | – | Which fix: "business_facts" (structured data plus About and FAQ text, from the owner's confirmed facts), "llms_txt" (an llms.txt titled with the confirmed name), or "robots_txt" (Allow lines for the… |
| platform | string | – | The platform to write the steps for, one of the `platforms` keys in the site's fix list (e.g. "wordpress", "shopify", "developer_host"). Left out, the platform detected for the site. |
| Name | Type | Req | Description |
|---|---|---|---|
| confirm | object | – | The confirm block: each fact with what the site says and what the owner confirmed. |
| domain | string | yes | – |
| fix | object | – | Present when served. |
| message | string | yes | – |
| reason | string | – | Present on confirm_first: "unconfirmed", "stale" (the site changed a confirmed fact), "no_name", or "facts_not_read" (the site has not been read, so nothing can be confirmed yet). |
| request | object | – | Present when served: the request this call was recorded as. |
| seen | object | – | Present on confirm_first when the owner can answer it. |
| status | string | yes | "served": the fix, finished. "confirm_first": nothing served; the facts it states are not confirmed by the owner yet. "nothing_to_fix": nothing served; the site's newest audit found nothing for this… |
No examples provided.
get_fix_facts Facts to confirm ~234
Read the business facts a site's fixes are written from, as they stand to be confirmed. Use this before confirming facts, to correct facts already confirmed, or after a confirmation answered facts_changed. Returns `confirm` (each fact with what the site says and what the owner confirmed, `confirmed_at`, and any facts gone stale), `name` (the business name the audits found, for the name fact where the site states none), and `seen`, exactly what the block shows, which confirm_facts sends back unchanged. `seen` is absent when the facts cannot be confirmed yet (`can_confirm` false: the site has not been read). The facts are the owner's to confirm: show them to the owner. Reads only. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| can_confirm | boolean | yes | – |
| confirm | object | yes | The confirm block: each fact with what the site says and what the owner confirmed. |
| domain | string | yes | – |
| message | string | yes | – |
| name | string | yes | The business name the audits found, for the name fact where the site states none; empty when none. |
| seen | object | – | Absent when the facts cannot be confirmed yet. |
No examples provided.
get_gtm_plan Build a GTM plan from the audit ~309
Build a written go-to-market plan from a website's latest audit, grounded in its citation evidence. Use this when someone asks "what should I do about my AI visibility," "turn this audit into a plan," or wants a GTM or marketing plan for their site. The plan is built from the `sources` the assistants actually read — each marked `yours`, `competitor` or `third_party`; competitor sources shape the analysis but are never placement targets. When the audit recorded no citation evidence the plan grounds itself in the report's issues and stats instead. Pass `focus` or `constraints` to steer it, and `prior_plan` (the markdown from an earlier call) to refine rather than start over. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | string | – | Budget, team, or time constraints — e.g. "solo founder, $200/mo". |
| domain | string | yes | The website domain, e.g. "example.com". |
| focus | string | – | What to emphasize — e.g. "local directories", "content", "a launch next month". |
| prior_plan | string | – | The markdown of a plan from an earlier call, to refine instead of starting over. |
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | – | – |
| domain | string | yes | – |
| evidence_note | string | – | Additive, never an error: set when the plan had no citation evidence. |
| model | string | yes | – |
| plan | object | yes | – |
| sources_used | array | yes | – |
| summary | string | yes | – |
No examples provided.
get_monitoring_status Monitoring status summary ~332
Get a glanceable summary of monitoring status across all tracked websites. Use this when someone asks "how are my tracked sites doing," "what's my current AI visibility across everything I monitor," "when were my sites last checked or when do they run next," or wants a dashboard of their monitored domains. Returns, per domain, the latest AI-visibility score of its series (the measured weekly re-audits and any audit that asked the same question as the newest recorded one, while it has no gap longer than four weeks and a day from the newest weekly re-audit that recorded its question, through each later snapshot of the series (weekly re-audits included, recorded or not), to the newest measured snapshot; otherwise every measured snapshot; a newer measured snapshot outside the series is not shown, and get_changes names it), the date of its last scheduled run and when the next one runs, and the most recent change against the last snapshot that asked the same question, or a note or the summary saying why there is none — when different engines answered the two snapshots, the change shows the per-engine changes only, with a note naming which answered each, and its score_delta is null; like get_changes, a change carries competitor_changes, new_issues and resolved_issues, always empty. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | – | – |
| limit | number | yes | – |
| remaining | number | yes | – |
| sites | array | yes | – |
| summary | string | yes | – |
| used | number | yes | – |
No examples provided.
get_recommendations Prioritized fixes ~169
Get specific, prioritized fixes to raise a website's AI visibility and audit scores. Use this when someone asks "how do I fix this," "what should I change," "how do I improve my AI visibility," or after an audit surfaces issues. Returns ranked actions with expected impact, each built from the domain's latest audit and citing its evidence (blocked AI crawlers, missing structured data, the competitor sites the assistants cited). Works with any Website Auditor API key and needs an audit on record for the domain; with Pro it also says where to get listed, what the assistants get wrong about the business, and which file in the fix package fixes each finding — without Pro the listing places are only counted.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | – | – |
| recommendations | array | yes | – |
| run_id | string|null | – | The audit the steps come from. |
| tier | string | – | Which list the API served. "free" omits where to get listed, what the assistants get wrong and each finding's fix file; its step marked `locked` only counts what Pro shows. |
No examples provided.
get_report Shareable report + badge ~143
Get a shareable report URL and the embeddable "Audited by Website Auditor" badge snippet for a website. Use this when someone wants to "share," "export," "send a client," or "embed" the audit result. Returns a link and an HTML badge snippet. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| badge_html | string | yes | – |
| report_url | string | yes | – |
No examples provided.
get_sample_audit See a sample audit (no key needed) ~143
Show a complete sample Website Auditor report — no API key required, nothing to set up. Use this whenever someone wants to "try it," "see a demo," "show me what this does," "what does the output look like," or is deciding whether Website Auditor is worth subscribing to — and use it INSTEAD of refusing when no API key is configured. Returns fixed sample data for example.com in the exact shape a real audit returns: scored summary, per-test results, and the AI-visibility breakdown by engine. It is clearly marked as a sample and always describes example.com, never the user's own site — auditing a real domain needs a subscription.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| audit | object | yes | A real GET /api/audit payload, populated with sample data. |
| domain | string | yes | The fixed sample domain. Never the caller's own. |
| is_sample | boolean | yes | Always true. Never present this as a live result. |
| note | string | yes | – |
| price | string | – | – |
| upgrade_url | string | yes | – |
No examples provided.
list_fixes List ready-made fixes ~231
List the ready-made fixes Website Auditor can serve finished for a tracked site, top first: whether each is needed and why, whether the platform the site runs on can take it, and its newest request with that request's status (live, missing, or not checked yet). Use this when someone asks which fixes their site needs, which to do first, or whether a fix they added has gone live. Also returns the site's detected `platform`, the `platforms` a fix's steps can be written for, and each newest request's `id`, which check_fix takes, without recording a new request. Reads only: nothing is recorded and the site is not fetched. It answers only for a site the account tracks. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| fixes | array | yes | – |
| platform | string | – | The platform detected for the site ("unknown" when none was). |
| platforms | array | – | The platforms a fix's steps can be written for. |
| summary | string | yes | – |
| top | string|null | yes | The top fix's kind, or null when none is needed that the site's platform can take. |
No examples provided.
list_tracked_sites List monitored sites ~177
List the websites currently being monitored for AI visibility on a schedule. Use this when someone asks "what am I tracking," "which sites am I monitoring," "how many monitoring slots am I using," or wants to see their tracked domains. Returns each tracked domain with its cadence and active state, plus slots used and remaining out of the account's limit (3 sites, or 5 for a subscription started before 18 October 2026; an Agency account includes 10 client sites, plus any extra client sites it has added). Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | yes | – |
| remaining | number | yes | – |
| summary | string | yes | – |
| tracked | array | yes | – |
| used | number | yes | – |
No examples provided.
run_audit Run a full audit ~379
Run a full one-time audit of a website — AI visibility, plus security headers, broken links, performance, and a crawlability-and-markup score (`scores.seo`: robots.txt, AI crawler access, sitemap, structured data, meta description and Open Graph tags). Use this when someone asks to "audit," "scan," "check," or "review" a website's health, or wants a complete report rather than just the AI-visibility number. Returns a scored summary across categories and a link to the full report. The ranked cited-`sources` evidence behind the AI-visibility number is returned by get_ai_visibility, not by this tool. If `name_warning` is present, the business name the AI-visibility score was measured against could not be verified — relay that caveat rather than presenting the score as settled fact. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| business_location | string | – | Optional. The city the business trades in, e.g. "Hilo, HI". Leave it out and the audit detects it; when nothing is detectable the questions widen to the country or drop the place entirely, which is r… |
| business_name | string | – | Optional. The business's real name, if you know it. Leave it out and the audit detects the name from the site and flags it when unverified — a guessed name is scored as if confirmed, so supply one on… |
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| dashboard | object | – | – |
| name_warning | string | – | Set ONLY when the business name could not be verified, which puts the AI-visibility score in question. |
| next_steps | array | – | Free audits only: what this result found that another tool can act on, as plain facts with the tool's name. |
| recommendation_gap | object | – | How far behind the top beatable rival the site is, in the answers that recommend it. Present only when measured; its sentence reads the result back in one line. |
| report_url | string | yes | – |
| scores | object | yes | – |
| stance_counts | object | – | – |
| summary | string | – | Free audits only: next_steps in one sentence. |
| top_issues | array | yes | – |
No examples provided.
track_site Start/stop monitoring ~221
Start (or stop) ongoing monitoring of a website's AI visibility on a schedule. Use this when someone wants to "monitor," "track," "watch," or "get alerted about" a site's AI visibility over time, rather than a one-off check. Adds weekly re-audits to the history that get_changes reads from — a history every audit already accrues, tracked or not — so use this to be watched on a schedule, not to make get_changes work. Passing enabled: false stops monitoring by deleting the enrollment, as untrack_site does. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| cadence | string | – | Monitoring cadence (weekly). |
| domain | string | yes | The website domain, e.g. "example.com". |
| enabled | boolean | – | Set false to stop monitoring. |
| Name | Type | Req | Description |
|---|---|---|---|
| already_tracked | boolean | – | – |
| cadence | string | – | – |
| created | boolean | – | Present when starting: whether this call created a new tracking. |
| dashboard | object | – | – |
| domain | string | yes | – |
| message | string | yes | – |
| removed | boolean | – | Present when stopping. |
| tracking | boolean | yes | True after a start/confirm; false after a stop. |
No examples provided.
untrack_site Stop monitoring ~167
Stop ongoing monitoring of a website's AI visibility. Use this when someone wants to "stop tracking," "unmonitor," "stop watching," or "remove" a site from scheduled monitoring, or to free up a monitoring slot. Removing a tracked site deletes its monitoring enrollment (its past audits are kept); calling it for a site that isn't tracked changes nothing. Returns how many monitoring slots are now free. Requires a Website Auditor subscription ($49/month; eligible new customers get a 7-day free trial — payment method required, no charge until the trial ends) — if the user doesn't have one, call get_sample_audit first to show them the exact output format, free and with no API key.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The website domain, e.g. "example.com". |
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | – |
| limit | number | – | – |
| message | string | yes | – |
| remaining | number | – | – |
| removed | boolean | yes | – |
| tracking | boolean | yes | – |
| used | number | – | – |
No examples provided.
How do I install the Website Auditor MCP server?
Website Auditor runs locally as an npm package, launched with npx -y website-auditor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · website-auditor-mcp
claude mcp add spikeycoder-website-auditor-mcp -- npx -y website-auditor-mcp
What is the Website Auditor MCP server?
Website Auditor is an MCP server listed in the public MCP registry as io.github.SpikeyCoder/website-auditor-mcp. AI visibility in ChatGPT, Gemini, Claude, Perplexity, Copilot & AI Overviews, plus site audits. This page covers its npm package (website-auditor-mcp).
Is the Website Auditor MCP server safe to use?
Website Auditor scores 76 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Website Auditor MCP server expose?
Website Auditor exposes 20 tools: get_ai_visibility, run_audit, get_changes, compare_competitors, track_site, and 15 more. Their descriptions and schemas cost roughly 5,757 tokens of context every time the server is loaded.
Is the Website Auditor MCP server still maintained?
Website Auditor is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Website Auditor MCP server under?
Website Auditor declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Website Auditor MCP server?
VerifyMCP ran 16 checks on Website Auditor, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.