Ext Ops Panel
Open dashboard
Comparison

Lob vs io.github.theYahia/dadata-mcp

Lob is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.theYahia/dadata-mcp is an MCP server published by theYahia. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceLobio.github.theYahia/dadata-mcp
Official MCP Registry Listed
Version: 0.2.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.5
Downloads/month (npm): 218
Downloads/week (npm): 99
Forks (GitHub): 1
Stars (GitHub): 3
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

Lob vs io.github.theYahia/dadata-mcp
FactLobio.github.theYahia/dadata-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)2026-11-02Not published
Where it runs (differs)Remote server (gateway.pipeworx.io/lob/mcp)On your machine (@metarebalance/dadata-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/pipeworx-io/mcp-lobgithub.com/theyahia/dadata-mcp
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 19 h 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

Lob

In its own words, on Official MCP Registry:

Lob MCP — US address verification, bulk verification, and autocompletion (docs.lob.com). BYO-key…

io.github.theYahia/dadata-mcp

In its own words, on Official MCP Registry:

MCP server for DaData.ru — address validation, company lookup, geocoding. 31 tools.

How to run each

Lob As a remote MCP server

Claude Code
claude mcp add --transport http lob https://gateway.pipeworx.io/lob/mcp

Requires: PIPEWORX_API_KEY (secret)

io.github.theYahia/dadata-mcp As a local MCP server: npm package

Claude Code
claude mcp add --env "DADATA_API_KEY=<YOUR_DADATA_API_KEY>" --transport stdio dadata-mcp -- npx -y @metarebalance/dadata-mcp

Requires: DADATA_API_KEY (secret)

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

Only Lob 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

Only Lob asks for

  • PIPEWORX_API_KEY (secret)

Only io.github.theYahia/dadata-mcp asks for

  • DADATA_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Lob · What it can do: io.github.theYahia/dadata-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