AI Visibility MCP Server
One-call AI visibility report: can ChatGPT, Claude and Perplexity reach and understand your site?
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http ai-visibility-mcp-server 'https://steadfeed--ai-visibility-mcp.apify.actor/mcp' --header 'Authorization: <Bearer <your Apify API token>>'
{
"mcpServers": {
"ai-visibility-mcp-server": {
"type": "http",
"url": "https://steadfeed--ai-visibility-mcp.apify.actor/mcp",
"headers": {
"Authorization": "<Bearer <your Apify API token>>"
}
}
}
}
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
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. Only want the AI-visibility part? Use the focused AI Visibility MCP Server, built from this same code (MCP_TOOL_PROFILE=ai-visibility). 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 |
|---|---|---|---|
ai_visibility_report | One call: can AI assistants reach, read and understand this site? Runs crawler access, structured data / llms.txt, mobile PageSpeed, accessibility and tech stack together and returns a plain-English summary, a 0-100 readiness score and prioritized fixes | The audit Actors below | about $0.015 of checks per homepage; not charged when fewer than 2 of 4 checks can run |
check_ai_search_visibility | Ask ChatGPT and/or Perplexity your buyers' questions and measure whether your brand is named, its rank, cited sites and tone. Needs your own OpenAI / Perplexity key | AI Search Visibility Tracker | $0.01 / answer |
audit_schema_ai_readiness | JSON-LD, Open Graph, canonical, llms.txt, AI-crawler robots cues | Schema & AI-Readiness Validator | $0.003 / page |
audit_accessibility | axe-core WCAG 2.x checks (static HTML) | Accessibility WCAG / EAA Checker | $0.005 / page |
detect_tech_stack | CMS, frameworks, analytics, tags, CDN | Website Tech-Stack Detector | $0.002 / domain |
audit_pagespeed | Lighthouse via Google PageSpeed Insights, URLs / sitemap / crawl, mobile + desktop. Needs your free Google API key | Bulk PageSpeed Audit | $0.004 / audit |
audit_ai_crawler_access | Can ChatGPT, Perplexity, Claude, Apple, Google AI crawlers reach the site? | AI Crawler Access Auditor | $0.005 / site |
monitor_page_changes | New / unchanged / changed with a plain-words summary and noise filtering | Page Change Monitor | $0.002 / page |
monitor_pay_transparency | Check job postings for pay-range disclosure issues (potential issues for human review, sources kept) | Pay Transparency Compliance Monitor | $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, or $0.01 per
ai_visibility_reportwhere that event is priced (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).
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."
- "Give me an AI visibility report for example.com."
- "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.
Frequently asked questions
What is AI Visibility MCP Server?
One-call AI visibility report: can ChatGPT, Claude and Perplexity reach and understand your site?
How do I install AI Visibility MCP Server?
It runs as a remote server. In Claude Code: claude mcp add --transport http ai-visibility-mcp-server 'https://steadfeed--ai-visibility-mcp.apify.actor/mcp' --header 'Authorization: <Bearer <your Apify API token>>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does AI Visibility MCP Server need an API key?
Yes. It expects Authorization, which you set in its configuration.
Is AI Visibility MCP Server open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains AI Visibility MCP Server?
It is published by steadfeed-dev. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.