io.github.jaimenbell/mcp-factory vs Example App
io.github.jaimenbell/mcp-factory is an MCP server published by jaimenbell. Marketplaces we read that list it: 1 (Official MCP Registry). Example App is an MCP server published by mctx-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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.jaimenbell/mcp-factory | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.3 Downloads/month (PyPI): 110 Downloads/week (PyPI): 36 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.3.4 No figure published 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.jaimenbell/mcp-factory | Example App |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (jaimenbell-mcp-factory) | Remote server (example-app.mctx.ai/v1.3.4) |
| Transport (differs) | stdio | SSE |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/jaimenbell/mcp-factory | github.com/mctx-ai/example-app |
| 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 | Not responding since 2026-10-15 |
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.jaimenbell/mcp-factory
Manifest-driven MCP server scaffolder and runtime hub for tool integrations.
Example App
Build complete Apps with our framework — study or fork this reference implementation. Covers all @mc
How to run each
io.github.jaimenbell/mcp-factory As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-factory -- uvx jaimenbell-mcp-factoryExample App As a remote MCP server
claude mcp add --transport sse example-app https://example-app.mctx.ai/v1.3.4Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Example App 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: io.github.jaimenbell/mcp-factory · What it can do: Example App · 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.