redfox-mcp-core vs ContextStream MCP Server
redfox-mcp-core is an MCP server published by redfox-data. Marketplaces we read that list it: 1 (PyPI (MCP servers)). ContextStream MCP Server is an MCP server published by contextstream. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-08. 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 |  redfox-mcp-core |   ContextStream MCP Server |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.3.0 Downloads/month (PyPI): 1 980 Downloads/week (PyPI): 635 Forks (GitHub): 2 Stars (GitHub): 2 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.72 Downloads/month (npm): 14 297 Downloads/week (npm): 5 502 Forks (GitHub): 12 Stars (GitHub): 45 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.72 Downloads/month (npm): 14 297 Downloads/week (npm): 5 502 Forks (GitHub): 12 Stars (GitHub): 45 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 | redfox-mcp-core | ContextStream MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 45 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 12 (better) |
| Last release (differs) | 2026-11-04 (worse) | 2026-11-08 (better) |
| Where it runs (differs) | On your machine (redfox-mcp-core) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/redfox-data/redfox-mcp | github.com/contextstream/mcp-server |
| Changes in the last 7 days (differs) | 1 | 20 or more |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 7 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
redfox-mcp-core
Shared runtime for RedFoxHub MCP servers: client management, multi-tenant auth, async task polling, stdio/HTTP serving
ContextStream MCP Server
The context platform for AI agents: code search, team decisions, and grounded project context.
How to run each
redfox-mcp-core
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ContextStream MCP Server As a remote MCP server
claude mcp add --transport http contextstream-mcp-server https://mcp.contextstream.io/mcpRequires: CONTEXTSTREAM_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ContextStream MCP Server 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 redfox-mcp-core publish no settings it asks for, so we do not compare settings.
What it can do: redfox-mcp-core · What it can do: ContextStream MCP Server · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.