Ext Ops Panel
Open dashboard
Comparison

ScrapeField vs HSH Data-on-Demand

ScrapeField is an MCP server published by scrapefield.com. Marketplaces we read that list it: 1 (Official MCP Registry). HSH Data-on-Demand is an MCP server published by hshintelligence. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
MarketplaceScrapeFieldHSH Data-on-Demand
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.1.1
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

ScrapeField vs HSH Data-on-Demand
FactScrapeFieldHSH Data-on-Demand
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (scrapefield.com/mcp)Remote server (api.hshintelligence.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/scrapefield/scrapefieldgithub.com/hshintelligence/data-on-demand
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agoResponded 2 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

ScrapeField

In its own words, on Official MCP Registry:

Google Maps, LinkedIn, Instagram, TikTok and X data as tools. Demo mode needs no key.

HSH Data-on-Demand

In its own words, on Official MCP Registry:

Made-to-order data for AI agents: company intel, B2B contacts, scraping. Pay per call via x402.

How to run each

ScrapeField As a remote MCP server

Claude Code
claude mcp add --transport http scrapefield https://scrapefield.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

HSH Data-on-Demand As a remote MCP server

Claude Code
claude mcp add --transport http data-on-demand https://api.hshintelligence.com/mcp

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

Both endpoints responded at the last daily 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: ScrapeField · What it can do: HSH Data-on-Demand · 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