Ext Ops Panel
Open dashboard
Comparison

CTRL vs io.github.matiosera3-ops/defi-mcp

CTRL is an MCP server published by CTRLabs. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.matiosera3-ops/defi-mcp is an MCP server published by matiosera3-ops. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplaceCTRLio.github.matiosera3-ops/defi-mcp
Official MCP Registry Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.6
Downloads/month (PyPI): 139
Downloads/week (PyPI): 44
Forks (GitHub): 0
Stars (GitHub): 1
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

CTRL vs io.github.matiosera3-ops/defi-mcp
FactCTRLio.github.matiosera3-ops/defi-mcp
Marketplaces that list it11
Stars (GitHub)11
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (www.ctrl.build/api/mcp)On your machine (defi-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/ctrlabs/ctrl-mcpgithub.com/matiosera3-ops/defi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 402 (5 days ago)no 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

CTRL

In its own words, on Official MCP Registry:

Visual DeFi workflow automation on Base + Ethereum mainnet.

io.github.matiosera3-ops/defi-mcp

In its own words, on Official MCP Registry:

AI agent access to on-chain DeFi data on Polygon & Arbitrum: balances, positions, prices.

How to run each

CTRL As a remote MCP server

Claude Code
claude mcp add --transport http ctrl-mcp https://www.ctrl.build/api/mcp

io.github.matiosera3-ops/defi-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ARBITRUM_RPC_URL=<YOUR_ARBITRUM_RPC_URL>" --env "POLYGON_RPC_URL=<YOUR_POLYGON_RPC_URL>" --transport stdio defi-mcp -- uvx defi-mcp

Requires: ARBITRUM_RPC_URL (secret), POLYGON_RPC_URL (secret)

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

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

What it can do: CTRL · What it can do: io.github.matiosera3-ops/defi-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