Is the Franksterino Citeguard MCP server down?

mcp-registry/io.github.franksterino/citeguard · v0.1.2

Also listed as glama/franksterino/citeguard

down
Last checked 2026-10-26 21:17 UTC · handshake 399ms

As of 2026-10-26 21:17 UTC, the Franksterino Citeguard MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 74% of Glimind's liveness checks. It had 80 outages in 90 days, with a median recovery of 25.7 hours.

uptime (30d checks)
74%
checks observed
691
outages (90d)
80
tools
3

Verify citations in AI text: fetches each cited source, returns verdicts with evidence quotes.

Point your MCP client at this streamable-http endpoint: https://citeguard.boundy.workers.dev/mcp

Agent-readiness: D (68/100)

D (68/100): 2 error(s), 2 warning(s) across 3 tool(s); ~394 tokens of tool definitions.
Scores higher than 3% of 15,772 MCP servers Glimind has audited.
Its tool list costs an agent ~394 tokens per session — lighter than 95% of servers.
69 → 70 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions67
Safety hints30
Token cost100
Client compatibility70
Protocol100
Reliability0
Stability100

What to fix (5)

The endpoint did not complete an MCP handshake.

Check the URL, TLS certificate and that the server answers a JSON-RPC "initialize" POST. How to fix →

Reachable 74.0% of the time over the last 30 days; median recovery 1543 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

3 of 3 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: check_document, check_links, verify_claims

1 parameter(s) across 1 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: verify_claims

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: 2 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 1 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.franksterino%2Fciteguard/fixes

check_document 1 change 
{
  "name": "check_document",
  "description": "Audit every citation in a markdown/plain-text document: extracts claim+source pairs (markdown links, footnotes, DOIs, bare URLs), verifies each against the fetched source, and returns a report with a citation integrity score (0-100).",
  "inputSchema": {
    "type": "object",
    "required": [
      "document"
    ],
    "properties": {
      "document": {
        "type": "string",
        "description": "Document text (markdown or plain text)"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_links 1 change 
{
  "name": "check_links",
  "description": "Liveness-only check (no LLM): extracts all cited URLs and reports dead links, homepage redirects, and archive.org availability.",
  "inputSchema": {
    "type": "object",
    "required": [
      "document"
    ],
    "properties": {
      "document": {
        "type": "string",
        "description": "Document text (markdown or plain text)"
      }
    }
  },
  "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.franksterino/citeguard"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.franksterino/citeguard"}) 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.franksterino%2Fciteguard.svg)](https://glimind.com/server/mcp-registry%2Fio.github.franksterino%2Fciteguard?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.franksterino%2Fciteguard?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.franksterino%2Fciteguard.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.franksterino%2Fciteguard.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.franksterino%2Fciteguard?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:f2d1aa9f2c0dcef5…, first seen 2026-10-17, included at leaf 10651 of 76,900. Version history · verify what your client received.

Working alternatives

Tools (3)

Compare: most reliable retrieval servers · most reliable web 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 Franksterino Citeguard MCP server down right now?

As of 2026-10-26 21:17 UTC, the Franksterino Citeguard MCP server is down with a Glimind reliability score of 38/100 (grade F). Over the last 30 days it answered 74% of Glimind's liveness checks. It had 80 outages in 90 days, with a median recovery of 25.7 hours.

How many tools does Franksterino Citeguard MCP server provide?

Franksterino Citeguard MCP server advertises 3 tools, including check_document, check_links, verify_claims.

How do I install Franksterino Citeguard MCP server?

Point your MCP client at this streamable-http endpoint: https://citeguard.boundy.workers.dev/mcp

Is the Franksterino Citeguard MCP server safe to connect to an AI agent?

Glimind scanned all 3 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 Franksterino Citeguard 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