Context7
제작자: upstash
Up-to-date docs for AI agents
컴퓨터 또는 클라우드★ 64,224MIT오늘 업데이트
설치
Website Auditor
개요
제작자가 쓴 설명(영어 원문)
AI visibility in ChatGPT, Gemini, Claude, Perplexity, Copilot & AI Overviews, plus site audits.
PopNx MCP의 세 기둥
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
- 사용자 의견i아직 리뷰가 없어요리뷰는 다음 단계에서 계정 기능과 함께 열려요
- 우리의 기본 점검i1개 중 1개 통과공개된 정보로 점검했으며, 코드는 아직 스캔하지 않았어요
- 사용 정도i아직 측정 안 함★ –
할 수 있는 일
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
- 연결 방식: 내 컴퓨터에서 실행
- 전송 방식: stdio
- 카테고리: 검색 및 AI 기억
- 입력해야 할 값: WA_API_KEY
설치
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
설치하기 전에
- 기본 점검: 1개 중 1개 통과
- 내 컴퓨터에서 내 사용자 계정의 권한(파일, 네트워크, 앱)으로 실행돼요.
- 직접 입력할 값:
WA_API_KEY,WA_API_BASE_URL
비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
- npmNode.js 설치(npx 명령어용)
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
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는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
직접 입력할 값
- Optional: get_sample_audit works with no key and returns a full report in the real output format. Every other tool requires a key, and minting one requires an active Website Auditor subscription ($49…
WA_API_BASE_URLenvBase URL of the Website Auditor API this server wraps. Defaults to the public production host.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
할 수 있는 일
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
기본 점검i
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 6일 점검
- ✓ 통과
제작자와 저장소 일치
레지스트리 이름이 GitHub 계정 SpikeyCoder 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
- … 아직 점검 안 함
계속 관리되고 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- … 아직 점검 안 함
라이선스 있음
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
- – 해당 없음
엔드포인트 응답
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
- – 해당 없음
OAuth로 로그인
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
- … 아직 점검 안 함
도구 설명에 숨겨진 지시 없음
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
검색 및 AI 기억 카테고리의 다른 서버와 비교i
- 이 카테고리의 다른 서버 7246개 중 0%보다 스타가 많아요
- 이 카테고리의 다른 서버 7246개 중 95%보다 최근에 레지스트리에 공개됐어요
- 기본 점검 결과가 이 카테고리의 다른 서버 7246개 중 100%와 같거나 더 좋아요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
자주 묻는 질문
Website Auditor, 안전한가요?
해당하는 기본 점검 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 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Codebase Memory
제작자: DeusData
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
내 컴퓨터에서 실행★ 48,148MIT20일 전 업데이트
설치
Exa
제작자: exa-labs
Connect AI agents to Exa for web search, content fetching, and multi-step research.
클라우드에서 실행★ 5,213MIT지난달 업데이트
설치
제작자의 README
README 열기
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
Website Auditor MCP
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.
Tools
| 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. |
Prompts
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.
Naming the business (optional)
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"
Install & configure
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-mcpCodex — 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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요