Ext Ops Panel
Open dashboard
Comparison

Clinical Trial Tracker vs io.github.pkotecha-eng/aria-mcp-server

Clinical Trial Tracker is an MCP server published by agentstructure. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pkotecha-eng/aria-mcp-server is an MCP server published by pkotecha-eng. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
MarketplaceClinical Trial Trackerio.github.pkotecha-eng/aria-mcp-server
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (PyPI): 161
Downloads/week (PyPI): 48
Forks (GitHub): 2
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

Clinical Trial Tracker vs io.github.pkotecha-eng/aria-mcp-server
FactClinical Trial Trackerio.github.pkotecha-eng/aria-mcp-server
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub2
Last releaseNot publishedNot published
Where it runs (differs)Remote server (clinicaltracker.org/mcp/public)On your machine (aria-mcp-server)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/pkotecha-eng/aria-mcp-server
Changes in the last 7 days (differs)20
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)Responded 25 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

Clinical Trial Tracker

In its own words, on Official MCP Registry:

Search and monitor ClinicalTrials.gov and EU trial registry records, with trial change tracking and

io.github.pkotecha-eng/aria-mcp-server

In its own words, on Official MCP Registry:

Search 35M+ PubMed, 400K+ ClinicalTrials.gov & ISRCTN trials. Prompts included. No API key.

How to run each

Clinical Trial Tracker As a remote MCP server

Claude Code
claude mcp add --transport http clinical https://clinicaltracker.org/mcp/public

io.github.pkotecha-eng/aria-mcp-server As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio aria-mcp-server -- uvx aria-mcp-server

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

Only Clinical Trial Tracker 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

Neither one's marketplaces publish the settings it asks for.

What it can do: Clinical Trial Tracker · What it can do: io.github.pkotecha-eng/aria-mcp-server · 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