# Academic Evidence Pack (remote · aep-api.fly.dev)

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

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `aep-api.fly.dev`: 66/100 (this document), [markdown](https://verifymcp.io/servers/jmxisnext-academic-evidence-pack/aep-api.md), [page](https://verifymcp.io/servers/jmxisnext-academic-evidence-pack/aep-api)

## Channel facts

- Endpoint: `https://aep-api.fly.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1213 tokens (~202/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Academic Evidence Pack MCP server?

Academic Evidence Pack is a hosted endpoint at https://aep-api.fly.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http jmxisnext-academic-evidence-pack 'https://aep-api.fly.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jmxisnext-academic-evidence-pack": {
      "url": "https://aep-api.fly.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jmxisnext-academic-evidence-pack": {
      "type": "http",
      "url": "https://aep-api.fly.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jmxisnext-academic-evidence-pack]
url = "https://aep-api.fly.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jmxisnext-academic-evidence-pack": {
      "type": "remote",
      "url": "https://aep-api.fly.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jmxisnext-academic-evidence-pack --url 'https://aep-api.fly.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jmxisnext-academic-evidence-pack:
    url: "https://aep-api.fly.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jmxisnext-academic-evidence-pack": {
      "Transport": "http",
      "Url": "https://aep-api.fly.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jmxisnext-academic-evidence-pack -t streamable-http -u 'https://aep-api.fly.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jmxisnext-academic-evidence-pack": {
      "type": "http",
      "url": "https://aep-api.fly.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 63, +1)

- [cosmetic] “citation_report” reworded the description of “bibtex”
- [cosmetic] “citation_report_large” reworded the description of “bibtex”
- [cosmetic] “citation_report_preview” reworded the description of “bibtex”

### 2026-09-12 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-10 (score 61)

First indexed and scored.

## MCP tools (6)

### `evidence_pack_preview` (~150 tokens)

Evidence pack (free preview)

Free preview. 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. Returns at most 3 papers; no payment.

Input parameters:

- `exclude_known_retracted` (boolean): Default keeps retracted records but marks them; true filters them.
- `fields` (array): Optional response minimization.
- `from_year` (integer)
- `open_access_only` (boolean)
- `query` (string, required): Question, claim, or research topic.
- `to_year` (integer)

### `citation_report_preview` (~171 tokens)

Citation Integrity Report (free preview)

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.

Input parameters:

- `bibtex` (string): A BibTeX bibliography (entry key → reference id); at most 262144 UTF-8 bytes — maxLength counts characters and is exact for ASCII.
- `options` (object)
- `references` (array): Structured references. Exactly one of references / bibtex.

### `citation_report_receipt` (~125 tokens)

Citation Integrity Report (receipt re-fetch, free)

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.

Input parameters:

- `request_id` (string, required): The request_id from a paid citation_report / citation_report_large result.

### `evidence_pack` (~197 tokens)

Evidence pack (paid)

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.

Input parameters:

- `exclude_known_retracted` (boolean): Default keeps retracted records but marks them; true filters them.
- `fields` (array): Optional response minimization.
- `from_year` (integer)
- `limit` (integer): Papers to return (3-10, default 5).
- `open_access_only` (boolean)
- `query` (string, required): Question, claim, or research topic.
- `to_year` (integer)

### `citation_report` (~207 tokens)

Citation Integrity Report (paid, standard tier)

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.

Input parameters:

- `bibtex` (string): A BibTeX bibliography (entry key → reference id); at most 262144 UTF-8 bytes — maxLength counts characters and is exact for ASCII.
- `options` (object)
- `references` (array): Structured references. Exactly one of references / bibtex.

### `citation_report_large` (~254 tokens)

Citation Integrity Report (paid, large tier)

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 75 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. 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.

Input parameters:

- `bibtex` (string): A BibTeX bibliography (entry key → reference id); at most 262144 UTF-8 bytes — maxLength counts characters and is exact for ASCII.
- `options` (object)
- `references` (array): Structured references. Exactly one of references / bibtex.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/jmxisnext-academic-evidence-pack/aep-api#diagnostics

## Score history

- 2026-09-21: 66
- 2026-09-20: 66
- 2026-09-19: 65
- 2026-09-18: 65
- 2026-09-17: 64
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 63
- 2026-09-13: 62
- 2026-09-12: 62
- 2026-09-11: 61
- 2026-09-10: 61

## Common questions

### What is the Academic Evidence Pack MCP server?

Academic Evidence Pack is an MCP server listed in the public MCP registry as io.github.jmxisnext/academic-evidence-pack. Signed citation-integrity reports + retraction-checked evidence packs, paid per call via x402/USDC. This page covers its hosted endpoint (https://aep-api.fly.dev/mcp).

### Is the Academic Evidence Pack MCP server safe to use?

Academic Evidence Pack scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Academic Evidence Pack MCP server expose?

Academic Evidence Pack exposes 6 tools: evidence_pack_preview, citation_report_preview, citation_report_receipt, evidence_pack, citation_report, citation_report_large. Their descriptions and schemas cost roughly 1,104 tokens of context every time the server is loaded.

### Does the Academic Evidence Pack MCP server require authentication?

No. We connected to Academic Evidence Pack without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Academic Evidence Pack MCP server still maintained?

Academic Evidence Pack is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://aep-api.fly.dev/mcp
- Website: https://aep-api.fly.dev/docs
- Changelog RSS feed: https://verifymcp.io/servers/jmxisnext-academic-evidence-pack/aep-api.xml
- Changelog JSON feed: https://verifymcp.io/servers/jmxisnext-academic-evidence-pack/aep-api.json
- HTML version of this page: https://verifymcp.io/servers/jmxisnext-academic-evidence-pack/aep-api