Ext Ops Panel
Open dashboard
Comparison

Dappier Remote vs CrustAPI Google + LinkedIn Data

Dappier Remote is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). CrustAPI Google + LinkedIn Data is an MCP server published by crustapi.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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

Where each is published
MarketplaceDappier RemoteCrustAPI Google + LinkedIn Data
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.3.2
Downloads/month (npm): 250
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
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

Dappier Remote vs CrustAPI Google + LinkedIn Data
FactDappier RemoteCrustAPI Google + LinkedIn Data
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.dappier.com/mcp)On your machine (crustapi-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 11, secrets among them: 1
Licence (differs)Apache-2.0Not stated
Repository (differs)Not statedgithub.com/crustapi/crustapi-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 403 (42 h ago)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

Dappier Remote

In its own words, on Docker MCP Catalog:

Enable fast, free real-time web search and access premium data from trusted media brands—news, financial markets, sports, entertainment, weather, and more. Build powerful AI agents with Dappier.

CrustAPI Google + LinkedIn Data

In its own words, on Official MCP Registry:

Live Google + public LinkedIn data: search, maps, profiles, companies, jobs. Pay only for results.

How to run each

Dappier Remote As a remote MCP server

Claude Code
claude mcp add --transport http dappier-remote https://mcp.dappier.com/mcp

Requires: DAPPIER_REMOTE_API_KEY (secret)

CrustAPI Google + LinkedIn Data As a local MCP server: npm package

Claude Code
claude mcp add --env "CRUSTAPI_API_KEY=<YOUR_CRUSTAPI_API_KEY>" --transport stdio search -- npx -y crustapi-mcp

Requires: CRUSTAPI_API_KEY (secret)

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

Only Dappier Remote 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 Dappier Remote asks for

  • DAPPIER_REMOTE_API_KEY (secret)

Only CrustAPI Google + LinkedIn Data asks for

  • CRUSTAPI_API_KEY (secret)

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

What it can do: Dappier Remote · What it can do: CrustAPI Google + LinkedIn Data · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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