Ext Ops Panel
Open dashboard
Comparison

Supadata vs Instagram Agent by Nova (CIVAI)

Supadata is an MCP server published by supadata-ai. Marketplaces we read that list it: 2 (Docker MCP Catalog, Official MCP Registry). Instagram Agent by Nova (CIVAI) is an MCP server published by nova.civai.co. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplaceSupadataInstagram Agent by Nova (CIVAI)
Docker MCP Catalog Listed
Version: sha256:a8a78f1b81a8
Forks (GitHub): 10
Stars (GitHub): 63
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 1.3.2
Forks (GitHub): 10
Stars (GitHub): 63
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

Supadata vs Instagram Agent by Nova (CIVAI)
FactSupadataInstagram Agent by Nova (CIVAI)
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)63No figure on GitHub
Forks (GitHub) (differs)10No figure on GitHub
Last release (differs)2026-10-17Not published
Where it runs (differs)Remote server or your machineRemote server (nova.civai.co/mcp/agents/instagram-web-agent)
Transport (differs)stdio, Streamable HTTPStreamable HTTP
Tools it declares (differs)6Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/supadata-ai/mcpNot stated
Changes in the last 7 days (differs)50
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 13 h ago, requires a keyResponded 41 h 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

Supadata

In its own words, on Docker MCP Catalog:

Official Supadata MCP Server - Adds powerful video & web scraping to Cursor, Claude and any other LLM clients.

Instagram Agent by Nova (CIVAI)

In its own words, on Official MCP Registry:

I use your Instagram Web browser session (Integrations → Instagram Web) via instagrapi, not Meta /…

How to run each

Supadata As a local MCP server: Docker image

Claude Code
claude mcp add --env "SUPADATA_API_KEY=<YOUR_SUPADATA_API_KEY>" --transport stdio supadata -- docker run -i --rm -e SUPADATA_API_KEY ghcr.io/supadata-ai/mcp

Requires: SUPADATA_API_KEY (secret)

Instagram Agent by Nova (CIVAI) As a remote MCP server

Claude Code
claude mcp add --transport http instagram-web-agent https://nova.civai.co/mcp/agents/instagram-web-agent

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

The marketplaces of Instagram Agent by Nova (CIVAI) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Instagram Agent by Nova (CIVAI) publish no settings it asks for, so we do not compare settings.

What it can do: Supadata · What it can do: Instagram Agent by Nova (CIVAI) · 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