Ext Ops Panel
Open dashboard
Comparison

Academic Evidence Pack vs Particles

Academic Evidence Pack is an MCP server published by jmxisnext. Marketplaces we read that list it: 1 (Official MCP Registry). Particles is an MCP server published by linkedparticles.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceAcademic Evidence PackParticles
Official MCP Registry Listed
Version: 1.5.0
No figure published
Not marked · First seen
Listed
Version: 1.210.2
Downloads/month (PyPI): 645
Downloads/week (PyPI): 483
Forks (GitHub): 1
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Academic Evidence Pack vs Particles
FactAcademic Evidence PackParticles
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub1
Last release (differs)Not published2026-10-24
Where it runs (differs)Remote server (aep-api.fly.dev/mcp)On your machine (linkedparticles)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/linkedparticles/particles-engine-py
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 41 h agono remote endpoint we check

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Academic Evidence Pack

In its own words, on Official MCP Registry:

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

Particles

In its own words, on Official MCP Registry:

An append-only ledger of sourced, dated, confidence-scored claims your agent cites and you audit

How to run each

Academic Evidence Pack As a remote MCP server

Claude Code
claude mcp add --transport http academic-evidence-pack https://aep-api.fly.dev/mcp

Particles As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio particles -- uvx --from linkedparticles particles linkedparticles mcp serve

Requires: ANTHROPIC_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Academic Evidence Pack has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of Academic Evidence Pack publish no settings it asks for, so we do not compare settings.

What it can do: Academic Evidence Pack · What it can do: Particles · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built