Home / MCP registry index / io.github.0xSardius/solenrich

io.github.0xSardius/solenrich

io.github.0xSardius/solenrich in the official MCP registry. Endpoint https://api.solenrich.com/mcp. Source: github.com/0xSardius/solenrich.

The registry describes it as: Solana onchain intelligence for AI agents: wallet risk, due-diligence, perps funding, smart money.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

claude mcp add --transport http solenrich https://api.solenrich.com/mcp

{
  "mcpServers": {
    "solenrich": {
      "url": "https://api.solenrich.com/mcp"
    }
  }
}

code --add-mcp '{"name":"solenrich","type":"http","url":"https://api.solenrich.com/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

enrich_wallet enrich_token parse_transaction whale_watch due_diligence wallet_graph wallet_link_check copy_trade_signals batch_enrich compare_tokens compare_wallets token_trend wallet_history portfolio_history new_tokens protocol_profile query perps_market_structure perps_trader_profile hyperliquid_trader_profile hyperliquid_smart_money perps_basis_signal perps_market_trend perps_venue_comparison perps_cross_venue_funding trending_signals smart_money_flow smart_money_trenches runner_scan feed_latest check_alerts consensus_signal trenches_check exit_signal trenches_scan attention_momentum gacha_ev_scan stonk_pairs stonk_reward_risk stonk_yield stonk_alerts stonk_yield_batch stonk_screener stonk_gems stonk_launch_intel stonk_preflight stonk_quote stonk_market_pulse stonk_creator

Run this server? Show the check in your README

The badge reflects the latest weekly read:

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-0xsardius-solenrich/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-0xsardius-solenrich)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Crypto and Web3 MCP servers