Ext Ops Panel
Open dashboard
Comparison

io.github.abm-dev-git/abm-mcp vs io.github.patwalls/slope-mcp

io.github.abm-dev-git/abm-mcp is an MCP server published by abm-dev-git. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.patwalls/slope-mcp is an MCP server published by patwalls. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
Marketplaceio.github.abm-dev-git/abm-mcpio.github.patwalls/slope-mcp
Official MCP Registry Listed
Version: 1.0.3
Downloads/month (npm): 217
Downloads/week (npm): 42
Forks (GitHub): 1
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.1.0
Downloads/month (npm): 100
Downloads/week (npm): 23
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

io.github.abm-dev-git/abm-mcp vs io.github.patwalls/slope-mcp
Factio.github.abm-dev-git/abm-mcpio.github.patwalls/slope-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)1No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.abm.dev/mcp)On your machine (slope-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/abm-dev-git/abm-mcpgithub.com/patwalls/slope
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 2 days ago, requires a keyno 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

io.github.abm-dev-git/abm-mcp

In its own words, on Official MCP Registry:

abm.dev — the account-based marketing API for AI agents: Search, Enrich, and Create across B2B.

io.github.patwalls/slope-mcp

In its own words, on Official MCP Registry:

Proprietary B2B creator-velocity data: ranked board, live breakouts, and audience-growth curves.

How to run each

io.github.abm-dev-git/abm-mcp As a remote MCP server

Claude Code
claude mcp add --transport http abm-mcp https://mcp.abm.dev/mcp

io.github.patwalls/slope-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "SLOPE_API_KEY=<YOUR_SLOPE_API_KEY>" --transport stdio slope-mcp -- npx -y slope-mcp

Requires: SLOPE_API_KEY (secret)

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

Only io.github.abm-dev-git/abm-mcp 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 io.github.abm-dev-git/abm-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.abm-dev-git/abm-mcp · What it can do: io.github.patwalls/slope-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