Robinhood Chain (madeonsol) MCP Server

mcp-server-robinhood-chain npm v0.8.2

Published by madeonsol — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for the MadeOnSol Robinhood Chain (chain id 4663) API — EVM-native on-chain trading intelligence for AI agents. Live KOL trades, DEX trade tape, token discovery/bundles/candles, deployer reputation, and smart-money wallets. Use from Claude, Cur

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Sensitive-source and external-sink co-existMTC-FLOW-004

Tools that read sensitive data ([rhc_token_flow]) and tools that can send data out ([rhc_copytrade_update, rhc_copytrade_signals, rhc_price_alerts_update, rhc_coordination_alerts_update, rhc_first_touch_subscriptions_create]) are exposed together. An agent can move private data to the sink.

Evidence: sources [rhc_token_flow] → sinks [rhc_copytrade_update, rhc_copytrade_signals, rhc_price_alerts_update, rhc_coordination_alerts_update, rhc_first_touch_subscrip

Fix: Keep secret-reading and egress capabilities on separate, separately-approved servers.

Location: flow rhc_token_flow → rhc_copytrade_update

Tools 64

Each tool and what it can reach — statically extracted from the published source.

  • rhc_coordination_alerts_updatenetwork egress
  • rhc_copytrade_signalsnetwork egress
  • rhc_copytrade_updatenetwork egress
  • rhc_first_touch_subscriptions_createnetwork egress
  • rhc_price_alerts_updatenetwork egress
  • rhc_token_flowreads sensitive data
  • rhc_alpha_walletsno sensitive capability
  • rhc_coordination_alerts_createno sensitive capability
  • rhc_coordination_alerts_deleteno sensitive capability
  • rhc_coordination_alerts_getno sensitive capability
Show 54 more tools ↓
  • rhc_coordination_alerts_listno sensitive capability
  • rhc_copytrade_createno sensitive capability
  • rhc_copytrade_deleteno sensitive capability
  • rhc_copytrade_getno sensitive capability
  • rhc_copytrade_listno sensitive capability
  • rhc_deployer_alertsno sensitive capability
  • rhc_deployer_best_tokensno sensitive capability
  • rhc_deployer_historyno sensitive capability
  • rhc_deployer_leaderboardno sensitive capability
  • rhc_deployer_profileno sensitive capability
  • rhc_deployer_statsno sensitive capability
  • rhc_deployer_tokensno sensitive capability
  • rhc_deployer_trajectoryno sensitive capability
  • rhc_equitiesno sensitive capability
  • rhc_first_touch_subscriptions_deleteno sensitive capability
  • rhc_first_touch_subscriptions_getno sensitive capability
  • rhc_first_touch_subscriptions_listno sensitive capability
  • rhc_first_touch_subscriptions_updateno sensitive capability
  • rhc_kol_coordinationno sensitive capability
  • rhc_kol_feedno sensitive capability
  • rhc_kol_first_touchesno sensitive capability
  • rhc_kol_hot_tokensno sensitive capability
  • rhc_kol_leaderboardno sensitive capability
  • rhc_kol_profileno sensitive capability
  • rhc_lp_eventsno sensitive capability
  • rhc_price_alerts_createno sensitive capability
  • rhc_price_alerts_deleteno sensitive capability
  • rhc_price_alerts_eventsno sensitive capability
  • rhc_price_alerts_getno sensitive capability
  • rhc_price_alerts_listno sensitive capability
  • rhc_recent_bondsno sensitive capability
  • rhc_tokenno sensitive capability
  • rhc_token_batchno sensitive capability
  • rhc_token_batch_buyer_qualityno sensitive capability
  • rhc_token_bundleno sensitive capability
  • rhc_token_buyer_qualityno sensitive capability
  • rhc_token_candlesno sensitive capability
  • rhc_token_holdersno sensitive capability
  • rhc_token_kol_consensusno sensitive capability
  • rhc_token_peak_historyno sensitive capability
  • rhc_token_riskno sensitive capability
  • rhc_token_top_tradersno sensitive capability
  • rhc_tokensno sensitive capability
  • rhc_tradesno sensitive capability
  • rhc_walletno sensitive capability
  • rhc_wallet_pnlno sensitive capability
  • rhc_wallet_positionsno sensitive capability
  • rhc_wallet_tracker_addno sensitive capability
  • rhc_wallet_tracker_listno sensitive capability
  • rhc_wallet_tracker_relabelno sensitive capability
  • rhc_wallet_tracker_removeno sensitive capability
  • rhc_wallet_tracker_summaryno sensitive capability
  • rhc_wallet_tracker_tradesno sensitive capability
  • rhc_wallet_tradesno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.8.2 latest A 93/100 1 1.13.0 2026-09-07
v0.8.1 A 93/100 1 1.13.0 2026-08-31
v0.8.0 A 93/100 1 1.13.0 2026-08-27
v0.6.0 A 93/100 1 1.12.1 2026-08-16
v0.5.0 A 93/100 1 1.12.1 2026-08-15
Show 5 more versions ↓
v0.4.0 A 93/100 1 1.12.1 2026-08-12
v0.3.1 A 96/100 0 1.12.1 2026-08-02
v0.2.2 A 99/100 0 1.12.1 2026-07-29
v0.2.0 A 99/100 0 1.12.1 2026-07-27
v0.1.2 A 99/100 0 1.10.0 2026-07-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-server-robinhood-chain/badge.svg)](https://mcptrustchecker.com/registry/mcp-server-robinhood-chain)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-server-robinhood-chain"><img src="https://mcptrustchecker.com/registry/mcp-server-robinhood-chain/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-server-robinhood-chain/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-server-robinhood-chain --online

Use the free API → How scoring works

Other implementations of Robinhood Chain 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Cloud & DevOps