MangroveTrader

Server Details

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

If you are the author of this connector, you can claim ownership with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.

Status: Healthy
Uptime: 99.9% over 37 days
Last Tested: 2026-09-23 09:46
Transport: Streamable HTTP · MCP 2025-11-25
URL

TDQS

D1.8/5.0

Scored 2026-09-11 07:51 across 10 tools

Disambiguation3/5

Most tools target distinct actions or resources, such as watch/unwatch, login, search_trader, and get_leaderboard. However, trader_my_stats and trader_performance_report likely overlap in meaning, and trader_last_trade vs trader_get_trade_history could be confused without descriptions. Empty tool descriptions worsen the ambiguity.

Naming Consistency4/5

All tools use the same trader_ prefix and snake_case, which is a clear consistent convention. The structure is not uniformly verb_noun, mixing verbs, nouns, and adjective phrases like trader_my_stats and trader_last_trade, but it remains readable.

Tool Count5/5

The server has 10 tools, which is well within the typical 3-15 range for a focused API. This count seems appropriate for a trader/social-trading surface without obvious bloat.

Completeness3/5

The surface covers login, searching, watching, leaderboard, trade history, stats, and canceling a last action. However, it lacks obvious operations like listing watched traders, placing a trade, or retrieving a portfolio, which are notable gaps for a trading-oriented server.

Available Tools

10 tools

trader_cancel_lastDInspect

ParametersJSON Schema

Name	Required	Description	Default
`auth_token`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_get_leaderboardDInspect

ParametersJSON Schema

Name	Required	Default
`limit`	No
`payment`	No
`timeframe`	No	all_time

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_get_trade_historyDInspect

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`payment`	No
`auth_token`	No
`twitter_handle`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_last_tradeDInspect

ParametersJSON Schema

Name	Required	Description	Default
`twitter_handle`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_loginDInspect

ParametersJSON Schema

Name	Required	Description	Default
No parameters

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_my_statsDInspect

ParametersJSON Schema

Name	Required	Description	Default
`auth_token`	Yes
`twitter_handle`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_performance_reportDInspect

ParametersJSON Schema

Name	Required	Description	Default
`timeframe`	No		all_time
`auth_token`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_search_traderDInspect

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No
`query`	Yes
`payment`	No

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_unwatchDInspect

ParametersJSON Schema

Name	Required	Description	Default
`auth_token`	Yes
`target_handle`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trader_watchDInspect

ParametersJSON Schema

Name	Required	Description	Default
`auth_token`	Yes
`target_handle`	Yes

Output Schema

ParametersJSON Schema

Name	Required	Description
`result`	Yes

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

7 tool updatesApr 10, 2026

Changedtrader_cancel_last3 fields changed

addedInput schema / properties / auth_token

Added value: +{
+  "title": "Auth Token",
+  "type": "string"
+}

removedInput schema / properties / twitter_handle

Removed value: -{
-  "title": "Twitter Handle",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "twitter_handle"
-]New value: +[
+  "auth_token"
+]

Changedtrader_get_trade_history2 fields changed

addedInput schema / properties / auth_token

Added value: +{
+  "default": "",
+  "title": "Auth Token",
+  "type": "string"
+}

removedInput schema / properties / requester_handle

Removed value: -{
-  "default": "",
-  "title": "Requester Handle",
-  "type": "string"
-}

Addedtrader_login
Changedtrader_my_stats5 fields changed
- addedInput schema / properties / auth_token
```
Added value: +{
+  "title": "Auth Token",
+  "type": "string"
+}
```
- addedInput schema / properties / twitter_handle / anyOf
```
Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
```
- addedInput schema / properties / twitter_handle / default
```
Added value: +null
```
- removedInput schema / properties / twitter_handle / type
```
Removed value: -"string"
```
- changedInput schema / required
```
Previous value: -[
-  "twitter_handle"
-]New value: +[
+  "auth_token"
+]
```

Changedtrader_performance_report3 fields changed

addedInput schema / properties / auth_token

Added value: +{
+  "title": "Auth Token",
+  "type": "string"
+}

