Skip to content

CiteMe

by citeme.app · remote · no sign-in to list tools · v1.2.0 · published by app.citeme

Search papers, format citations in 60 styles, and verify bibliographies against scholarly sources.

Changes · 3

3 tools: 3 change things.

Scanned Oct 21, 2026

1 check matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http citeme https://citeme.app/api/mcp

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "search_citations" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "search_citations" says "search": a word for reading.

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Changes things 3Claude Code: ask
  • check_referencesVerify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues.Reads text others writeNo 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.
    Description, as the server wrote it
    Verify a user-provided bibliography against scholarly sources and return match status, identifiers, and citation issues. Results may be cached for up to six hours and usage may be logged; the bibliography is not published or added to an account.

    Annotations the server declares

    • title: Check References
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • format_citationFormat citation data (title, authors, year, etc.) into a specific citation style.Can 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

    • 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
    Format citation data (title, authors, year, etc.) into a specific citation style. The formatted result may be stored in an operational cache; the tool does not publish content or modify a user account.

    Annotations the server declares

    • title: Format Citation
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_citationsSearch scholarly sources by topic, title, author, DOI, or ISBN and return matching works as formatted citations.Reads text others write1 finding

    Why it is in this group

    • The name "search_citations" says "search": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "search_citations" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "search_citations" says "search": a word for reading.

      What this check looks for
    Description, as the server wrote it
    Search scholarly sources by topic, title, author, DOI, or ISBN and return matching works as formatted citations. Resolved works may be merged into CiteMe's shared scholarly catalog and operational caches; the tool does not publish content or modify a user account.

    Annotations the server declares

    • title: Search Citations
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: 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 write2
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.

Looked at Oct 22, 2026, 14:22 UTC, unchanged since Oct 22, 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
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
none
RFC 9728 protected resource metadata
none
Authorization servers
none
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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://citeme.app/api/mcp: tools/list returned 3 tools to an anonymous client, including search_citations (write), format_citation (write), check_references (write)

    What this check looks for

Install

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

claude mcp add --transport http citeme https://citeme.app/api/mcp

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__citeme__search_citations",
      "mcp__citeme__format_citation",
      "mcp__citeme__check_references"
    ],
    "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 citeme. Review it before you use it.

Capability tags behind 3 rules
  • mcp__citeme__search_citations untrusted-input
  • mcp__citeme__format_citation outbound
  • mcp__citeme__check_references untrusted-input