Home / MCP registry index / online.chainray/chainray

ChainRay

online.chainray/chainray in the official MCP registry. Endpoint https://chainray.online/mcp.

The registry describes it as: Multi-chain on-chain intelligence for AI agents through a public remote MCP server.

We read its 79 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

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

Claude Code

claude mcp add --transport http chainray https://chainray.online/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "chainray": {
      "url": "https://chainray.online/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"chainray","type":"http","url":"https://chainray.online/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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

monitor.whale.alerts token.risk gas.tracker token.price wallet.profile token.trending defi.yields nft.collection nft.metadata chain.bridge.monitor analyze.recent_interactions security.contract.scan gas.history security.contract.events security.mev.detect defi.compare token.screener defi.liquidity util.governance market.stablecoin.monitor gas.predict defi.tvl token.holders defi.farming monitor.flashloan monitor.liquidation token.approval util.multi_sig util.ens_resolve market.overview chain.compare wallet.portfolio wallet.smart_money wallet.credit_score analyze.risk_dashboard chain.bridge.flow defi.health nft.floor chain.cross security.sandwich token.unlock gas.optimize defi.aggregator wallet.labels token.supply chain.block security.contract.verify analyze.tx_decode nft.holders market.dex_trades market.new_pairs market.stablecoin.supply wallet.report chain.health defi.opportunity monitor.whale.tracker oracle.gas_avg oracle.price_feed oracle.chain_status agent.reputation and 19 more

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-30): e0f4082b15bf7d14. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/online-chainray-chainray/badge.svg)](https://lazaretto.dev/mcp-registry/online-chainray-chainray)

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.