# CiteRank MCP (remote · citerankscore.com)

Full AI visibility audits: schema, citations, agentic readiness, agent journeys, WordPress deploys.

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-19

## Components

- remote · `citerankscore.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/webformike-citerank/api-mcp-server.md), [page](https://verifymcp.io/servers/webformike-citerank/api-mcp-server)

## Channel facts

- Endpoint: `https://citerankscore.com/api/mcp-server`
- Transports: `streamable-http`
- Auth: `required`
- Version: `2.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-19.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 800 tokens (~88/item across 9 items; 9 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http webformike-citerank https://citerankscore.com/api/mcp-server
```

### Codex

```toml
[mcp_servers.webformike-citerank]
url = "https://citerankscore.com/api/mcp-server"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "webformike-citerank": {
      "type": "remote",
      "url": "https://citerankscore.com/api/mcp-server",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add webformike-citerank --url https://citerankscore.com/api/mcp-server --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  webformike-citerank:
    url: "https://citerankscore.com/api/mcp-server"
```

### Other

```json
{
  "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.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-18 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-16 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-12 (score 63, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-11 (score 62)

First indexed and scored.

## MCP tools (9)

### `citerank_analyze_url` (~77 tokens)

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.

Input parameters:

- `focus` (string): Audit focus area. Defaults to full.
- `url` (string, required): The URL to audit (must be publicly accessible)

### `citerank_check_brand_citations` (~86 tokens)

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.

Input parameters:

- `domain` (string, required): The domain to check (e.g. example.com)
- `keywords` (array): Optional keywords to test (max 10). Auto-derived from domain if omitted.

### `citerank_generate_schema` (~78 tokens)

Generate production-ready JSON-LD structured data for any URL. Analyzes page content and produces schema markup ready to implement.

Input parameters:

- `schemaType` (string): Preferred schema type (e.g. Article, LocalBusiness, Product, FAQPage). Auto-detected if omitted.
- `url` (string, required): The URL to generate schema for

### `citerank_check_agentic_readiness` (~71 tokens)

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.

Input parameters:

- `url` (string, required): The URL (or domain) to check

### `citerank_simulate_agent_journey` (~78 tokens)

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.

Input parameters:

- `journeyType` (string, required): The type of journey to simulate
- `url` (string, required): The URL to simulate the journey on

### `citerank_list_wp_pages` (~83 tokens)

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.

Input parameters:

- `page` (number): Page number for pagination (default 1)
- `per_page` (number): Results per page (default 50, max 100)

### `citerank_analyze_wp_page` (~74 tokens)

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.

Input parameters:

- `post_id` (number, required): The WordPress post ID to analyze

### `citerank_deploy_schema` (~192 tokens)

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.

Input parameters:

- `payload` (object, required): 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, required): Deployment type. Use "schema" for per-page JSON-LD. "robots_txt" for AI bot rules. "entity_schema" for sitewide entity.

### `citerank_get_wp_health` (~61 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/webformike-citerank/api-mcp-server#diagnostics

## Score history

- 2026-08-19: 66
- 2026-08-18: 66
- 2026-08-17: 65
- 2026-08-16: 65
- 2026-08-15: 64
- 2026-08-14: 64
- 2026-08-13: 63
- 2026-08-12: 63
- 2026-08-11: 62

## Links

- Remote endpoint: https://citerankscore.com/api/mcp-server
- Authorisation metadata: https://citerankscore.com/.well-known/oauth-protected-resource/api/mcp-server
- Website: https://citerankscore.com/
- Changelog RSS feed: https://verifymcp.io/servers/webformike-citerank/api-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/webformike-citerank/api-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/webformike-citerank/api-mcp-server