Ext Ops Panel
Open dashboard
Comparison

Google Review Velocity & Reply Rate Lead Scorer vs Cargo

Google Review Velocity & Reply Rate Lead Scorer is an MCP server published by Nero-Engine. Marketplaces we read that list it: 1 (Official MCP Registry). Cargo is an MCP server published by getcargohq. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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
MarketplaceGoogle Review Velocity & Reply Rate Lead ScorerCargo
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.0.147
Downloads/month (npm): 101 947
Downloads/week (npm): 66 012
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.0.146
Downloads/month (npm): 101 947
Downloads/week (npm): 66 012
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

Google Review Velocity & Reply Rate Lead Scorer vs Cargo
FactGoogle Review Velocity & Reply Rate Lead ScorerCargo
Marketplaces that list it (differs)1 (worse)2 (better)
Last release (differs)Not published2026-11-10
Where it runs (differs)Remote server (mcp.apify.com)Remote server or your machine
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedUNLICENSED
Repository (differs)Not statedgithub.com/getcargohq/cargo
Changes in the last 7 days (differs)09
First seen (differs)2026-11-022026-10-17
Endpoint at the last check (differs)Status out of date: last check 32 h ago returned HTTP 401Status out of date: last check 33 h ago returned HTTP 401

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

Google Review Velocity & Reply Rate Lead Scorer

In its own words, on Official MCP Registry:

Scores Google Maps businesses on review velocity, owner reply rate and unanswered bad reviews

Cargo

In its own words, on Official MCP Registry:

Find and verify work emails, enrich companies and contacts, score leads and sync to your CRM.

How to run each

Google Review Velocity & Reply Rate Lead Scorer

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

Requires: Authorization header

Cargo As a remote MCP server

Claude Code
claude mcp add --transport http cargo https://mcp.getcargo.io/mcp

Requires: CARGO_API_TOKEN (secret)

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

The marketplaces of Google Review Velocity & Reply Rate Lead Scorer publish no settings it asks for, so we do not compare settings.

What it can do: Google Review Velocity & Reply Rate Lead Scorer · What it can do: Cargo · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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