Ext Ops Panel
Open dashboard
Comparison

Python Package Runtime Test vs io.github.mrfentmen/pypi-mcp

Python Package Runtime Test is an MCP server published by ligafew. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrfentmen/pypi-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplacePython Package Runtime Testio.github.mrfentmen/pypi-mcp
Official MCP Registry Listed
Version: 1.0.2
No figure published
Not marked · First seen
Listed
Version: 1.0.0
Downloads/month (npm): 574
Downloads/week (npm): 77
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

Python Package Runtime Test vs io.github.mrfentmen/pypi-mcp
FactPython Package Runtime Testio.github.mrfentmen/pypi-mcp
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)Remote server (apcs-public-mcp-gateway.apcs-mcp.workers.dev/mcp/python-package-runtime-test)On your machine (pypi-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/mrfentmen/awesome-mcps
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 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

Python Package Runtime Test

In its own words, on Official MCP Registry:

Hosted Python sandbox for package runtime verification: pip install and usable-import evidence.

io.github.mrfentmen/pypi-mcp

In its own words, on Official MCP Registry:

Keyless MCP server for PyPI: Python package versions, summaries, authors, requirements, release...

How to run each

Python Package Runtime Test As a remote MCP server

Claude Code
claude mcp add --transport http python-package-runtime-test https://apcs-public-mcp-gateway.apcs-mcp.workers.dev/mcp/python-package-runtime-test

io.github.mrfentmen/pypi-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio pypi-mcp -- npx -y pypi-mcp

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

Only Python Package Runtime Test 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: Python Package Runtime Test · What it can do: io.github.mrfentmen/pypi-mcp · 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