io.github.drfccv/mcp-server-12306 vs treg.to
io.github.drfccv/mcp-server-12306 is an MCP server published by drfccv. Marketplaces we read that list it: 1 (Official MCP Registry). treg.to is an MCP server published by superdesigndev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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.drfccv/mcp-server-12306 |  treg.to |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.1 Downloads/month (PyPI): 1 318 Downloads/week (PyPI): 225 Forks (GitHub): 59 Stars (GitHub): 414 Not marked · First seen |
Listed Version: 0.14.0 Forks (GitHub): 519 Stars (GitHub): 6 067 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.drfccv/mcp-server-12306 | treg.to |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 414 (worse) | 6 067 (better) |
| Forks (GitHub) (differs) | 59 (worse) | 519 (better) |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | On your machine (mcp-server-12306) | Remote server (treg.to/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not a bundle | 6 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/drfccv/mcp-server-12306 | github.com/superdesigndev/treg |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 307 (4 days 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
io.github.drfccv/mcp-server-12306
An MCP server that provides 12306 ticket query
treg.to
OpenRouter for tools and data. Compare catalog providers and call them from one hosted MCP endpoint.
How to run each
io.github.drfccv/mcp-server-12306 As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-server-12306 -- uvx mcp-server-12306treg.to As a remote MCP server
claude mcp add --transport http treg https://treg.to/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only treg.to 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.drfccv/mcp-server-12306 · What it can do: treg.to · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.