Skip to content

Citation check MCP server

io.github.ladanyin/citation-checkladanyinstreamable-httpv1.0.1Scanned

Check whether a page URL supports a claim.

1 tool: 1 change things.

Tools: 0 delete, 0 irreversible, 1 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Citation check MCP server can do

The Citation check MCP server is published by the GitHub account ladanyin. It has 1 tool. It can create or change data (1 tool: check_citation), but cannot delete data. None of its tools only reads.

1 tool brings in text other people can write (check_citation); 1 tool can send data out of your system (check_citation).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.1.

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.

1 tool

Changes things 1Claude Code: ask
  • check_citationCheck whether one public page supports one claim.Reads text others writeCan 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.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • 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 whether one public page supports one claim. Returns verdict supported, partially_supported, unclear, or unsupported, plus score, confidence, page_title, and method. score is the share of claim words found on the page, from 0 to 1, not a legal grade. Costs 0.08 credit only after the page is fetched. invalid_url and fetch_failed are not charged. Use it with one public http or https URL and one statement. Do not use it for login pages, files, or as legal advice. A low score means few claim words appear on the page. Key: https://firm.bestsmartgoods.com/signup

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
    • idempotentHint: true

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 write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
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.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:22 UTC, unchanged since Nov 10, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://cite.bestsmartgoods.com/mcp: tools/list returned 1 tool to an anonymous client, including check_citation (write)

    What this check looks for

Posture changes

  1. Nov 10, 2026
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

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.

  1. Tools1 changed.~1 changedView diff
    • Changed:check_citationChanges thingstitledescriptioninputSchemaannotations
  2. PostureRemote posture changed. HTTP status of an anonymous initialize: 401 -> 200; tools/list served without credentials: no -> yes; Tools that change things, listed without credentials: 0 -> 1 (and 2 more).View diff
    • HTTP status of an anonymous initialize: 401 to 200
    • tools/list served without credentials: no to yes
    • Tools that change things, listed without credentials: 0 to 1
    • Protocol version: none to 2025-06-18
    • WWW-Authenticate on 401: yes to not observed

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http citation-check https://cite.bestsmartgoods.com/mcp --header 'X-API-Key: <your-x-api-key>'
claude mcp add --transport http citation-check https://cite.bestsmartgoods.com/mcp --header 'X-API-Key: <your-x-api-key>'

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.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__citation-check__check_citation"
    ],
    "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 citation-check. Review it before you use it.

Capability tags behind 1 rule
  • mcp__citation-check__check_citation untrusted-input, 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.ladanyin/citation-check/verify?hash=5d0b7e19d4a3db684c639901c05dfcc49946d97fe6e0d1e6db8ed4fbd56cfd8c" | jq -e '.changed == false'

Pinned hash 5d0b7e19d4a3, from Nov 17, 2026, 09:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ladanyin/citation-check/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ladanyin/citation-check
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ladanyin/citation-check.svg)](https://radar.anlyon.com/servers/io.github.ladanyin/citation-check)

Source: MCP Registry · repository. Synced Nov 3, 2026, 20:17 UTC.

Citation check MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Citation check MCP server safe?

No scan can promise that. What its definitions show: 1 tool, 1 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 Citation check MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Citation check MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Citation check MCP server have?

1 tool: 1 write. check_citation.

Does the Citation check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Citation check MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): check_citation.

Has the Citation check MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 17, 2026. Every change is on this page and in its Atom feed.