ilinxa edge vs com.mcparmory/parallel
ilinxa edge is an MCP server published by ilinxa.com. Marketplaces we read that list it: 1 (Official MCP Registry). com.mcparmory/parallel is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  com.mcparmory/parallel | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Downloads/month (npm): 177 Downloads/week (npm): 43 Not marked · First seen |
Listed Version: 1.0.2 Downloads/month (PyPI): 822 Downloads/week (PyPI): 150 Forks (GitHub): 4 Stars (GitHub): 32 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 | ilinxa edge | com.mcparmory/parallel |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 32 |
| Forks (GitHub) (differs) | No figure on GitHub | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (edge.ilinxa.cloud/mcp) | On your machine (mcparmory-parallel) |
| Transport (differs) | Streamable HTTP | stdio |
| 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) | Not stated | github.com/mcparmory/registry |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 30 h ago returned HTTP 405 | 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
ilinxa edge
Run your ilinxa edge projects from an AI agent: content, forms, email, tasks.
com.mcparmory/parallel
Search the web, extract content, and run distributed tasks with AI-powered automation
How to run each
ilinxa edge As a remote MCP server
claude mcp add --transport http edge https://edge.ilinxa.cloud/mcpRequires: ILX_TOKEN (secret)
com.mcparmory/parallel As a local MCP server: PyPI package
claude mcp add --transport stdio parallel -- uvx mcparmory-parallelCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ilinxa edge 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 com.mcparmory/parallel publish no settings it asks for, so we do not compare settings.
What it can do: ilinxa edge · What it can do: com.mcparmory/parallel · 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.