removedInput schema / properties / twitter_handle

Removed value: -{
-  "title": "Twitter Handle",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "twitter_handle"
-]New value: +[
+  "auth_token"
+]

Changedtrader_unwatch3 fields changed

addedInput schema / properties / auth_token

Added value: +{
+  "title": "Auth Token",
+  "type": "string"
+}

removedInput schema / properties / twitter_handle

Removed value: -{
-  "title": "Twitter Handle",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "twitter_handle",
-  "target_handle"
-]New value: +[
+  "auth_token",
+  "target_handle"
+]

Changedtrader_watch3 fields changed

addedInput schema / properties / auth_token

Added value: +{
+  "title": "Auth Token",
+  "type": "string"
+}

removedInput schema / properties / twitter_handle

Removed value: -{
-  "title": "Twitter Handle",
-  "type": "string"
-}

changedInput schema / required

Previous value: -[
-  "twitter_handle",
-  "target_handle"
-]New value: +[
+  "auth_token",
+  "target_handle"
+]

1 tool updateMar 30, 2026
- Changedtrader_performance_report1 field changed
  - changedInput schema / properties / timeframe / default
```
Previous value: -"30d"New value: +"all_time"
```
9 tool updatesMar 26, 2026
- First observedtrader_cancel_last
- First observedtrader_get_leaderboard
- First observedtrader_get_trade_history
- First observedtrader_last_trade
- First observedtrader_my_stats
- First observedtrader_performance_report
- First observedtrader_search_trader
- First observedtrader_unwatch
- First observedtrader_watch

Related MCP Connectors

trabot-intel
io.github.trabotpro
TraBot market intel MCP: regime, spreads, advisor. Paid x402 tools on Base.
Finance Cryptocurrency Blockchain
1
mcp-server A
xyz.lonestaroracle
Paid market-data MCP: crypto, equities, smart-money, macro, wallet PnL. x402 per call on Base.
Cryptocurrency Finance Government Data
62
LION - Trend Intent MCP + Marketplace Visibility Audit A
app.netlify.gleaming-cassata-d41682
x402-paid MCP data: trend feed + visibility audit. USDC/Base. No API key. No PII.
Finance Cryptocurrency Blockchain
52
tollbooth C
io.github.huwhitememes
37 paid x402 MCP tools for OSINT, prediction markets, web intel, and agent security on Base USDC.
Blockchain Security Web Scraping
1042

Related MCP Servers

Alien Plugg x402 MCP Server
Cryptocurrency Blockchain Web3 & Decentralized Tech
michaelhutchings626-hub
A
license
Not graded
quality
B
maintenance
MCP server exposing 10 curated tools for AI agents, providing crypto trading signals, on-chain analysis, and web utilities via pay-per-call x402 endpoints on the Base network.
Updated 2 months ago (2026-08-03 23:38 UTC)
MIT
@praveen030686/data-apis-mcp
Finance Web Scraping Search
yantrix-ai
A
license
A
quality
D
maintenance
22 MCP tools for AI agents: crypto prices and trading signals (53 coins), stock prices and company financials, forex rates and conversion, and web scraping with AI summaries. All powered by x402 USDC micropayments on Base. $0.01-$0.25 per request.
Updated 6 months ago (2026-03-18 12:22 UTC)
22
19 npm
MIT
AgentData MCP Server
Cryptocurrency Blockchain Finance
speteai
A
license
A
quality
B
maintenance
Provides 16 crypto market data tools for MCP-compatible AI clients with x402/USDC micropayments on Base Mainnet.
Updated 22 days ago (2026-09-01 10:03 UTC)
16
12 npm
MIT
carbon-cashmere-mcp
Cryptocurrency Finance AI & Machine Learning
CarbonCashmere
A
license
Not graded
quality
D
maintenance
Crypto intelligence MCP: 104 tools for market data, ML signals, on-chain analytics, derivatives, and Bittensor subnets. Pay-per-call via x402 USDC on Base/Solana/Algorand/Stellar or $9.99/mo API key.
Updated 4 months ago (2026-05-17 11:18 UTC)
MIT

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?