Is the Rootz Ship Maritime MCP server down?

mcp-registry/global.rootz.ship/maritime · v0.1.0

healthy
Last checked 2026-10-18 08:45 UTC · handshake 246ms

As of 2026-10-18 08:45 UTC, the Rootz Ship Maritime MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 122 outages in 90 days, with a median recovery of 6 minutes.

uptime (30d checks)
98.8%
checks observed
3,651
outages (90d)
122
tools
13

Signed global shipping & commodity data: oil, LNG, grain, sanctions, fleet, emissions.

Install Rootz Ship Maritime MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http rootz-ship-maritime-mcp-server https://ship.rootz.global/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "rootz-ship-maritime-mcp-server": {
      "type": "http",
      "url": "https://ship.rootz.global/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 5 warning(s) across 13 tool(s); ~1,520 tokens of tool definitions.
Scores higher than 2% of 15,363 MCP servers Glimind has audited.
Its tool list costs an agent ~1,520 tokens per session — lighter than 60% of servers.
67 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions47
Safety hints30
Token cost100
Client compatibility70
Protocol40
Reliability60
Stability100

What to fix (6)

13 of 13 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: shipping_chokepoint, shipping_country_flows, shipping_doc_intel, shipping_emissions, shipping_fleet and 8 more

21 parameter(s) across 8 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: shipping_country_flows, shipping_emissions, shipping_fleet, shipping_oil_prices, shipping_oil_trade and 3 more

Negotiates MCP 2024-11-05. Structured output, tool output schemas and elicitation arrived in 2025-06-18.

Upgrade the MCP SDK and negotiate 2025-06-18 or newer. How to fix →

Reachable 98.8% of the time over the last 30 days; median recovery 6 min.

Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.

Handshake + tools/list takes ~1,657 ms.

Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 3 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 8 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fglobal.rootz.ship%2Fmaritime/fixes

shipping_country_flows 1 change
{
  "name": "shipping_country_flows",
  "description": "Trade partners for a specific country (who they export to / import from). Pass the country as `country` or `query`.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 30
      },
      "query": {
        "type": "string",
        "description": "Alias for country"
      },
      "country": {
        "type": "string"
      },
      "direction": {
        "type": "string",
        "default": "exports"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
shipping_status 1 change
{
  "name": "shipping_status",
  "description": "Database statistics plus per-dataset freshness: how recently each dataset was refreshed by our pipeline, how old its newest record is, and whether it is ok / lagging / stale / empty. Call this to decide how much to trust anything else this server returns.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "annotations": {
    "readOnlyHint": true
  }
}
shipping_top_exporters 1 change
{
  "name": "shipping_top_exporters",
  "description": "Top oil exporting countries by value/volume (a ranking — no query needed). Optional `product` or `query` recognizes a product keyword (crude/refined/lng/coal/iron_ore).",
  "inputSchema": {
    "type": "object",
    "properties": {
      "limit": {
        "type": "integer",
        "default": 20
      },
      "query": {
        "type": "string"
      },
      "product": {
        "type": "string",
        "default": "crude"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/global.rootz.ship/maritime"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/global.rootz.ship/maritime"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fglobal.rootz.ship%2Fmaritime.svg)](https://glimind.com/server/mcp-registry%2Fglobal.rootz.ship%2Fmaritime?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fglobal.rootz.ship%2Fmaritime?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fglobal.rootz.ship%2Fmaritime.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fglobal.rootz.ship%2Fmaritime.svg
   :target: https://glimind.com/server/mcp-registry%2Fglobal.rootz.ship%2Fmaritime?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:fbb5cd0268802492…, first seen 2026-10-17, included at leaf 6531 of 21,099. Version history · verify what your client received.

Tools (13)

Compare: most reliable data servers · most reliable knowledge servers · most reliable database servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Rootz Ship Maritime MCP server down right now?

As of 2026-10-18 08:45 UTC, the Rootz Ship Maritime MCP server is up with a Glimind reliability score of 71/100 (grade C). Over the last 30 days it answered 98.8% of Glimind's liveness checks. It had 122 outages in 90 days, with a median recovery of 6 minutes.

How many tools does Rootz Ship Maritime MCP server provide?

Rootz Ship Maritime MCP server advertises 13 tools, including shipping_chokepoint, shipping_country_flows, shipping_doc_intel, shipping_emissions, shipping_fleet.

How do I install Rootz Ship Maritime MCP server?

Point your MCP client at this streamable-http endpoint: https://ship.rootz.global/mcp

Is the Rootz Ship Maritime MCP server safe to connect to an AI agent?

Glimind scanned all 13 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Rootz Ship Maritime MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.