redfox-mcp-core vs Railhook
redfox-mcp-core is an MCP server published by redfox-data. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Railhook is an MCP server published by vadymkykalo. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  Railhook |
|---|---|---|
| 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: 3.7.0 Downloads/month (npm): 6 898 Downloads/week (npm): 341 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 3.7.0 Downloads/month (npm): 6 898 Downloads/week (npm): 341 Forks (GitHub): 1 Stars (GitHub): 4 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 | Railhook |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (worse) | 4 (better) |
| Forks (GitHub) (differs) | 2 (better) | 1 (worse) |
| Last release (differs) | 2026-11-04 | Not published |
| Where it runs (differs) | On your machine (redfox-mcp-core) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| 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/vadymkykalo/railhook |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 36 h ago returned HTTP 401 |
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
Railhook
Webhooks for AI agents: send events, manage endpoints, inspect and retry deliveries.
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.
Railhook As a remote MCP server
claude mcp add --transport http railhook https://railhook.io/mcpRequires: RAILHOOK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Railhook 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: Railhook · 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.