CiteRank MCP
REMOTE · CITERANKSCORE.COM · SCANNED OCT 9
Full AI visibility audits: schema, citations, agentic readiness, agent journeys, WordPress deploys.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 800 tokens (~88/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "citerank_deploy_schema" implies "deploy" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the CiteRank MCP server?
CiteRank MCP is a hosted endpoint at https://citerankscore.com/api/mcp-server, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · citerankscore.com
claude mcp add --transport http webformike-citerank 'https://citerankscore.com/api/mcp-server'
{
"mcpServers": {
"webformike-citerank": {
"url": "https://citerankscore.com/api/mcp-server"
}
}
} {
"servers": {
"webformike-citerank": {
"type": "http",
"url": "https://citerankscore.com/api/mcp-server"
}
}
} [mcp_servers.webformike-citerank] url = "https://citerankscore.com/api/mcp-server"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"webformike-citerank": {
"type": "remote",
"url": "https://citerankscore.com/api/mcp-server",
"enabled": true
}
}
} openclaw mcp add webformike-citerank --url 'https://citerankscore.com/api/mcp-server' --transport streamable-http
mcp_servers:
webformike-citerank:
url: "https://citerankscore.com/api/mcp-server" {
"McpServers": {
"webformike-citerank": {
"Transport": "http",
"Url": "https://citerankscore.com/api/mcp-server"
}
}
} assistant mcp add webformike-citerank -t streamable-http -u 'https://citerankscore.com/api/mcp-server'
{
"mcpServers": {
"webformike-citerank": {
"type": "http",
"url": "https://citerankscore.com/api/mcp-server"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 +3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 +1
- Stability: 0.97 → pass security
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 11 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 9 Oct 2026 · Probed https://citerankscore.com/api/mcp-server
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.citerankscore.com | CN=YR2,O=Let's Encrypt,C=US | 29 Sept 2026 | 28 Dec 2026 | RSA 2048 | SHA256-RSA | 6e6bb360d13b0177bd976fdd4dad5228828 |
| SANs: *.citerankscore.com, citerankscore.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of citerankscore.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| citerankscore.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval' https://fonts.googleapis.com https://cdn.jsdelivr.net https://www.googletagmanager.com https://d3js.org https://cdnjs.cloudflare.com https://www.clarity.ms https://*.clarity.ms; worker-src 'self' blob:; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com https://fonts.gstatic.com; img-src 'self' data: https: blob:; font-src 'self' https://fonts.gstatic.com; connect-src 'self' https://cdn.jsdelivr.net https://contentcredentials.org https://cai-watermark.adobe.net https://*.supabase.co https://generativelanguage.googleapis.com https://api.openai.com https://api.anthropic.com https://api.perplexity.ai https://api.x.ai https://api.bing.microsoft.com https://dataforseo.com https://api.lemonsqueezy.com https://www.googletagmanager.com https://www.google-analytics.com https://*.google-analytics.com https://*.analytics.google.com https://www.wikidata.org https://en.wikipedia.org https://www.clarity.ms https://*.clarity.ms; media-src 'n |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://citerankscore.com/api/mcp-server | Verified | 200 | |
| http (plaintext) | http://citerankscore.com/api/mcp-server | HTTPS enforced | 308 | https://citerankscore.com/api/mcp-server |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
citerank_analyze_url ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| focus | string | – | Audit focus area. Defaults to full. |
| url | string | yes | The URL to audit (must be publicly accessible) |
No output schema declared.
No examples provided.
citerank_analyze_wp_page ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| post_id | number | yes | The WordPress post ID to analyze |
No output schema declared.
No examples provided.
citerank_check_agentic_readiness ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The URL (or domain) to check |
No output schema declared.
No examples provided.
citerank_check_brand_citations ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | The domain to check (e.g. example.com) |
| keywords | array | – | Optional keywords to test (max 10). Auto-derived from domain if omitted. |
No output schema declared.
No examples provided.
citerank_deploy_schema ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| payload | object | yes | Deployment payload. For schema: {jsonld: "..."}. For llms_txt: {content:"..."}. For robots: {rules:"..."}. |
| post_id | number | – | WordPress post ID to deploy schema to (required for per-page schema) |
| signal_key | string | – | Signal identifier (e.g. "schema", "speakable"). Defaults to type. |
| type | string | yes | Deployment type. Use "schema" for per-page JSON-LD. "robots_txt" for AI bot rules. "entity_schema" for sitewide entity. |
No output schema declared.
No examples provided.
citerank_generate_schema ~78
Generate production-ready JSON-LD structured data for any URL. Analyzes page content and produces schema markup ready to implement.
| Name | Type | Req | Description |
|---|---|---|---|
| schemaType | string | – | Preferred schema type (e.g. Article, LocalBusiness, Product, FAQPage). Auto-detected if omitted. |
| url | string | yes | The URL to generate schema for |
No output schema declared.
No examples provided.
citerank_get_wp_health ~61
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
citerank_list_wp_pages ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination (default 1) |
| per_page | number | – | Results per page (default 50, max 100) |
No output schema declared.
No examples provided.
citerank_simulate_agent_journey ~78
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.
| Name | Type | Req | Description |
|---|---|---|---|
| journeyType | string | yes | The type of journey to simulate |
| url | string | yes | The URL to simulate the journey on |
No output schema declared.
No examples provided.
What is the CiteRank MCP server?
CiteRank MCP is listed in the public MCP registry as io.github.WebforMike/citerank. Full AI visibility audits: schema, citations, agentic readiness, agent journeys, WordPress deploys. This page covers its hosted endpoint (https://citerankscore.com/api/mcp-server).
Is the CiteRank MCP server safe to use?
CiteRank MCP scores 80 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CiteRank MCP server expose?
CiteRank MCP exposes 9 tools: citerank_analyze_url, citerank_analyze_wp_page, citerank_check_agentic_readiness, citerank_check_brand_citations, citerank_deploy_schema, and 4 more. Their descriptions and schemas cost roughly 800 tokens of context every time the server is loaded.
Does the CiteRank MCP server require authentication?
No. We connected to CiteRank MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CiteRank MCP server still maintained?
CiteRank MCP is still listed as active in the MCP registry. We last reached this channel on 9 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.