Is the Mangrove One Mangrove Trader MCP server down?

mcp-registry/io.github.mangrove-one/mangrove-trader · v1.28.0

healthy
Last checked 2026-10-18 21:41 UTC · handshake 115ms

As of 2026-10-18 21:41 UTC, the Mangrove One Mangrove Trader MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.9%
checks observed
3,739
outages (90d)
2
tools
10

Social trading leaderboard. 9 MCP tools, x402 micropayments (USDC on Base).

Install Mangrove One Mangrove Trader MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http mangrove-one-mangrove-trader-mcp-server https://api.mangrovetraders.com/mcp/

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "mangrove-one-mangrove-trader-mcp-server": {
      "type": "http",
      "url": "https://api.mangrovetraders.com/mcp/"
    }
  }
}

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

Agent-readiness: D (65/100)

D (65/100): 1 error(s), 4 warning(s) across 10 tool(s); ~750 tokens of tool definitions.
Scores higher than 1% of 15,312 MCP servers Glimind has audited.
Its tool list costs an agent ~750 tokens per session — lighter than 85% of servers.
65 → 65 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions0
Safety hints12
Token cost100
Client compatibility100
Protocol100
Reliability85
Stability100

What to fix (5)

10 tool(s) have no description.

Describe what each tool does, when to use it and what it returns in one or two sentences. Models choose tools almost entirely from this text. How to fix →

Tools: trader_cancel_last, trader_get_leaderboard, trader_get_trade_history, trader_last_trade, trader_login and 5 more

10 of 10 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: trader_cancel_last, trader_get_leaderboard, trader_get_trade_history, trader_last_trade, trader_login and 5 more

20 parameter(s) across 9 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: trader_cancel_last, trader_get_leaderboard, trader_get_trade_history, trader_last_trade, trader_my_stats and 4 more

1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: trader_cancel_last

Handshake + tools/list takes ~1,630 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.

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 9 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mangrove-one%2Fmangrove-trader/fixes

trader_cancel_last 1 change
{
  "name": "trader_cancel_last",
  "description": "",
  "inputSchema": {
    "type": "object",
    "title": "_cancel_lastArguments",
    "required": [
      "auth_token"
    ],
    "properties": {
      "auth_token": {
        "type": "string",
        "title": "Auth Token"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": true,
    "idempotentHint": true
  }
}
trader_get_leaderboard 1 change
{
  "name": "trader_get_leaderboard",
  "description": "",
  "inputSchema": {
    "type": "object",
    "title": "_get_leaderboardArguments",
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 100
      },
      "payment": {
        "type": "string",
        "title": "Payment",
        "default": ""
      },
      "timeframe": {
        "type": "string",
        "title": "Timeframe",
        "default": "all_time"
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
trader_get_trade_history 1 change
{
  "name": "trader_get_trade_history",
  "description": "",
  "inputSchema": {
    "type": "object",
    "title": "_get_trade_historyArguments",
    "required": [
      "twitter_handle"
    ],
    "properties": {
      "limit": {
        "type": "integer",
        "title": "Limit",
        "default": 0
      },
      "payment": {
        "type": "string",
        "title": "Payment",
        "default": ""
      },
      "auth_token": {
        "type": "string",
        "title": "Auth Token",
        "default": ""
      },
      "twitter_handle": {
        "type": "string",
        "title": "Twitter Handle"
      }
    }
  },
  "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/io.github.mangrove-one/mangrove-trader"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.mangrove-one/mangrove-trader"}) 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%2Fio.github.mangrove-one%2Fmangrove-trader.svg)](https://glimind.com/server/mcp-registry%2Fio.github.mangrove-one%2Fmangrove-trader?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mangrove-one%2Fmangrove-trader?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mangrove-one%2Fmangrove-trader.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mangrove-one%2Fmangrove-trader.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.mangrove-one%2Fmangrove-trader?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:ca09437700d26b61…, first seen 2026-10-17, included at leaf 5475 of 23,477. Version history · verify what your client received.

Tools (10)

Compare: most reliable other servers · most reliable retrieval servers · most reliable finance servers · most reliable data servers · most reliable search 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 Mangrove One Mangrove Trader MCP server down right now?

As of 2026-10-18 21:41 UTC, the Mangrove One Mangrove Trader MCP server is up with a Glimind reliability score of 90/100 (grade A). Over the last 30 days it answered 99.9% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Mangrove One Mangrove Trader MCP server provide?

Mangrove One Mangrove Trader MCP server advertises 10 tools, including trader_cancel_last, trader_get_leaderboard, trader_get_trade_history, trader_last_trade, trader_login.

How do I install Mangrove One Mangrove Trader MCP server?

Point your MCP client at this streamable-http endpoint: https://api.mangrovetraders.com/mcp/

Is the Mangrove One Mangrove Trader MCP server safe to connect to an AI agent?

Glimind scanned all 10 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 Mangrove One Mangrove Trader 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.

Feedback
Help us improve