Ext Ops Panel
Open dashboard
Comparison

dfwmetro.net directory vs io.github.seldonframe/mcp

dfwmetro.net directory is an MCP server published by cexplayer01. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.seldonframe/mcp is an MCP server published by seldonframe. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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
Marketplacedfwmetro.net directoryio.github.seldonframe/mcp
Official MCP Registry Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.59.2
Downloads/month (npm): 399
Downloads/week (npm): 46
Forks (GitHub): 26
Stars (GitHub): 63
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

dfwmetro.net directory vs io.github.seldonframe/mcp
Factdfwmetro.net directoryio.github.seldonframe/mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)63 (better)
Forks (GitHub) (differs)0 (worse)26 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (dfwmetro.net/mcp)Remote server or your machine
Transport (differs)Streamable HTTPStreamable HTTP, stdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)github.com/cexplayer01/dfwmetro-mcpgithub.com/seldonframe/seldonframe
Changes in the last 7 days (differs)20
First seen (differs)2026-10-212026-10-11
Endpoint at the last check (differs)not checked yetResponded 4 days ago

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

dfwmetro.net directory

In its own words, on Official MCP Registry:

Verified DFW home-services directory. AI agents submit listings and find bookable pros.

io.github.seldonframe/mcp

In its own words, on Official MCP Registry:

Build, deploy, and sell AI agents for local-service businesses - from your IDE.

How to run each

dfwmetro.net directory As a remote MCP server

Claude Code
claude mcp add --transport http dfwmetro-directory https://dfwmetro.net/mcp

io.github.seldonframe/mcp As a remote MCP server

Claude Code
claude mcp add --transport http io-github-seldonframe-mcp https://mcp.seldonframe.com/v1

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

Only io.github.seldonframe/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 dfwmetro.net directory publish no settings it asks for, so we do not compare settings.

What it can do: dfwmetro.net directory · What it can do: io.github.seldonframe/mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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