Ext Ops Panel
Open dashboard
Comparison

AgentLaunch vs SaaSCity

AgentLaunch is an MCP server published by cracked-collective. Marketplaces we read that list it: 1 (Official MCP Registry). SaaSCity is an MCP server published by saascity.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
MarketplaceAgentLaunchSaaSCity
Official MCP Registry Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 2.0.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

AgentLaunch vs SaaSCity
FactAgentLaunchSaaSCity
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Not statedRemote server (saascity.io/api/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/cracked-collective/agentlaunch-mcpgithub.com/nyyhao/saascity-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 18 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

AgentLaunch

In its own words, on Official MCP Registry:

Plan and run paced startup, SaaS and AI directory launches from your agent, in your own Chrome.

SaaSCity

In its own words, on Official MCP Registry:

Audit your site, pick from 1,600+ launch directories by DR and link type, and list on SaaSCity.

How to run each

AgentLaunch

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

SaaSCity As a remote MCP server

Claude Code
claude mcp add --transport http saascity https://saascity.io/api/mcp

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

Only SaaSCity 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: AgentLaunch · What it can do: SaaSCity · 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