Ext Ops Panel
Open dashboard
Comparison

co.servicegraph.mcp/servicegraph vs Untapped Agency Compare

co.servicegraph.mcp/servicegraph is an MCP server published by mcp.servicegraph.co. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). Untapped Agency Compare is an MCP server published by CTF-Max. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. 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
Marketplaceco.servicegraph.mcp/servicegraphUntapped Agency Compare
Official MCP Registry Listed
Version: 0.1.1
Forks (GitHub): 7
Stars (GitHub): 61
Not marked · First seen
Listed
Version: 0.4.0
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

co.servicegraph.mcp/servicegraph vs Untapped Agency Compare
Factco.servicegraph.mcp/servicegraphUntapped Agency Compare
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)61 (better)0 (worse)
Forks (GitHub) (differs)7 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.servicegraph.co)On your machine (https://github.com/CTF-Max/untapped-plugins/releases/download/v0.4.0/untapped-agency-compare-mcp-0.4.0.mcpb)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)19Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/nostrband/servicegraphgithub.com/ctf-max/untapped-plugins
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-23
Endpoint at the last check (differs)No HTTP response at the last check (21 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

co.servicegraph.mcp/servicegraph

In its own words, on Official MCP Registry:

Datasets for founders: directories, newsletters, and agencies, with metrics attached.

Untapped Agency Compare

In its own words, on Official MCP Registry:

Compare agency services and terms with sources

How to run each

co.servicegraph.mcp/servicegraph As a remote MCP server

Claude Code
claude mcp add --transport http servicegraph https://mcp.servicegraph.co

Untapped Agency Compare

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Only co.servicegraph.mcp/servicegraph 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

Neither one's marketplaces publish the settings it asks for.

What it can do: co.servicegraph.mcp/servicegraph · What it can do: Untapped Agency Compare · 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