Home / MCP registry index / io.github.EkuboProtocol/ekubo

Ekubo Protocol

io.github.EkuboProtocol/ekubo in the official MCP registry. Endpoint https://mcp.ekubo.org/mcp. Source: github.com/EkuboProtocol/ekubo-mcp-server.

The registry describes it as: Token and pool data, swap quotes, and unsigned transaction plans for Ekubo and other DeFi protocols.

We read its 99 tools on 2026-11-04. 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 about every two weeks.

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 ekubo https://mcp.ekubo.org/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "ekubo": {
      "url": "https://mcp.ekubo.org/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"ekubo","type":"http","url":"https://mcp.ekubo.org/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

list_tokens export_tokens get_token get_tokens get_quotes_with_plans get_value_transfer_status prepare_ve33_vote prepare_ve33_extend prepare_ve33_stake prepare_ve33_split prepare_ve33_claim_fees prepare_ve33_reinvest prepare_ve33_claim_all_fees prepare_ve33_clear_vote get_ve33_allocations get_stonx_allocation_recommendation prepare_ve33_reallocation get_positions_by_owner get_pool get_pool_liquidity list_pool_keys derive_pool_id decode_pool_config get_position get_position_pool_candidates prepare_lp_position_deposit prepare_lp_position_earnings_claim prepare_lp_position_withdraw prepare_wrap_unwrap prepare_transfers prepare_lp_position_transfer prepare_fix_pool_price prepare_twamm_order prepare_twamm_order_collection prepare_twamm_order_stop prepare_twamm_virtual_orders prepare_auction_create prepare_auction_complete prepare_auction_creator_proceeds prepare_manual_pool_boost prepare_oracle_capacity_expansion prepare_approval_revocations get_rewards_claims_by_owner prepare_rewards_claim prepare_revenue_buybacks prepare_ve33_increase_stake prepare_ve33_merge prepare_ve33_withdraw get_liquidity_opportunities prepare_pool_initialization get_aave_v3_markets prepare_aave_v3_supply prepare_aave_v3_withdraw prepare_aave_v3_borrow prepare_aave_v3_repay prepare_aave_v3_collateral prepare_aave_v3_emode get_morpho_vaults prepare_morpho_vault_deposit prepare_morpho_vault_withdraw and 39 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-11-04): a512a2a0c96c4e0e. 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.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-ekuboprotocol-ekubo/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-ekuboprotocol-ekubo)

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. How tool poisoning works. What we found across the registry. Check another server.

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

The Stall
ai.intuitek.the-stall/the-stall
200 tools, nothing matched
2026-10-22
SAP MCP Server
ai.oobeprotocol.sap.mcp/sap-mcp
200 tools, nothing matched
2026-10-22
Citiview Agent Market
com.citiviewgroup.mcp/agent-market
200 tools, nothing matched
2026-10-26
ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
Apex Edge — x402-paid machine services
dev.pages.nonsynthetic/apex-edge
200 tools, nothing matched
2026-10-23
x402 Factory
io.github.praneeth12098/x402-factory
200 tools, nothing matched
2026-10-26