io.github.MetaLift-AI/metalift vs tech.geckovision/surf
io.github.MetaLift-AI/metalift is an MCP server published by MetaLift-AI. Marketplaces we read that list it: 1 (Official MCP Registry). tech.geckovision/surf is an MCP server published by geckovision.tech. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
| Marketplace |  io.github.MetaLift-AI/metalift |  tech.geckovision/surf |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.15 Downloads/month (npm): 817 Downloads/week (npm): 78 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.2.0 Downloads/month (PyPI): 397 Downloads/week (PyPI): 214 Forks (GitHub): 0 Stars (GitHub): 21 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
| Fact | io.github.MetaLift-AI/metalift | tech.geckovision/surf |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 21 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@metalift/mcp) | Remote server (mcp.geckovision.tech/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/metalift-ai/metalift-mcp | github.com/geckovision/gecko-surf |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 32 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
io.github.MetaLift-AI/metalift
Metalift MCP for AI agents: web search (2 credits), scrape, crawl, and map tools
tech.geckovision/surf
Point Gecko at an OpenAPI spec; get first-call-correct, auth-hidden agent tools.
How to run each
io.github.MetaLift-AI/metalift As a local MCP server: npm package
claude mcp add --env "METALIFT_API_KEY=<YOUR_METALIFT_API_KEY>" --env "METALIFT_API_URL=<YOUR_METALIFT_API_URL>" --transport stdio metalift -- npx -y @metalift/mcpRequires: METALIFT_API_KEY (secret), METALIFT_API_URL
tech.geckovision/surf As a remote MCP server
claude mcp add --transport http surf https://mcp.geckovision.tech/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only tech.geckovision/surf 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
The marketplaces of tech.geckovision/surf publish no settings it asks for, so we do not compare settings.
What it can do: io.github.MetaLift-AI/metalift · What it can do: tech.geckovision/surf · 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.