Self-hosted MCP server reporting URLs cited by major AI search engines for any query, using your own API keys.
Copy the AI prompt to install this server into Claude Code, Cursor, or another agent โ or use 1-click editor setup below.
This server is confirmed live โ we successfully called its tools/list endpoint directly (see the verified badge above). We haven't yet sandbox-tested the stdio install command below specifically, which is a separate, ongoing check.
๐ก Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Inspect callable tools, capabilities, and parameters exposed to AI agents by Citation Intelligence.
citations_checkReturn URLs cited by an AI engine (Perplexity, Claude, ChatGPT, Gemini, or Bing) for a query. Use this when an agent or user wants to see what sources an AI search engine grounds answers on. Requires at least one engine API key; auto-picks the first available.
domain_am_i_citedCheck whether a domain is cited by an AI engine across a cluster of queries. Returns per-query presence, rank, and a citation-rate summary. Use to measure visibility for a brand, product, or content site in AI search.
signals_ai_overviewCheck whether Google shows an AI Overview for a query, and which URLs it cites. Uses SerpAPI (free tier: 100/month). Set SERPAPI_KEY.
domain_cited_forList queries that the given domain has been cited for, served from the local cache. Build up a corpus by calling check_citations or am_i_cited first; cited_for queries it without spending API budget.
citations_predictScore citation likelihood for a URL from public signals (Wikipedia link presence, schema.org markup, /llms.txt, GitHub and Reddit references, canonical hygiene, HTTPS). No LLM fired - all heuristic. Returns 0-100 score, grade, signal breakdown, and ranked fixes.
panel_trackSave, load, or list named query panels. A panel is a persisted set of queries you want to monitor over time (e.g. editorial-watchlist). Use action=save with queries[] to create, action=load to read, action=list to enumerate. Panels live under <config>/panels/<name>.json.
A free, self-hosted MCP server that tells your agent what LLMs cite - across Perplexity, Google AI Overviews, ChatGPT, Claude, Gemini, and Bing.
An MCP server for agents and developers who need to know which URLs get cited by AI search engines for any query. Install once, query from any MCP-compatible client (Claude Desktop, Cursor, Claude Code, Continue, Cline, n8n, LangGraph). Self-hosted, no account, no centralized backend. Bring your own API keys; nothing is stored on a remote server.
Install this if you're:
Do NOT install this if you want:
The AI citation tracking market is dominated by VC-funded dashboards starting at $295/mo. None ships MCP-first. If you're an agent or developer who wants citation data piped directly into your workflow - not into a SaaS login - there isn't a tool for you. This is that tool.
Tools are grouped into seven namespaces: citations_*, domain_*, signals_*, panel_*, report_*, competitors_*, audit_*. The prefix is the question category; the suffix is the action. Wire names use underscores (not dots) so Anthropic-API-based MCP clients (Claude Desktop, Claude Code) can forward the tool list without HTTP 400.
Start with citations_provenance or domain_am_i_cited. Single-engine results (citations_check with a pinned engine) are directional; multi-engine consensus is the honest signal. A URL cited by 4 of 5 engines is a very different finding than one cited by 1.
citations_* โ query-level: who cites what, with what evidence| Tool | Purpose |
|---|---|
citations_provenance | Recommended first tool. Fan a query across engines; per-URL cross-engine consensus matrix. Returns interpretation_note per engine. |
citations_check | URLs cited by Perplexity / Claude / ChatGPT / Gemini / Google AI Mode for a query; or web rank via bing_serp / brave_serp |
citations_evidence | Extract the cited snippet from raw_answer for each citation (why, not just that) |
citations_predict | Citation likelihood from public signals - no LLM fired |
citations_trend | Time-series report of citation rate + per-query gained/lost deltas |
citations_freshness | Recency score (halflife=365d) for the pages an engine cites |
domain_* โ domain-level: am I cited, what for| Tool | Purpose |
|---|---|
domain_am_i_cited | Domain citation check. With engine=auto (default): fans across all available LLM engines, returns per-engine breakdown + cross-engine consensus. Pin engine= to reduce cost. |
domain_cited_for | Queries the domain has been cited for, from local cache |
domain_cited_for_diff | Diff of domain_cited_for between two time windows for a domain |
signals_* โ external signals: AI Overview, Wikipedia, GSC, answer-box position| Tool | Purpose |
|---|---|
signals_ai_overview | Google AI Overview presence + cited sources |
signals_wikipedia | List Wikipedia articles referencing a domain (zero keys) |
signals_gsc_gap | Join Google Search Console performance with AI citation status |
signals_answer_box | Bin each citation's first mention in raw_answer into early/middle/late thirds |
panel_* โ saved query panels (editorial watchlists)| Tool | Purpose |
|---|---|
panel_track | Save / load / list named query panels (editorial watchlists) |
panel_run | Run a panel through domain_am_i_cited and snapshot to disk |
report_* โ turnkey reporting artifacts| Tool | Purpose |
|---|---|
report_visibility | One-call AI visibility report over a query set (or panel): citation rate (mention frequency), share of voice vs competitors, average rank, and brand sentiment. Returns structured data + a Markdown artifact for a public page. |
competitors_* โ competitive landscape per query| Tool | Purpose |
|---|---|
competitors_canonical_set | Top cited domains per query, aggregated across engines |
competitors_compete | End-to-end competitive snapshot: your URL vs top cited competitors |
competitors_compare | Side-by-side citations_predict across 2-10 URLs |
audit_* โ fixable on-page / on-site checks| Tool | Purpose |
|---|---|
audit_schema | Deep schema.org validation - required fields per @type, malformed JSON-LD |
audit_structured_data | Repair-oriented schema.org diagnostics + suggested patches |
audit_crawler_access | Verify GPTBot / ClaudeBot / PerplexityBot / CCBot / Google-Extended etc. can fetch a URL |
audit_sitemap | Bulk citations_predict across every URL in a sitemap, worst-first |
audit_sitemap_map | Cross-reference sitemap URLs with cached citations (inverse of audit_sitemap) |
audit_llms_txt | Generate an llms.txt (https://llmstxt.org) from a sitemap |
Server-side prompt templates the client can offer end users (call via the MCP prompt list):
audit_citation_readiness(url) - chains citations_predict + audit_schemaaudit_competitor_snapshot(query, your_url?) - chains competitors_canonical_set + competitors_competeaudit_crawler_checkup(url) - runs audit_crawler_access and writes a remediation listaudit_gap_analysis(domain, days?) - drives signals_gsc_gap and suggests next movesaudit_sitemap_coverage(sitemap_url) - runs audit_sitemap_map and recommends prioritiesCache views the client can read or subscribe to (no tool call required):
citation://cache/summary - entry counts by type/engine, unique queries/URLs, oldest/newestcitation://panels - saved panels + per-panel snapshot countscitation://docs/llms-txt - llms.txt primer (markdown)citation://docs/ai-crawlers - AI crawlers cheatsheet (markdown)citation://domain/{domain}/cited-for - dynamic template: citations for {domain}Every response includes a surface field that tells you exactly how the data was collected. Understanding this is important before drawing conclusions.
| Surface | Engines | What it means |
|---|---|---|
consumer_scrape | perplexity, google_ai_mode | Proxied through a real consumer-facing AI search product. Closest to what your users see. |
api_proxy | claude, openai, gemini | API call to a search-enabled LLM. May differ from consumer product behavior โ different model versions, no UI-level ranking logic, no personalization. Use as a directional proxy, not as ground truth. |
web_rank | bing_serp, brave_serp | Traditional web search rank (not LLM citation). Measures whether a URL appears in SERP results, not whether an LLM cites it. |
static_signal | citations_predict, signals_wikipedia | Offline signal computed from public data. No live LLM query. |
perplexity (consumer_scrape) โ Sonar Pro via the Perplexity API with a consumer-equivalent system prompt. Reasonably close to Perplexity.ai. Citations come from search_results in the response; the citations fallback contains URL-only entries without title.
claude (api_proxy) โ Claude Sonnet via the Anthropic Messages API with web_search tool enabled. The consumer Claude.ai product uses different routing and ranking logic. Citation behavior can differ, especially for recent/time-sensitive queries.
openai (api_proxy) โ gpt-4o + the web_search_preview tool via the OpenAI Responses API. Replaces the deprecated gpt-4o-search-preview alias OpenAI retired; base gpt-4o plus the tool is the supported path.
gemini (api_proxy) โ Gemini 2.5 Pro via the Generative Language API with google_search grounding. Consumer Gemini uses the same grounding index but different re-ranking. Results are directional.
google_ai_mode (consumer_scrape) โ Google AI Mode results via SerpAPI. Closest to what users see in Google Search. Requires SERPAPI_KEY.
bing_serp / brave_serp (web_rank) โ Traditional SERP rank. Does NOT measure LLM citations. Use citations_check with these engines to compare organic web rank against LLM citation rank. domain_am_i_cited refuses these engines โ it only measures LLM behavior.
The proxy nature of api_proxy engines is a feature, not a bug: it lets you run citation checks without consuming expensive consumer-product quota. Just don't report API-proxy numbers as "ChatGPT cites you" without the caveat.
Every tool response includes an interpretation_note field that summarizes the fidelity in one sentence. Full per-engine fidelity ratings: docs/surface-fidelity.md.
Factual signals from GitHub, npm, and our automated checks โ not a rating.
No reviews yet โ be the first to share how this listing worked for you.
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
[](https://allmcps.com/mcp/automatelab-tech-citation-intelligence)<a href="https://allmcps.com/mcp/automatelab-tech-citation-intelligence"><img src="https://allmcps.com/api/badge/automatelab-tech-citation-intelligence?style=directory" alt="Citation Intelligence on AllMCPs" /></a>