Apify vs Infrawise
Apify is a plugin bundle for AI coding tools published by Apify. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Infrawise is an MCP server published by Sidd27. Marketplaces we read that list it: 3 (Official MCP Registry, npm registry (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-21. 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 |  Apify |  Infrawise |
|---|---|---|
| Community marketplace apify/apify-claude-code-plugin | Listed Version: 1.0.2 Forks (GitHub): 2 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 026 Downloads/week (npm): 100 Forks (GitHub): 5 Stars (GitHub): 22 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.0 Downloads/month (npm): 1 026 Downloads/week (npm): 100 Forks (GitHub): 5 Stars (GitHub): 22 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 | Apify | Infrawise |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 7 (worse) | 22 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 5 (better) |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (infrawise) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 7 | 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/apify/apify-claude-code-plugin | github.com/sidd27/infrawise |
| Changes in the last 7 days (differs) | 3 | 4 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago, requires a key | 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
Apify
Run ready-made Actors from Apify, the largest marketplace of tools for AI, or build and publish your own.
Infrawise
Live AWS, database & Kafka infrastructure context for AI coding assistants via MCP.
How to run each
Apify As a Claude Code plugin
/plugin marketplace add apify/apify-claude-code-plugin
/plugin install apify@apifyInfrawise As a local MCP server: npm package
claude mcp add --transport stdio infrawise -- npx -y infrawiseCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Apify 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: Apify · What it can do: Infrawise · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.