Google Search Console integration for Model Context Protocol (MCP)
Nothing to run from here
SiteVerdict — Website Audit Tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
29
tools declared
local
runs on your machine
—
downloads a day
What it does
Website audits for AI agents: GDPR consent, speed, WCAG, SPF/DMARC and AI-search readiness.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio siteverdict-website-audit-tools-mcp '--' npx -y @siteverdict/mcp
# 2 — ask your agent for something these tools do
# full_website_audit, get_audit_results, audit_tracking_consent and 26 more
It needs APIFY_TOKEN: this reads it from your environment, so export it first.
SiteVerdict — Website Audit Tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
SIAll 1 server
siteverdict1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts SiteVerdict — Website Audit Tools as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads APIFY_TOKEN (Your Apify API token. Audits run as Apify Actors on your account and are billed by Apify (pay-per-event)) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx APIFY_TOKEN … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'APIFY_TOKEN=${APIFY_TOKEN}' --transport stdio siteverdict-website-audit-tools-mcp '--' npx -y @siteverdict/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: APIFY_TOKEN — Your Apify API token. Audits run as Apify Actors on your account and are billed by Apify (pay-per-event).. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
29 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Runs the tracking & consent, speed & revenue, accessibility (WCAG 2.2), domain/email health and AI-search readiness checks IN PARALLEL on one website, then merges them into an overall score, an executive summary and a single fix list ranked by severity, legal/revenue impact and effort. Best first…
No parameter schema on file.
Fetches the status and results of an audit run that was still "running" when its tool returned (or any earlier run), by Apify runId. Does not start a new scan and costs nothing extra.
No parameter schema on file.
Audit tracking & cookie consent (GDPR / Consent Mode v2)
No parameter schema on file.
Scan page speed & estimate revenue lost to slowness
No parameter schema on file.
Audit accessibility (WCAG 2.2 / European Accessibility Act)
No parameter schema on file.
Check domain & email health (SPF, DKIM, DMARC, TLS, DNS)
No parameter schema on file.
Check AI-search readiness (ChatGPT, Perplexity, Google AI Overviews)
No parameter schema on file.
Detect website technology stack
No parameter schema on file.
Check website uptime and changes since last check
No parameter schema on file.
Fetch web pages as clean Markdown with citations
No parameter schema on file.
Check Google/Brave rankings for keywords
No parameter schema on file.
Diagnose organic traffic from Search Console and GA4
No parameter schema on file.
Query Google ad transparency data (BigQuery)
No parameter schema on file.
Monitor your own business's reviews
No parameter schema on file.
Find local businesses by category and place
No parameter schema on file.
Look up companies in SEC EDGAR and GLEIF
No parameter schema on file.
Watch companies for new SEC filings
No parameter schema on file.
Search the full text of SEC filings
No parameter schema on file.
Search UK and EU public tenders and contract awards
No parameter schema on file.
Screen names against UK, UN, EU and US sanctions lists
No parameter schema on file.
Validate VAT numbers, UK company numbers and LEIs
No parameter schema on file.
Extract invoice data and tables from PDFs
No parameter schema on file.
Scan flight prices and spot unusually cheap fares
No parameter schema on file.
Estimate the cost of a flight fare scan (no searches)
No parameter schema on file.
Find current flight deals and error fares from public deal feeds
No parameter schema on file.
Check UK261 / EU261 flight delay compensation
No parameter schema on file.
Check visa and entry requirements from official sources
No parameter schema on file.
UK sold prices, house price index and planning constraints
No parameter schema on file.
Get results of an earlier data-tool run
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install SiteVerdict — Website Audit Tools or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.2.1 · scanned 15 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digest8a9ae3a720c8f2b29759b67f60ec9e8ef2015d5e1cf954c3ca787d066f50326a
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (3 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
1 of the 3 recovered tools are registered only when enabled(['web'], 'full_website_audit') holds (dist/server.js:229) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 3 recovered tools are registered only when auditTools.length holds (dist/server.js:340) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
1 of the 3 recovered tools are registered only when registered.length holds (dist/tools/register.js:167) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes none of the recovered tools.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
No tool is registered unconditionally · (1) 1 only when enabled(['web'], 'full_website_audit') holds (dist/server.js:229) · (2) 1 only when auditTools.length holds (dist/server.js:340) · (3) 1 only when registered.length holds (dist/tools/register.js:167) — typically when a key or option is configured. All 3 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| full_website_audit conditional (1) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_audit_results conditional (2) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_run_results conditional (3) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest8a9ae3a720c8f2b2
Scanned2026-10-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.2.1. Pin a release below and the command asks for exactly that one.
0.2.1
13 Oct 2026
latestNo release note was published with this version.
0.2.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish SiteVerdict — Website Audit Tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.