MangroveTrader

io.github.mangrove-onePublished by GitHub account mangrove-onev1.0.0Updated Oct 11, 2026

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

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

A social trading leaderboard MCP server that exposes nine tools and charges per call via x402 micropayments in USDC on Base.

What you can do
MangroveTrader is a remote MCP server for a social trading leaderboard. According to its registry description, it exposes nine MCP tools and uses x402 micropayments settled in USDC on Base. No tool list, README, or authentication details are provided, so the exact capabilities of the nine tools are not documented here.
When to use it
Consider it if an assistant needs leaderboard-style social trading data and you are willing to pay per request through x402 micropayments. Because the tool list is undocumented, it is hard to judge fit before connecting.
Requirements
A remote MCP client that can reach the streamable HTTP endpoint at No packages, environment variables, headers, or authentication are declared. Calls involve x402 micropayments in USDC on Base, so a funded wallet or payment-capable client is implied.
Before you install
The server charges per call through x402 micropayments in USDC on Base, which means real spending and wallet interaction; set limits before use. No authentication is declared, and no tool list or README is available, so what each tool does and what data leaves your machine cannot be verified from the provided material.

Installation

In SourceWeft

  1. Open MangroveTrader in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.mangrove-one%2Fmangrove-trader/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "mangrovetrader": {
      "type": "http",
      "url": "https://api.mangrovetraders.com/mcp/"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.