ai.petraport/agent-commerce vs handle-mcp
ai.petraport/agent-commerce is an MCP server published by petraport.ai. Marketplaces we read that list it: 1 (Official MCP Registry). handle-mcp is an MCP server published by NJohansen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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 |  ai.petraport/agent-commerce |  handle-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 1.8.0 Forks (GitHub): 17 Stars (GitHub): 141 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 | ai.petraport/agent-commerce | handle-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 141 |
| Forks (GitHub) (differs) | No figure on GitHub | 17 |
| Last release (differs) | Not published | 2026-11-14 |
| Where it runs (differs) | Remote server (petraport.ai/api/agent-commerce/v1/mcp) | On your machine (handle-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/njohansen/handle-mcp |
| Changes in the last 7 days (differs) | 0 | 9 |
| First seen (differs) | 2026-10-11 | 2026-11-08 |
| Endpoint at the last check (differs) | Responded 18 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
ai.petraport/agent-commerce
AI-agent product catalog: search, lookup & purchase routing over verified merchant data.
handle-mcp
Your AI agent fills the cheapest cart at nemlig.com, BilkaToGo and REMA 1000. You pay.
How to run each
ai.petraport/agent-commerce As a remote MCP server
claude mcp add --transport http agent-commerce https://petraport.ai/api/agent-commerce/v1/mcphandle-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio handle-mcp -- uvx handle-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ai.petraport/agent-commerce 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: ai.petraport/agent-commerce · What it can do: handle-mcp · 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.