Home / MCP registry index / io.github.imokokok/insight-oracle

io.github.imokokok/insight-oracle

io.github.imokokok/insight-oracle in the official MCP registry. Endpoint https://www.oracleinsight.xyz/api/mcp. Source: github.com/imokokok/Insight.

The registry describes it as: Decision-input integrity for onchain AI agents: verify oracle prices before signing a trade.

We read its 62 tools on 2026-10-29. 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 insight-oracle https://www.oracleinsight.xyz/api/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "insight-oracle": {
      "url": "https://www.oracleinsight.xyz/api/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"insight-oracle","type":"http","url":"https://www.oracleinsight.xyz/api/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

assess_rwa_evidence get_robinhood_rwa_instrument get_robinhood_rwa_context get_oracle_price get_consensus_price get_risk_summary get_oracle_health check_liquidation_risk compare_oracle_deviation get_stablecoin_peg get_protocol_risk_params get_symbols recommend_oracle_setup get_stablecoin_list get_oracle_prices_batch get_price_history get_cross_chain_spreads get_wrapped_asset_peg get_protocols get_protocol_oracle_exposure get_feed_freshness get_feeds get_feed_health get_feed_uptime get_reputation_rankings get_provider_reputation get_daily_report get_incidents get_latency get_anomalies get_correlation get_coverage get_metrics get_monad_dex_market get_hanji_monad_market get_base_dex_market get_base_dex_venue_integrations get_aerodrome_slipstream_market prepare_aerodrome_slipstream_swap get_pancakeswap_v3_market prepare_pancakeswap_v3_swap get_quickswap_v2_market get_solana_dex_route get_hyperliquid_perp_market prepare_hyperliquid_perp_order verify_hyperliquid_perp_execution base_lending_guard base_lending_guard_exact_call monad_lending_guard monad_lending_guard_exact_call multichain_evm_lending_guard multichain_evm_lending_guard_exact_call solana_lending_guard loopscale_vault_deposit check_position_safety pre_trade_safety_check oracle_watch oracle_watch_history execution_receipt execution_preflight and 2 more

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/io-github-imokokok-insight-oracle/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-imokokok-insight-oracle)

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.