Home / MCP registry index / io.github.seekdaseek/agentfeed

AgentFeed

io.github.seekdaseek/agentfeed in the official MCP registry. Endpoint https://x402.ochinimus.app/mcp. Source: github.com/seekdaseek/agentfeed.

The registry describes it as: Crypto briefs and data, Solana pre-trade checks, sanctions, papers, NLP. 93 tools, USDC, 20 chains.

We read its 93 tools on 2026-10-30. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

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 agentfeed https://x402.ochinimus.app/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "agentfeed": {
      "url": "https://x402.ochinimus.app/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"agentfeed","type":"http","url":"https://x402.ochinimus.app/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

get_liq_pulse get_perp get_funding_pulse get_liquidation_leaders get_cascade_scan get_liq_heatmap get_squeeze_score get_cascade_forecast_free get_forecast_record get_cascade_forecast get_open_interest get_funding_rate get_sol_price get_btc_price get_fear_greed get_market_snapshot get_wallet_holdings get_token_metadata get_recent_liquidations get_cascade_alert get_forecast_question get_liquidation_stats get_last_liquidation get_positioning get_trade_context get_token_risk get_exit_method get_liq_history get_cascade_history get_venue_liq_share get_funding_extremes get_funding_radar get_market_state get_macro_calendar get_tradfi_radar get_equity_24h get_oi_spike_scan get_basis get_volatility get_funding_history get_top_movers get_orderbook_imbalance get_orderbook_walls get_token_holders get_wallet_activity get_priority_fees get_jito_tips get_sol_network get_peg_deviation get_peg_sessions get_peg_universe get_exit_quote get_eth_price get_base_gas get_base_balance get_honeypot_check get_base_launches get_hl_whales get_web_markdown get_pdf_markdown and 33 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-seekdaseek-agentfeed/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-seekdaseek-agentfeed)

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.

Crypto and Web3 MCP servers