global.rootz.ship/maritime vs Terminal49
global.rootz.ship/maritime is an MCP server published by ship.rootz.global. Marketplaces we read that list it: 1 (Official MCP Registry). Terminal49 is an MCP server published by Terminal49. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  global.rootz.ship/maritime |   Terminal49 |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 5 Stars (GitHub): 2 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 | global.rootz.ship/maritime | Terminal49 |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 2 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 5 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (ship.rootz.global/mcp) | Remote server (mcp.terminal49.com) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/rootz-global/mcp-servers | github.com/terminal49/api |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 38 h ago | Responded 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
global.rootz.ship/maritime
Signed global shipping & commodity data: oil, LNG, grain, sanctions, fleet, emissions.
Terminal49
Find and monitor ocean shipments and containers, and create new tracking requests.
How to run each
global.rootz.ship/maritime As a remote MCP server
claude mcp add --transport http maritime https://ship.rootz.global/mcpTerminal49 As a remote MCP server
claude mcp add --transport http terminal49 https://mcp.terminal49.comCommands built only from what the marketplaces declare; the full set for every client is on each card.
Both endpoints responded at the last daily 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: global.rootz.ship/maritime · What it can do: Terminal49 · 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.