Context7
Up-to-date docs for AI agents
作者による説明(英語の原文)
AI visibility in ChatGPT, Gemini, Claude, Perplexity, Copilot & AI Overviews, plus site audits.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
WA_API_KEY, WA_API_BASE_URL「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"website-auditor": {
"command": "npx",
"args": [
"-y",
"website-auditor-mcp"
],
"env": {
"WA_API_KEY": "your-value",
"WA_API_BASE_URL": "your-value"
}
}
}
}ターミナルでこれを実行します
claude mcp add website-auditor --env WA_API_KEY=your-value --env WA_API_BASE_URL=your-value -- npx -y website-auditor-mcp動かす前に、空欄の値を入力してください。
プロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"website-auditor": {
"command": "npx",
"args": [
"-y",
"website-auditor-mcp"
],
"env": {
"WA_API_KEY": "your-value",
"WA_API_BASE_URL": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"website-auditor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"website-auditor-mcp"
],
"env": {
"WA_API_KEY": "your-value",
"WA_API_BASE_URL": "your-value"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
WA_API_BASE_URL envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント SpikeyCoder で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:WA_API_KEY
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(1.0.29)がレジストリに届いたのは一昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Context7, Codebase Memory, Exa
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Up-to-date docs for AI agents
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
An MCP server for [website-auditor.io](https://website-auditor.io) — AI-visibility (GEO) and site-audit tools you can call from any MCP client (Claude Desktop, Claude Code, Cursor, Codex, and other agents).
Ask an agent *"does ChatGPT recommend my business?"*, *"what's my AI-visibility score?"*, *"audit example.com"*, or *"how do I stack up against my competitors?"* and it answers with real data — an overall AI-visibility score (0–100), a per-engine breakdown across ChatGPT, Perplexity, Claude, Gemini, Microsoft Copilot and Google AI Overviews, a full site audit (security, performance, crawlability and markup), competitor comparisons, and ongoing monitoring.
The server is a thin, authenticated wrapper over the Website Auditor API — the audit engine, AI-visibility scoring and monitoring live in that service; this server just makes them available to agents.
| Tool | Tier | What it does |
|---|---|---|
get_sample_audit | Free — no key | A complete sample report for example.com in the exact shape a real audit returns. Needs no API key, no subscription and no network. Try this first to see what you'd be buying. |
get_ai_visibility | Pro | Current AI-visibility score (0–100) + per-engine breakdown (ChatGPT, Perplexity, Claude, Gemini, Microsoft Copilot, Google AI Overviews) + the top competitor appearing in your place. Pro subscribers also get trend: 7- and 30-day score movement from stored snapshot history for the question this audit asked, ending at its snapshot and compared only between measured snapshots that asked it, the overall further only between endpoints the same engines answered (a window engines differed over carries its engine deltas and an overall_note saying which answered each; null, with a note, when the audit stored no measured snapshot). Also recommendation_gap (points behind the top beatable rival in the answers that *recommend* you, overall and per engine, with one sentence to read back; marketplaces, delivery apps, directories and national chains are not beatable rivals) and stance_counts (answers that recommended, mentioned or cautioned against you), each present only when measured. Also questions_asked: the questions put to the assistants for the score, when the report recorded them. |
run_audit | Pro, rate-limited | Full one-time audit → category scores (AI visibility, crawlability and markup as seo, security, performance) + top issues + a shareable report URL. Also recommendation_gap and stance_counts (see get_ai_visibility), each present only when measured. |
get_changes | Pro | What changed in the AI-visibility score — 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 (else it is null with an overall_note naming which answered each, and the per-engine changes stand alone); summary says the change in plain sentences; competitor_changes, new_issues and resolved_issues are always empty. Only between two snapshots that asked the same question (the same business name, market and queries), read from the domain's series: its 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. When there is no such pair it says why instead of a number, with the date the series re-baselined when it did. 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. |
compare_competitors | Pro | Head-to-head AI-visibility ranking against named competitor domains + where each appears that you don't. Quota-aware: caps the audit fan-out to your remaining daily quota, reuses recent cached audits, and reports any competitors it had to skip rather than dropping them silently. Also recommendation_gap: how far behind the competitor you trail most you are (ties on identical counts are all named), each side as a share of its own answers, over the assistants that answered for BOTH sites; same_questions says whether both audits asked the same set of questions (null when either did not record them) and assistants which assistants the figures are over. Present only when both audits recorded stances. |
track_site | Pro | Start (or stop) weekly monitoring of a site's AI visibility. Its weekly re-audits join the history get_changes reads from, which audits accrue tracked or not — monitoring watches a site, it does not enable get_changes. |
untrack_site | Pro | Stop monitoring a site and free up a monitoring slot. Deletes the site's monitoring enrollment; past audits are kept. |
list_tracked_sites | Pro | List the sites you're monitoring, with cadence, active state, and slots used/remaining. |
get_monitoring_status | Pro | A glanceable dashboard across all tracked sites — latest score of each site's series (the series get_changes reads), the date of each one's last scheduled run and when the next runs, and the most recent like-for-like change (or a note, or the summary, saying why there is none), shown as its per-engine changes with a note naming the engines when different ones answered the two snapshots; like get_changes, its change carries competitor_changes, new_issues and resolved_issues, always empty. |
list_fixes | Pro | A tracked site's ready-made fixes ("Get this fix"), top first: whether each is needed and why, whether the site's platform can take it, and its newest request and status (live / missing). Records nothing. |
get_fix_facts | Pro | The business facts the fixes are written from, to show the owner: what the site says, what they confirmed, the business name the audits found, and seen (exactly what was shown, sent back unchanged to confirm). |
get_fix | Pro | "Get this fix": the fix served finished (structured data plus About/FAQ text, an llms.txt, or robots.txt lines that let blocked AI assistants in), the first two written only from the owner's confirmed facts, each block ready to copy, with paste steps for the site's platform and copy_all where an agent edits the site. Each call is recorded as a request. Before the facts are confirmed it answers status: "confirm_first" with the facts to show the owner; when the newest audit found nothing to change, status: "nothing_to_fix". |
confirm_facts | Pro | Confirms the facts the owner confirmed or corrected, sending back exactly the seen they were shown — never on the owner's behalf. status: "facts_changed" when the site changed since. |
check_fix | Pro | "I've added it": reads the live site for a fix request and says it's live or names what's missing. Once a minute per request (CHECKED_RECENTLY with retry_after). |
check_upgrade_status | Any valid key | Your own subscription standing — tier, status, period end, and what upgrading unlocks (starting Pro requires a payment method and accepting the Terms). Consumes no audit quota. |
Clients that support MCP prompts (Claude Desktop, claude.ai) render these as something you can pick from a menu, so you don't have to phrase the request yourself or know which tool to ask for. In clients that don't surface prompts (Codex, currently), nothing is lost but the menu — ask in words and the same tools run.
| Prompt | Needs a key? | What it does |
|---|---|---|
| See a sample report | No | Walks through a complete report for example.com. No arguments, no setup — one click from any install. |
| Check my AI visibility | Pro | Runs get_ai_visibility for a domain you name, then explains the score, which assistants name the business, and who is named instead. |
| Run a full site audit | Pro | Runs run_audit for a domain and summarises it by category, with the three fixes that matter most. |
| Compare me to a competitor | Pro | Runs compare_competitors for your domain against a named rival, and explains where they get named and you don't. |
Each Pro prompt falls back to get_sample_audit when no API key is configured, so you always get output rather than an error.
get_ai_visibility and run_audit both accept two optional arguments that decide *what question* the AI-visibility check actually asks. compare_competitors accepts business_location only — see below for why it takes no name:
| Argument | Omitted | Supplied |
|---|---|---|
business_name | Detected from the site, and flagged with name_warning when it could not be verified | Taken as fact and recorded as caller-supplied — which suppresses the warning |
business_location | Detected from the site; if nothing is found the questions widen to the country, or drop the place entirely | Scopes the questions to that place |
Supply a name only when you actually know it. A supplied name overrides detection and is treated as confirmed, so a guess is scored exactly as if a human had verified it — and silences the warning that would have told you otherwise. Leaving it out is the safer default: detection is transparent about its own uncertainty.
The same applies to location, in the other direction. Omitting it is correct for a national or global business and wrong for a local one, since a local business measured without a place is measured against the wrong queries.
On `compare_competitors`: it takes business_location and applies it to your site *and every competitor*, because a comparison asks about one market — scoring you locally while scoring your rivals globally would rank the answers to two different questions. It deliberately takes no business_name: a name identifies one business, and forwarding yours to your competitors would score every one of them as you. The result names the market it used, so a scoped comparison is never mistaken for a global one.
"Check AI visibility for hawaiibackroad.com,
the business is Big Island Backroad Adventures in Hilo, HI"
The server runs directly via npx — no clone or build required.
Try it before you buy it. Install with no API key at all and ask your agent for a *sample audit* — get_sample_audit returns a full report for example.com in the exact format a real run produces, so you can check the shape fits your needs first.
Pricing. Auditing real domains needs a Website Auditor subscription at $49/month — eligible new customers get a 7-day free trial (payment method required to start; no charge until the trial ends; customers who used a trial in the last 12 months are billed immediately). Sign up and create an API key at [api.website-auditor.io/admin_portal](https://api.website-auditor.io/admin_portal/?source=mcp), then set it as WA_API_KEY below. There is no free API tier — a key only functions with an active subscription.
Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json), and most other clients use the same mcpServers shape:
{
"mcpServers": { "website-auditor": { "command": "npx", "args": ["-y", "website-auditor-mcp"], "env": { "WA_API_KEY": "wa_your_key_here" } } } }
Claude Code — add it from the CLI:
claude mcp add website-auditor -e WA_API_KEY=wa_your_key_here -- npx -y website-auditor-mcp
Codex — the CLI, IDE extension and ChatGPT desktop app all read the same ~/.codex/config.toml, so one of these covers all three:
codex mcp add website-auditor --env WA_API_KEY=wa_your_key_here -- npx -y website-auditor-mcp
[mcp_servers.website-auditor]
command
冒頭だけを表示しています。続きはリポジトリで読めます