CiteRank MCP server
io.github.WebforMike/citerankWebforMikestreamable-httpv2.0.2Scanned
Full AI visibility audits: schema, citations, agentic readiness, agent journeys, WordPress deploys.
10 tools: 1 do something that can't be undone, 6 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 5
- No findings
Sign-in required, OAuth metadata published. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CiteRank MCP server can do
The CiteRank MCP server is published by the GitHub account WebforMike. It has 10 tools. It can do things that cannot be undone, such as sending, paying or publishing (citerank_ai_traffic) and create or change data (6 tools: citerank_analyze_url, citerank_check_agentic_readiness, citerank_check_brand_citations, citerank_deploy_schema and 2 more), but cannot delete data. 3 tools only read.
2 tools bring in text other people can write (citerank_analyze_url and citerank_list_wp_pages); 5 tools can send data out of your system (citerank_ai_traffic, citerank_analyze_url, citerank_check_agentic_readiness and 2 more).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint asks for sign-in and publishes OAuth metadata.
Last scanned Nov 3, 2026, version 2.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
10 tools
Can't be undone 1Claude Code: ask
citerank_ai_trafficAI traffic for a site, measured at its own server: visits from ChatGPT, Perplexity, Claude, Gemini, Copilot and other assistants per platform, AI answer reads, top landing pages, p…Can send data outNo findings
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Description, as the server wrote it AI traffic for a site, measured at its own server: visits from ChatGPT, Perplexity, Claude, Gemini, Copilot and other assistants per platform, AI answer reads, top landing pages, pages AI reads but nobody visits, orders from AI visitors, unusual days, alerts and a plain-English summary. Compares with the previous period or the same period last year. Needs the Citerank Cloudflare Worker, the WordPress plugin, a log drain or uploaded logs on the site.
Changes things 6Claude Code: ask
citerank_analyze_urlRun a full AI visibility audit on any public URL.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "citerank_analyze_url" says "analyze": a word for reading.
- The description's first verb is "run": a word for a change.
What it can reach
- untrusted-inputThe name "citerank_analyze_url" says "analyze" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe description's first sentence says "run" and "url": it reads web pages, which anyone can write.
- untrusted-inputThe input takes a URL (input.url), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Run a full AI visibility audit on any public URL. Returns schema analysis, AI citation score, E-E-A-T signals, agentic readiness, and prioritized issues with specific fixes.
citerank_check_agentic_readinessCheck how ready a website is for AI agent interactions.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Check how ready a website is for AI agent interactions. Tests for MCP endpoint, WebMCP declarative tools, potentialAction schema, A2A agent card, llms.txt, pricing.md, and more.
citerank_check_brand_citationsCheck whether a brand/domain is cited in AI-generated answers (Google AI Overviews, Gemini).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it Check whether a brand/domain is cited in AI-generated answers (Google AI Overviews, Gemini). Returns citation rate, share of voice, top cited queries, and competitor sources.
citerank_deploy_schemaDeploy JSON-LD schema markup directly to a specific page on your connected WordPress site.No findings
Why it is in this group
- The name "citerank_deploy_schema" says "deploy": a word for a change.
Description, as the server wrote it Deploy JSON-LD schema markup directly to a specific page on your connected WordPress site. The schema is injected into the page head and tracked in the deployment log. Supports schema, speakable, llms_txt, robots, entity, webmcp, and a2a deployment types.
citerank_generate_schemaGenerate production-ready JSON-LD structured data for any URL.Can send data outNo findings
Why it is in this group
- The name "citerank_generate_schema" says "generate": a word for a change.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Generate production-ready JSON-LD structured data for any URL. Analyzes page content and produces schema markup ready to implement.
citerank_simulate_agent_journeySimulate an AI agent attempting to complete a task on a website (book, quote, contact, buy, subscribe).Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
What it can reach
- outboundThe input takes a URL (input.url): a request to a URL can carry data to whoever runs it.
Description, as the server wrote it Simulate an AI agent attempting to complete a task on a website (book, quote, contact, buy, subscribe). Returns step-by-step results and specific fixes for each failure point.
Only reads 3Show 3 read-only tools
citerank_analyze_wp_pageAnalyze a specific page on your connected WordPress site.No findings
Why it is in this group
- The name "citerank_analyze_wp_page" says "analyze": a word for reading.
Description, as the server wrote it Analyze a specific page on your connected WordPress site. Returns the recommended schema type with confidence + reason, extracted signals (phone, address, price, FAQ pairs, WooCommerce data), author info, and full content for schema generation.
citerank_get_wp_healthCheck the health of all deployments on your connected WordPress site.No findings
Why it is in this group
- The name "citerank_get_wp_health" says "get": a word for reading.
Description, as the server wrote it Check the health of all deployments on your connected WordPress site. Returns post-level schema status (active/missing/modified/deleted) and file-level checks for llms.txt, a2a.json, toolcatalog.json, and robots.txt rules.
citerank_list_wp_pagesList all pages and posts on your connected WordPress site with their current schema deployment status.Reads text others writeNo findings
Why it is in this group
- The name "citerank_list_wp_pages" says "list": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "list" and "post": it reads posts, which other people can write.
Description, as the server wrote it List all pages and posts on your connected WordPress site with their current schema deployment status. Returns each page with its URL, post type, word count, and whether schema has been deployed.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out5
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:01 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 401
- tools/list served without credentials
- no
- Tools that change things, listed without credentials
- 0
- Protocol version
- not observed
- WWW-Authenticate on 401
- yes
- resource_metadata in WWW-Authenticate
- https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- RFC 9728 protected resource metadata
- https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- Authorization servers
- https://citerankscore.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
Posture changes
- Nov 13, 2026
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- RFC 9728 protected resource metadata: none to https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- Authorization servers: none to https://citerankscore.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. HTTP status of an anonymous initialize: 200 -> 401; tools/list served without credentials: yes -> no; Tools that change things, listed without credentials: 7 -> 0 (and 7 more).View diff
- HTTP status of an anonymous initialize: 200 to 401
- tools/list served without credentials: yes to no
- Tools that change things, listed without credentials: 7 to 0
- Protocol version: 2025-06-18 to none
- WWW-Authenticate on 401: not observed to yes
- resource_metadata in WWW-Authenticate: none to https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- RFC 9728 protected resource metadata: none to https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- Authorization servers: none to https://citerankscore.com
- Dynamic client registration: not observed to yes
- Client ID metadata documents: not observed to no
Install
Pinned to version 2.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http citerank https://citerankscore.com/api/mcp-server --header 'Authorization: <your-authorization>'claude mcp add --transport http citerank https://citerankscore.com/api/mcp-server --header 'Authorization: <your-authorization>'Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__citerank__citerank_analyze_wp_page",
"mcp__citerank__citerank_get_wp_health",
"mcp__citerank__citerank_list_wp_pages"
],
"ask": [
"mcp__citerank__citerank_ai_traffic",
"mcp__citerank__citerank_analyze_url",
"mcp__citerank__citerank_check_agentic_readiness",
"mcp__citerank__citerank_check_brand_citations",
"mcp__citerank__citerank_deploy_schema",
"mcp__citerank__citerank_generate_schema",
"mcp__citerank__citerank_simulate_agent_journey"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as citerank. Review it before you use it.
Capability tags behind 6 rules
- mcp__citerank__citerank_ai_traffic outbound
- mcp__citerank__citerank_analyze_url untrusted-input, outbound
- mcp__citerank__citerank_check_agentic_readiness outbound
- mcp__citerank__citerank_generate_schema outbound
- mcp__citerank__citerank_list_wp_pages untrusted-input
- mcp__citerank__citerank_simulate_agent_journey outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.WebforMike/citerank/verify?hash=e482bf3e6f6be746ce28159c4cb5a6ae60fb7ccabbbcaa56b3e9df5b07826258" | jq -e '.changed == false'Pinned hash e482bf3e6f6b, from Nov 3, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.WebforMike/citerank/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.WebforMike/citerank)Source: MCP Registry. Synced Oct 21, 2026, 18:22 UTC.
CiteRank MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CiteRank MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 7 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CiteRank MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CiteRank MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: citerank_ai_traffic.
What tools does the CiteRank MCP server have?
- 10 tools: 1 irreversible, 6 write, 3 read. citerank_ai_traffic, citerank_analyze_url, citerank_check_agentic_readiness, citerank_check_brand_citations, citerank_deploy_schema, citerank_generate_schema, citerank_simulate_agent_journey, citerank_analyze_wp_page and 2 more.
Does the CiteRank MCP server need sign-in or OAuth?
- Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.
Does the CiteRank MCP server send data to outside services?
- 5 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): citerank_ai_traffic, citerank_analyze_url, citerank_check_agentic_readiness, citerank_generate_schema and citerank_simulate_agent_journey.
Has the CiteRank MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 3, 2026.