abm-dev vs MX Probe
abm-dev is a plugin bundle for AI coding tools published by abm.dev. Marketplaces we read that list it: 1 (Community GitHub marketplaces). MX Probe is an MCP server published by mxprobe.dev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
| Marketplace |  MX Probe | |
|---|---|---|
| Community marketplace abm-dev-git/abm-mcp | Listed Version: 0.1.0-47ab19d9 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.6 Downloads/month (npm): 893 Downloads/week (npm): 59 Forks (GitHub): 0 Stars (GitHub): 2 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
| Fact | abm-dev | MX Probe |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.abm.dev/mcp) | On your machine (mxprobe) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 2 | 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/abm-dev-git/abm-mcp | github.com/andrewchmr/mxprobe |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 2 h ago, requires a key | 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
abm-dev
Enrich B2B people & companies with cited multi-source data (verified work emails, LinkedIn, firmographics, AI research), search/source people at target accounts, and write results back to your CRM. Bundles the abm.dev skill and the MCP connector — zero-paste install.
MX Probe
Email verification for AI agents: send, hold or kill with the reason. Signup and credits by API.
How to run each
abm-dev As a Claude Code plugin
/plugin marketplace add abm-dev-git/abm-mcp
/plugin install abm-dev@abm-devMX Probe As a local MCP server: npm package
claude mcp add --env "MXPROBE_API_KEY=<YOUR_MXPROBE_API_KEY>" --transport stdio mxprobe -- npx -y mxprobe mcpRequires: MXPROBE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only abm-dev 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 abm-dev publish no settings it asks for, so we do not compare settings.
What it can do: abm-dev · What it can do: MX Probe · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.