Is the Webformike Citerank MCP server down?

mcp-registry/io.github.webformike/citerank · v2.0.0

healthy
Last checked 2026-10-23 19:20 UTC · handshake 130ms

As of 2026-10-23 19:20 UTC, the Webformike Citerank MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
100%
checks observed
4,404
outages (90d)
1
tools
10

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

Install Webformike Citerank MCP server

Add to Cursor Add to VS Code

Claude Code

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

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "webformike-citerank-mcp-server": {
      "type": "http",
      "url": "https://citerankscore.com/api/mcp-server"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (82/100)

B (82/100): 0 error(s), 2 warning(s) across 10 tool(s); ~1,618 tokens of tool definitions.
Scores higher than 37% of 15,588 MCP servers Glimind has audited.
Its tool list costs an agent ~1,618 tokens per session — lighter than 60% of servers.
81 → 82 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints12
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (3)

10 of 10 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: citerank_ai_traffic, citerank_analyze_url, citerank_analyze_wp_page, citerank_check_agentic_readiness, citerank_check_brand_citations and 5 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: citerank_deploy_schema

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.webformike%2Fciterank/fixes

citerank_analyze_url 1 change
{
  "name": "citerank_analyze_url",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The URL to audit (must be publicly accessible)"
      },
      "focus": {
        "enum": [
          "full",
          "schema",
          "citations",
          "agentic",
          "eeat"
        ],
        "type": "string",
        "description": "Audit focus area. Defaults to full."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
citerank_analyze_wp_page 1 change
{
  "name": "citerank_analyze_wp_page",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "post_id"
    ],
    "properties": {
      "post_id": {
        "type": "number",
        "description": "The WordPress post ID to analyze"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
citerank_check_agentic_readiness 1 change
{
  "name": "citerank_check_agentic_readiness",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "url"
    ],
    "properties": {
      "url": {
        "type": "string",
        "description": "The URL (or domain) to check"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.webformike/citerank"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.webformike/citerank"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.webformike%2Fciterank.svg)](https://glimind.com/server/mcp-registry%2Fio.github.webformike%2Fciterank?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.webformike%2Fciterank?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.webformike%2Fciterank.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.webformike%2Fciterank.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.webformike%2Fciterank?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:10549160c41c51ac…, first seen 2026-10-17, included at leaf 16621 of 54,038. Version history · verify what your client received.

Tools (10)

Compare: most reliable analytics servers · most reliable seo servers · most reliable web servers · most reliable search servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Webformike Citerank MCP server down right now?

As of 2026-10-23 19:20 UTC, the Webformike Citerank MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 1 outage in 90 days, with a median recovery of 6 minutes.

How many tools does Webformike Citerank MCP server provide?

Webformike Citerank MCP server advertises 10 tools, including citerank_ai_traffic, citerank_analyze_url, citerank_analyze_wp_page, citerank_check_agentic_readiness, citerank_check_brand_citations.

How do I install Webformike Citerank MCP server?

Point your MCP client at this streamable-http endpoint: https://citerankscore.com/api/mcp-server

Is the Webformike Citerank MCP server safe to connect to an AI agent?

Glimind scanned all 10 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Webformike Citerank MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve