Academic Evidence Pack
REMOTE · AEP-API.FLY.DEV · SCANNED SEP 20
Signed citation-integrity reports + retraction-checked evidence packs, paid per call via x402/USDC.
Available components
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
- Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
remote · aep-api.fly.dev
claude mcp add --transport http jmxisnext-academic-evidence-pack 'https://aep-api.fly.dev/mcp'
{
"mcpServers": {
"jmxisnext-academic-evidence-pack": {
"url": "https://aep-api.fly.dev/mcp"
}
}
} {
"servers": {
"jmxisnext-academic-evidence-pack": {
"type": "http",
"url": "https://aep-api.fly.dev/mcp"
}
}
} [mcp_servers.jmxisnext-academic-evidence-pack] url = "https://aep-api.fly.dev/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jmxisnext-academic-evidence-pack": {
"type": "remote",
"url": "https://aep-api.fly.dev/mcp",
"enabled": true
}
}
} openclaw mcp add jmxisnext-academic-evidence-pack --url 'https://aep-api.fly.dev/mcp' --transport streamable-http
mcp_servers:
jmxisnext-academic-evidence-pack:
url: "https://aep-api.fly.dev/mcp" {
"McpServers": {
"jmxisnext-academic-evidence-pack": {
"Transport": "http",
"Url": "https://aep-api.fly.dev/mcp"
}
}
} assistant mcp add jmxisnext-academic-evidence-pack -t streamable-http -u 'https://aep-api.fly.dev/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +1
- “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” cosmetic
3 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 12 Sept 26 +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.
- 11 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://aep-api.fly.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 21 Aug 2026 | 19 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 688c4daf5300c51e0a5c1f6837a3a67a868 |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of aep-api.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://aep-api.fly.dev/mcp | Verified | 200 | |
| http (plaintext) | http://aep-api.fly.dev/mcp | HTTPS enforced | 301 | https://aep-api.fly.dev/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
citation_report Citation Integrity Report (paid, standard tier) ~207
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
citation_report_large Citation Integrity Report (paid, large tier) ~254
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
citation_report_preview Citation Integrity Report (free preview) ~171
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
citation_report_receipt Citation Integrity Report (receipt re-fetch, free) ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | The request_id from a paid citation_report / citation_report_large result. |
No output schema declared.
No examples provided.
evidence_pack Evidence pack (paid) ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Question, claim, or research topic. |
| to_year | integer | – | – |
No output schema declared.
No examples provided.
evidence_pack_preview Evidence pack (free preview) ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Question, claim, or research topic. |
| to_year | integer | – | – |
No output schema declared.
No examples provided.
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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.