analyze.recent_interactions — ChainRay MCP Tool
analyze.recent_interactions
(analyze recent interactions) is one of 79 tools on the
ChainRay
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call analyze.recent_interactions from your client
- Claude Code ChainRay analyze.recent_interactions run in your project directory
- Claude Desktop ChainRay analyze.recent_interactions ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ChainRay analyze.recent_interactions ~/.cursor/mcp.json
- VS Code ChainRay analyze.recent_interactions .vscode/mcp.json
- Zed ChainRay analyze.recent_interactions ~/.config/zed/settings.json
- Windsurf ChainRay analyze.recent_interactions ~/.codeium/windsurf/mcp_config.json
- Cline ChainRay analyze.recent_interactions ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ChainRay analyze.recent_interactions ~/.gemini/settings.json
- Grok ChainRay analyze.recent_interactions .mcp.json (in your project root)
- ChatGPT ChainRay analyze.recent_interactions Settings → Connectors → Advanced → Developer mode
- Claude.ai ChainRay analyze.recent_interactions Settings → Connectors → Add custom connector
- LangChain ChainRay analyze.recent_interactions pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http chainray https://chainray.online/mcpOther tools on this server
- monitor.whale.alerts
- token.risk
- gas.tracker
- token.price
- wallet.profile
- token.trending
- defi.yields
- nft.collection
- nft.metadata
- chain.bridge.monitor
- 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
- util.context_brief
- agent.card.register
- agent.card.discover
- agent.card.lookup
- security.mev.shield
- market.solver_feed
- token.sentiment
- util.workflow_brief
- agent.erc8004
- util.intent_router
- util.verify_proof
- monitor.watch.address
- monitor.watch.diff
- predict.gas
- predict.whale_move
- predict.liquidity
- predict.token_momentum
- security.mev.intel
- util.stream_info
This list was read from the server itself, by connecting to it and calling tools/list on 2 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.