Ext Ops Panel
Open dashboard
Comparison

ProAgentStore vs DCC-MCP Core

ProAgentStore is an MCP server published by ProAgentStore. Marketplaces we read that list it: 1 (Official MCP Registry). DCC-MCP Core is an MCP server published by dcc-mcp. 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
MarketplaceProAgentStoreDCC-MCP Core
Official MCP Registry Listed
Version: 0.1.134
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.20.45
Downloads/month (PyPI): 44 802
Downloads/week (PyPI): 16 810
Forks (GitHub): 3
Stars (GitHub): 54
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

ProAgentStore vs DCC-MCP Core
FactProAgentStoreDCC-MCP Core
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)54 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last release (differs)2026-10-15 (better)2026-10-14 (worse)
Where it runs (differs)Remote server (mcp.proagentstore.online/mcp)On your machine (dcc-mcp-server)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/proagentstore/platformgithub.com/dcc-mcp/dcc-mcp-core
Changes in the last 7 days (differs)121
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

ProAgentStore

In its own words, on Official MCP Registry:

MCP-first control plane for ProAgentStore agents and private instances.

DCC-MCP Core

In its own words, on Official MCP Registry:

Agent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.

How to run each

ProAgentStore As a remote MCP server

Claude Code
claude mcp add --transport http platform https://mcp.proagentstore.online/mcp

DCC-MCP Core

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

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 ProAgentStore publish no settings it asks for, so we do not compare settings.

What it can do: ProAgentStore · What it can do: DCC-MCP Core · 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