Skip to content

Academic Evidence Pack MCP server

io.github.jmxisnext/academic-evidence-packjmxisnextstreamable-httpv1.6.0Scanned

Signed citation-integrity reports + retraction-checked evidence packs, paid per call via x402/USDC.

6 tools: 3 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • 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 Academic Evidence Pack MCP server can do

The Academic Evidence Pack MCP server is published by the GitHub account jmxisnext. It has 6 tools. It can create or change data (3 tools: citation_report_receipt, citation_report and citation_report_large), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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 18, 2026, version 1.6.0.

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.

6 tools

Changes things 3Claude Code: ask
  • citation_reportVerify a bibliography.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a bibliography. For every reference: exists, resolves, retracted/corrected/flagged, title/author/year match against the registered record, and a rule-derived fabrication risk — as a signed (Ed25519, RFC 8785 canonical JSON), byte-reproducible JSON report. Input: structured references or BibTeX. No LLM; every claim carries its source and retrieval time. Up to 50 references. Paid: $1.00 USDC per successful call via x402 (eip155:8453). An unpaid call returns the payment requirements (isError). Results carry settled / transaction / network / payer plus the signed report. Use this to check references you already have; to find papers for a question or claim, use evidence_pack_preview / evidence_pack instead.
  • citation_report_largeVerify a bibliography.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Verify a bibliography. For every reference: exists, resolves, retracted/corrected/flagged, title/author/year match against the registered record, and a rule-derived fabrication risk — as a signed (Ed25519, RFC 8785 canonical JSON), byte-reproducible JSON report. Input: structured references or BibTeX. No LLM; every claim carries its source and retrieval time. Up to 70 references. Paid: $3.00 USDC per successful call via x402 (eip155:8453). An unpaid call returns the payment requirements (isError). Results carry settled / transaction / network / payer plus the signed report. Use this to check references you already have; to find papers for a question or claim, use evidence_pack_preview / evidence_pack instead. NOTE: $3.00 is above the @x402/core client's default spend cap (maxAmountPerPayment $1.00); raise it (client.setSpendControls) before calling, or the client refuses without sending anything.
  • citation_report_receiptRe-fetch a paid report you already bought, by its request_id, within the cache TTL.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Re-fetch a paid report you already bought, by its request_id, within the cache TTL. Free; no payment; the same signed report (request_id re-attached, unsigned, as on the paid result). Over the hosted endpoint GET /v1/citation-report/receipts/<request_id> serves the same bytes; over a local stdio run only that process can. Not found after the TTL, for previews, or for reports served by another process.
Only reads 3Show 3 read-only tools
  • citation_report_previewFree preview.No findings

    Why it is in this group

    • The name "citation_report_preview" says "preview": a word for reading.
    Description, as the server wrote it
    Free preview. Verify a bibliography. For every reference: exists, resolves, retracted/corrected/flagged, title/author/year match against the registered record, and a rule-derived fabrication risk — as a signed (Ed25519, RFC 8785 canonical JSON), byte-reproducible JSON report. Input: structured references or BibTeX. No LLM; every claim carries its source and retrieval time. Checks only the first 3 references; unsigned; no payment. Use this to check references you already have; to find papers for a question or claim, use evidence_pack_preview / evidence_pack instead.
  • evidence_packFind 3-10 scholarly candidates for a question or topic.No findings

    Why it is in this group

    • The description's first verb is "find": a word for reading.
    Description, as the server wrote it
    Find 3-10 scholarly candidates for a question or topic. Returns DOI/OpenAlex IDs, authors, year, venue, source URLs, citation context, open-access location, and known retraction/correction warnings. JSON only. Does not claim that a paper proves a statement. Paid: $0.03 USDC per successful call via x402 (eip155:8453). An unpaid call returns the payment requirements (isError). Results carry settled / transaction / network / payer. Use this when the free evidence_pack_preview (at most 3 candidates) is not enough; to check references you already have, use citation_report instead.
  • evidence_pack_previewFree triage for a question or topic: returns at most 3 scholarly candidates with DOI/OpenAlex IDs, authors, year, venue, source URLs, citation context, open-access location and kno…No findings

    Why it is in this group

    • The name "evidence_pack_preview" says "preview": a word for reading.
    Description, as the server wrote it
    Free triage for a question or topic: returns at most 3 scholarly candidates with DOI/OpenAlex IDs, authors, year, venue, source URLs, citation context, open-access location and known retraction/correction warnings. JSON only; no payment. Does not claim that a paper proves a statement. For up to 10 candidates use evidence_pack; to check references you already have use citation_report_preview.

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 or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
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 20, 2026, 19:06 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
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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://aep-api.fly.dev/mcp: tools/list returned 6 tools to an anonymous client, including citation_report_receipt (write), citation_report (write), citation_report_large (write)

    What this check looks for

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

Install

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

claude mcp add --transport http academic-evidence-pack https://aep-api.fly.dev/mcp
claude mcp add --transport http academic-evidence-pack https://aep-api.fly.dev/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": [
      "mcp__academic-evidence-pack__evidence_pack_preview",
      "mcp__academic-evidence-pack__citation_report_preview",
      "mcp__academic-evidence-pack__evidence_pack"
    ],
    "ask": [
      "mcp__academic-evidence-pack__citation_report_receipt",
      "mcp__academic-evidence-pack__citation_report",
      "mcp__academic-evidence-pack__citation_report_large"
    ],
    "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 academic-evidence-pack. Review it before you use it.

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.jmxisnext/academic-evidence-pack/verify?hash=c32e0f212c1e46c5c96a1d95cfebf2d8ba95174331dc6a49a32c29030ad2141d" | jq -e '.changed == false'

Pinned hash c32e0f212c1e, from Nov 18, 2026, 22:18 UTC.

Watch

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

https://radar.anlyon.com/servers/io.github.jmxisnext/academic-evidence-pack/changes.xml

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

Badge

Anlyon Radar badge for io.github.jmxisnext/academic-evidence-pack
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.jmxisnext/academic-evidence-pack.svg)](https://radar.anlyon.com/servers/io.github.jmxisnext/academic-evidence-pack)

Source: MCP Registry. Synced Nov 5, 2026, 03:17 UTC.

Academic Evidence Pack MCP server: questions and answers

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

Is the Academic Evidence Pack MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 3 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 Academic Evidence Pack MCP server delete data?

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

Can the Academic Evidence Pack 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 Academic Evidence Pack MCP server have?

6 tools: 3 write, 3 read. citation_report_receipt, citation_report, citation_report_large, evidence_pack_preview, citation_report_preview and evidence_pack.

Does the Academic Evidence Pack MCP server need sign-in or OAuth?

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

Does the Academic Evidence Pack MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Academic Evidence Pack MCP server changed its tools?

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