Rhein-Ruhr Fahrplan MCP vs FreightUtils MCP Server
Rhein-Ruhr Fahrplan MCP is an MCP server published by MarcProe. Marketplaces we read that list it: 1 (Official MCP Registry). FreightUtils MCP Server is an MCP server published by SoapyRED. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  Rhein-Ruhr Fahrplan MCP |   FreightUtils MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.2 Downloads/month (PyPI): 0 Downloads/week (PyPI): 17 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.34.0 Downloads/month (npm): 3 405 Downloads/week (npm): 1 472 Forks (GitHub): 1 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 2.34.0 Downloads/month (npm): 3 405 Downloads/week (npm): 1 472 Forks (GitHub): 1 Stars (GitHub): 8 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 | Rhein-Ruhr Fahrplan MCP | FreightUtils MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-11-06 |
| Where it runs (differs) | On your machine (rhein-ruhr-fahrplan-mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 0 | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/marcproe/rhein-ruhr-fahrplan-mcp | github.com/soapyred/freightutils-mcp |
| Changes in the last 7 days (differs) | 0 | 11 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 46 h ago returned HTTP 405 |
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
Rhein-Ruhr Fahrplan MCP
Public transit data for the Rhein-Ruhr region: live departures, trips, disruptions, GTFS schedules.
FreightUtils MCP Server
Neutral freight reference + validation layer for AI agents: ADR, HS, UN/LOCODE, freight math
How to run each
Rhein-Ruhr Fahrplan MCP As a local MCP server: PyPI package
claude mcp add --transport stdio rhein-ruhr-fahrplan-mcp -- uvx rhein-ruhr-fahrplan-mcpFreightUtils MCP Server As a remote MCP server
claude mcp add --transport http freightutils https://www.freightutils.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only FreightUtils MCP Server has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of Rhein-Ruhr Fahrplan MCP nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
The marketplaces of FreightUtils MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: Rhein-Ruhr Fahrplan MCP · What it can do: FreightUtils MCP Server · Compare two other plugins
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.