Ext Ops Panel
Open dashboard
Comparison

io.github.abhiyoheswaran1/baseframelabs-catalogue vs m-dev-tools

io.github.abhiyoheswaran1/baseframelabs-catalogue is an MCP server published by abhiyoheswaran1. Marketplaces we read that list it: 1 (Official MCP Registry). m-dev-tools is an MCP server published by m-dev-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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.abhiyoheswaran1/baseframelabs-cataloguem-dev-tools
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.2.4
Downloads/month (PyPI): 49
Downloads/week (PyPI): 22
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

io.github.abhiyoheswaran1/baseframelabs-catalogue vs m-dev-tools
Factio.github.abhiyoheswaran1/baseframelabs-cataloguem-dev-tools
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.baseframelabs.com)On your machine (m-dev-tools-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/m-dev-tools/m-dev-tools-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 7 days agono 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.abhiyoheswaran1/baseframelabs-catalogue

In its own words, on Official MCP Registry:

Agent-native catalogue of Baseframe Labs dev tools and MCP servers.

m-dev-tools

In its own words, on Official MCP Registry:

MCP server wrapping the m-dev-tools catalog: route_intent, describe, verify.

How to run each

io.github.abhiyoheswaran1/baseframelabs-catalogue As a remote MCP server

Claude Code
claude mcp add --transport http baseframelabs-catalogue https://mcp.baseframelabs.com

m-dev-tools As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio m-dev-tools-mcp -- uvx m-dev-tools-mcp

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

Only io.github.abhiyoheswaran1/baseframelabs-catalogue 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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.abhiyoheswaran1/baseframelabs-catalogue · What it can do: m-dev-tools · 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