Tool reference
The hosted platform is proprietary and moved to a private repository on 2026-10-20: six browser
tools, two MCP servers with 41 distinct tools, and a scheduled content agent, all served from
advancelabs.dev. This repo holds the open core: the six npm packages, the Chrome extension
(apps/chrome-extension) and the skills. Routes and engines below describe the hosted platform; its
code is not in this repo.
The tools were originally nine standalone apps. ADR-0003 consolidated every HTTP deployable into one hosted app; the standalone apps were deleted and their logic preserved in the
@advance-labs/*packages.
Browser tools (6)
Free, no sign-up, hosted at advancelabs.dev/tools.
| Tool | Route | API | Engine |
|---|---|---|---|
| Technical SEO + AEO audit | /tools/audit | /api/audit/technical (+ /pdf) | crawler → html-parser → schema-validator → scoring |
| E-E-A-T scanner | /tools/eeat | /api/audit/eeat | scoring (eeatScore, 14 signals) |
| llms.txt generator | /tools/llms-txt | /api/generate | crawler + html-parser |
| GA4 + GSC chat | /tools/chat | /api/chat | hosted Google clients + BYOK LLM |
| Backlink graph (3D) | /tools/graph | /api/graph (+ /stream, /expand) | hosted backlink engine + WebGL |
| Authority | /tools/authority | hosted | hosted |
MCP servers — 2
Served by the hosted platform as Streamable-HTTP route handlers via the mcp-handler adapter.
Research has 12 tools and AEO Toolkit has 40; 41 distinct tools in total. The connection page is /mcp.
Every research tool is read-only. No tool edits your site. Six AEO Toolkit tools act on your
account and say so in their annotations (readOnlyHint: false): check_ai_visibility,
get_visibility_report and discover_ranking_prompts save to your dashboard and use your plan’s
quota, submit_indexnow and submit_to_bing submit URLs to IndexNow and Bing, and
install_ai_crawler_collector creates your collector key if you have none (it never rotates one).
Research needs no login. AEO Toolkit has one: an anonymous request gets a 401
whose WWW-Authenticate names /.well-known/oauth-protected-resource/api/mcp/search/mcp, and the
client then logs in against the authorization server at /api/mcp/oauth (Dynamic Client
Registration, PKCE, and Google’s consent screen as the approval step). The tokens it issues name
the user’s stored Google connection, so the tools refresh Google access on their own. A raw Google
Authorization: Bearer token and x-bing-api-key still work, unchanged. The ROOT
/.well-known/oauth-* documents return 404 on purpose: advertising OAuth at the root would drag
the keyless research server into a login they don’t need.
Connecting
Nothing to install — these are hosted HTTP endpoints. In Claude Code:
claude mcp add --transport http --scope user aeo-research https://aeo.advancelabs.dev/api/mcp/research/mcpclaude mcp add --transport http --scope user aeo-toolkit https://aeo.advancelabs.dev/api/mcp/search/mcpFor Claude.ai, Cursor and other clients, see the connection page
or the JSON block in the README. The trailing /mcp
is required — the bare /api/mcp/<slug> returns the adapter’s own “Not found”.
| Server | Endpoint | Auth | Tools |
|---|---|---|---|
| Research | /api/mcp/research/mcp | none | analyze_website_aeo, check_ai_visibility, discover_ranking_prompts, get_visibility_report, compare_competitor_visibility, find_prospects, find_mentions, extract_contact_info, check_page_history, generate_outreach_email, verify_page_links, find_competitor_link_sources |
| AEO Toolkit (account) | /api/mcp/search/mcp | AEO Toolkit account sign-in (OAuth); Google, Bing and AI keys come from the account. Legacy Google BYOK + x-bing-api-key still work for the search tools | 40: the 23 search tools below; list_workspaces, check_ai_visibility, get_visibility_report, discover_ranking_prompts, analyze_website_aeo, get_keyword_volumes, suggest_keywords (saved to your workspace); indexing_status, submit_indexnow, submit_to_bing; and the 7 backlink tools |
The account server kept the search server’s URL. /api/mcp/toolkit/mcp (the old signed-in server) and
/api/mcp/ga-gsc/mcp still work as compatibility aliases, so existing client configs need no change.
The research server replaced two servers on 2026-11-14: aeo-visibility (/api/mcp/ai-visibility/mcp)
and aeo-backlink (/api/mcp/backlink/mcp). Both URLs still work and serve their own tools, so
existing configs need no change.
Search tools (on the AEO Toolkit server): 23 tools
| Tool | Engine | Notes |
|---|---|---|
list_ga4_properties | ||
list_gsc_sites | ||
ga4_run_report | ||
gsc_search_analytics | ||
gsc_top_queries | ||
gsc_ctr_gaps | ||
compare_periods | ||
gsc_traffic_drop | ||
gsc_cannibalization | ||
gsc_decay | ||
gsc_url_inspect | up to 25 URLs per call; read-only, cannot request indexing | |
list_bing_sites | Bing | |
bing_traffic_stats | Bing | |
bing_top_queries | Bing | |
bing_top_pages | Bing | |
bing_query_pages | Bing | exactly one of query/page |
bing_index_health | Bing | crawl stats, crawl issues, submission quota |
bing_keyword_research | Bing | no Google Search Console equivalent exists |
compare_engines | Google + Bing | merged rows with an explicit coverage block |
engine_divergence | Google + Bing | classifies each query as google_specific / bing_specific / broad |
get_ai_demand | AI crawler collector | measured AI-assistant fetches per page and day beside search and training crawls, verified vs unverified split, change on the previous period; needs the collector installed; read-only, uses no checks |
verify_ai_crawler | AI crawler registry | is this User-Agent and IP a real AI crawler: claimed bot, vendor, kind, and whether the IP is in the vendor’s published ranges; read-only, uses no checks |
install_ai_crawler_collector | AI crawler collector | install steps and code for counting AI-assistant requests (Next.js, Cloudflare, WordPress, Vercel drain or other); creates the collector key if none exists, never rotates one; uses no checks |
On the signed-in server, Bing uses the Webmaster key saved on your project. The legacy path is an
X-Bing-Api-Key request header, or a static BING_API_KEY environment variable as a fallback. A missing Bing key does not fail the server: Bing tools return
their own credential error, but the eleven Google tools keep working, and the server degrades to
Google-only rather than failing outright.
engine_divergenceand the two engines’ date windows. Bing’sGetQueryStatstakes no date parameter, socompare_engineshonours the requested range on the Google side only and labels the Bing side as its own unwindowed aggregate.engine_divergencedoes honour the range on both sides, by a different route: it fetches Bing once and buckets the rows locally on each row’s own date, which works because Bing returns one row per (query x date) rather than one aggregate per query. Verified against the live API on 2026-09-09 (maxRowsForOneQuery=3acrossdistinctDates=6). When an engine cannot answer a half, that key is reported asinsufficient_data— never as zero clicks, which would manufacture a confident verdict out of an API failure.
Skills
The MCP tools detect and measure; the agent skills carry the method for fixing what they find. 24 skills cover every one of the 58 scoring rules (each rule has exactly one owning skill, see the audit rules) plus measurement workflows on top of the search and visibility tools. One command installs the skills together with these two servers:
/plugin install aeo-toolkit --marketplace Advance-Labs/aeo-toolkitContent agent — 1
The blogging agent runs as a Vercel Cron (/api/cron/blogging, daily 13:00 UTC), not a separate
app. Its pipeline — research → draft → edit → dedup → schedule → publish → self-correct — lives in
the hosted platform (the code is in the private repository).
Chrome extension — 1
apps/chrome-extension runs @advance-labs/scoring in single-page
mode against the active tab. The audit is fully client-side — the only network calls are same-origin
fetches for robots.txt, sitemap.xml, and llms.txt. Exports a PDF via jsPDF.
The scoring engine
All audit surfaces share one rule engine. The code is the source of truth:
| Rule set | Count | Covers |
|---|---|---|
technicalSeoRules | 31 | robots/sitemap/llms.txt, HTTPS, meta, Open Graph, canonical, structured data, content, mobile |
aeoRules | 13 | answerability, answer-engine schema, GPTBot/ClaudeBot/PerplexityBot directives, content extractability |
auditRules (the two above) | 44 | what the hosted technical audit runs |
eeatSignalDefs | 14 | the separate E-E-A-T scan: Experience, Expertise, Authoritativeness, Trust |
44 + 14 = 58 is the engine total, never what a single audit runs. The Chrome Web Store build (0.3.2, checked 2026-11-17) runs 44 checks.
mode: 'single-page' runs the same rules minus multi-page crawl signals; this is what the extension uses.
AEO Toolkit is an open-source instrument by Advance Labs.