Ext Ops Panel
Open dashboard
Comparison

Dappier Remote vs io.github.rjexile/sports-card-agent

Dappier Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.rjexile/sports-card-agent is an MCP server published by rjexile. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
MarketplaceDappier Remoteio.github.rjexile/sports-card-agent
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (PyPI): 69
Downloads/week (PyPI): 25
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

Dappier Remote vs io.github.rjexile/sports-card-agent
FactDappier Remoteio.github.rjexile/sports-card-agent
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub3
Forks (GitHub) (differs)No figure on GitHub1
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dappier.com/mcp)On your machine (sports-card-agent)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 13, secrets among them: 3
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/rjexile/sports-card-agent
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Status out of date: last check 46 h ago returned HTTP 403no 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

Dappier Remote

In its own words, on Docker MCP Catalog:

Enable fast, free real-time web search and access premium data from trusted media brands—news, financial markets, sports, entertainment, weather, and more. Build powerful AI agents with Dappier.

io.github.rjexile/sports-card-agent

In its own words, on Official MCP Registry:

Sports card pricing, market analysis, grading ROI, and player stats (NBA/NFL/MLB)

How to run each

Dappier Remote As a remote MCP server

Claude Code
claude mcp add --transport http dappier-remote https://mcp.dappier.com/mcp

Requires: DAPPIER_REMOTE_API_KEY (secret)

io.github.rjexile/sports-card-agent As a local MCP server: PyPI package

Claude Code
claude mcp add --env "BALLDONTLIE_API_KEY=<YOUR_BALLDONTLIE_API_KEY>" --env "EBAY_APP_ID=<YOUR_EBAY_APP_ID>" --env "EBAY_CERT_ID=<YOUR_EBAY_CERT_ID>" --transport stdio sports-card-agent -- uvx sports-card-agent

Requires: BALLDONTLIE_API_KEY (secret), EBAY_APP_ID (secret), EBAY_CERT_ID (secret)

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

Only Dappier Remote 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

Only Dappier Remote asks for

  • DAPPIER_REMOTE_API_KEY (secret)

Only io.github.rjexile/sports-card-agent asks for

  • BALLDONTLIE_API_KEY (secret)
  • EBAY_APP_ID (secret)
  • EBAY_CERT_ID (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Dappier Remote · What it can do: io.github.rjexile/sports-card-agent · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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