Site Audit MCP Server
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Site Audit MCP Server
Give your AI agent (Claude, Cursor, VS Code, ChatGPT-style MCP clients, n8n, custom agents) a set of website-audit tools. Each tool runs one of public Apify Actors on your own Apify account, so you see every run and every cost in your Apify console.
Tool | What it does | Underlying Actor | Price of that Actor |
| JSON-LD, Open Graph, canonical, llms.txt, AI-crawler robots cues | $0.003 / page | |
| axe-core WCAG 2.x checks (static HTML) | $0.005 / page | |
| CMS, frameworks, analytics, tags, CDN | $0.002 / domain | |
| Lighthouse via Google PageSpeed Insights, URLs / sitemap / crawl, mobile + desktop. Needs your free Google API key | $0.004 / audit | |
| Can ChatGPT, Perplexity, Claude, Apple, Google AI crawlers reach the site? | $0.005 / site | |
| New / unchanged / changed with a plain-words summary and noise filtering | $0.002 / page | |
| Check job postings for pay-range disclosure issues (potential issues for human review, sources kept) | $0.02 / posting check |
Only public pages are checked. Nothing logs in, bypasses paywalls or bot protection. Results are informational: they are not a legal compliance certificate, a ranking prediction or a guarantee of AI-search citations.
Cost
The underlying Actor's normal pay-per-event price (table above), billed to your Apify account.
Plus this server's own fee on the hosted version: $0.001 per successful tool call (and a $0.00005 start event). Running the open-source package locally (below) has no wrapper fee.
Every call has a hard spend cap (
maxTotalChargeUsd) sized from the number of URLs (minimum $0.05, Apify's per-run minimum, so a one-page check can never cost more than $0.05). Override it withmaxCostUsd($0.05 to $5).Add
dryRun: trueto preview with sample data at near-zero cost (not available for the AI-crawler and page-change tools).
Related MCP server: foglift-mcp
Connect (hosted, no install)
Use the Actor's Standby URL (shown in the Server / API tab, https://steadfeed--steadfeed-site-audit-mcp.apify.actor/mcp) with your Apify API token (create one):
{
"mcpServers": {
"steadfeed-site-audit": {
"url": "https://steadfeed--steadfeed-site-audit-mcp.apify.actor/mcp",
"headers": { "Authorization": "Bearer <YOUR_APIFY_API_TOKEN>" }
}
}
}Run locally (open source, MIT; runs straight from GitHub, no npm package)
{
"mcpServers": {
"steadfeed-site-audit": {
"command": "npx",
"args": ["-y", "github:steadfeed-dev/steadfeed-site-audit-mcp"],
"env": { "APIFY_TOKEN": "<YOUR_APIFY_API_TOKEN>", "GOOGLE_PSI_API_KEY": "<optional, for audit_pagespeed>" }
}
}
}Or clone and run it yourself: git clone https://github.com/steadfeed-dev/steadfeed-site-audit-mcp && cd steadfeed-site-audit-mcp && npm install, then point your MCP client at node /path/to/steadfeed-site-audit-mcp/src/stdio.js with APIFY_TOKEN in the environment.
Example prompts
"Audit https://example.com and https://example.com/pricing for structured data and AI readiness, then tell me the three highest-impact fixes."
"Can AI crawlers read our site? Check example.com."
"Run an accessibility check on our checkout and landing pages and group the issues by severity."
"Watch these 5 competitor pricing pages and tell me what meaningfully changed since last time" (call
monitor_page_changesagain with the samewatchlistId).
Notes and limits
Stateless Streamable HTTP; the hosted endpoint is
POST /mcp.Each call waits for the audit run and times out after 240 s; split very large lists. A very large result is truncated with a note.
The server never stores or logs your token or Google key. Locally, your
APIFY_TOKENis used only to start the run you asked for. On the hosted version, the Actor runs in your own Apify account (single-tenant) and uses that run's own credentials, so you see the server run and the audit runs in your Runs tab; the server run idles for up to 5 minutes after the last request, which uses a small amount of platform compute on your account.Not affiliated with Apify, Google or any AI vendor.
Available Tools
7 toolsaudit_accessibilityAccessibility (WCAG) checkAIdempotentInspect
Run axe-core accessibility checks (WCAG 2.x A/AA by default) on public pages and list violations by impact. Static HTML only (no login, no JavaScript rendering). Useful for EAA readiness reviews; not a legal compliance certificate.
Inputs: urls (required), dryRun, maxCostUsd, includeBestPractice, +1 more.
audit_ai_crawler_accessAI crawler access auditAIdempotentInspect
Check whether ChatGPT, Perplexity, Claude, Apple and Google AI crawlers can reach a website: robots.txt (RFC 9309), noindex tags and optional simulated live requests. Returns per-crawler allow/block results and fixes.
Inputs: urls (required), dryRun, extraPaths, liveChecks, +1 more.
audit_pagespeedBulk PageSpeed / Lighthouse auditAIdempotentInspect
Run Google PageSpeed Insights (Lighthouse) on a list of URLs, a sitemap, or a same-domain crawl, on mobile and/or desktop, with aggregated scores. Requires your own free Google PageSpeed Insights API key (googleApiKey, or the GOOGLE_PSI_API_KEY environment variable when running locally). Each URL x device is one billed audit.
Inputs: urls, dryRun, strategy, maxAudits, +5 more.
audit_schema_ai_readinessSchema and AI-readiness auditAIdempotentInspect
Check public pages for JSON-LD structured data, Open Graph, canonical/SEO signals, llms.txt and AI-crawler robots.txt cues. Returns a plain-English readiness score per page. Informational only; not a ranking or citation guarantee.
Inputs: urls (required), dryRun, maxCostUsd, checkRobots, +1 more.
detect_tech_stackWebsite tech-stack detectorBIdempotentInspect
Detect CMS, JavaScript frameworks, analytics, marketing tags and CDNs from public HTML and response headers, using curated fingerprints.
Inputs: urls (required), dryRun, maxCostUsd.
monitor_page_changesPage change monitorAInspect
Check public pages against their previous snapshot and report new/unchanged/changed with a plain-words summary of what changed (price, date and number changes, added/removed sections) and routine noise (timestamps, ads) filtered out. The first call for a watchlist stores the baseline; later calls report changes. Use the same watchlistId each time.
Inputs: pages (required), dryRun, maxCostUsd, watchlistId, +1 more.
monitor_pay_transparencyPay-transparency posting monitorAIdempotentInspect
Screen the public job postings on Greenhouse, Lever or Ashby careers boards for POTENTIAL pay-transparency issues (missing, open-ended or unparseable pay ranges, missing benefits or close-date wording where a law asks for it) under US state and city laws, with Canadian and EU notes. Every flagged item is a potential issue that needs human review, not a finding of violation, and this is not legal advice. Re-run with the same watchlistId to get changes since the last run. Pay per event: $0.02 per initial or changed posting check, $0.005 per verified unchanged recheck (maxJobsPerCompany bounds the cost).
Inputs: boardUrls (required), dryRun, maxCostUsd, watchlistId, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Most tools have clearly distinct audit targets: accessibility, tech stack, PageSpeed, page changes, and pay transparency. The two AI-related audits could be mildly confused because both inspect AI/SEO signals and robots.txt cues, but their descriptions distinguish structured-data readiness from crawler access.
The set mostly follows an action_noun pattern: audit_*, detect_*, monitor_*. Minor deviations appear in longer names like audit_schema_ai_readiness and audit_ai_crawler_access, and audit_pagespeed embeds a product name, but the convention remains readable.
Seven tools is well-scoped for a site-audit server: enough to cover multiple audit categories without overwhelming an agent. Each tool appears to earn its place as a distinct audit or monitoring capability.
The surface covers many important public-site audit areas: structured data/AI readiness, accessibility, tech stack, PageSpeed, AI crawler access, page-change monitoring, and pay-transparency screening. Some common site-audit checks are absent, such as general on-page SEO metadata, broken links, redirects, and security headers, but agents can work around these gaps for the core workflows shown.
Maintenance
Related MCP Connectors
Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.
17 data tools in one MCP server, run on Apify: Google Shopping, Flights, Hotels, News, Images, Videos, Ads Transparency, Jobs and Trends; YouTube transcripts; AI visibility checks; Google Maps leads; App Store and Google Play reviews. Pay per result. Sign in with Apify (OAuth) or an API token.
Unified 15-tool SEO, SERP, clean Markdown & GEO (LLM citation Share-of-Voice) MCP server.
6-category AI readiness, Schema.org, robots.txt, /llms.txt & 25k-token audit + auto-fix MCP server
Related MCP Servers
- AlicenseBqualityBmaintenanceMCP server that enables AI agents to perform comprehensive web audits using Google Lighthouse with 13+ tools for performance, accessibility, SEO, and security analysis.111,975 npm75MIT
- AlicenseNot gradedqualityNot gradedmaintenanceMCP server for website SEO + GEO analysis. Scan any URL to get scores across 5 categories (SEO, GEO, Performance, Security, Accessibility) with actionable fix recommendations. Enables AI coding assistants to audit websites and implement fixes autonomously.-
- AlicenseNot gradedqualityDmaintenanceOpen-source MCP server that audits websites for AI search readiness, providing deterministic scoring (0-100) and prioritized fix lists for metrics like JSON-LD, llms.txt, heading hierarchy, and AI crawler access.1MIT

squirrelscanofficial
AlicenseNot gradedqualityBmaintenanceMCP server for website QA auditing, covering SEO, performance, security, accessibility, and agent experience with 260+ rules and AI-optimized output for coding agents.310MIT