Skip to content
ProtocolProbe
Explore

MCP servers › io.github.EkuboProtocol › ekubo

MCP server · registry snapshot 2026-11-05 · last tested 2026-11-05

ekubo MCP server

Registry name io.github.EkuboProtocol/ekubo

Ekubo Protocol — the publisher's title

by EkuboProtocol · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

Token and pool data, swap quotes, and unsigned transaction plans for Ekubo and other DeFi protocols. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-11-05version 0.54.0TypeScriptstreamable HTTP99 tools

Summary

io.github.EkuboProtocol/ekubo is a remote MCP server listed in the official MCP registry at version 0.54.0, under the namespace of the GitHub account EkuboProtocol. Its linked repository, github.com/EkuboProtocol/ekubo-mcp-server, belongs to the same GitHub account. On 2026-11-05 ProtocolProbe connected to it in read-only mode and read its inventory: 99 tools, 17 resources and 0 prompts.

Record checks

4 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • not met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Repository
public
Tools
99
Last tested
2026-11-05

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-11-05 (mcp.ekubo.org), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (0.54.0).

Add to your client

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-11-05
Mode
read-only (no tool calls)
Latest version
0.54.0, published 2026-11-04 (registry, as of the 2026-11-05 snapshot)
First listed version
2026-11-04 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-11-05
Package and repository
checked 2026-11-05
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-11-04, listed on 2026-11-05 with version 0.54.0 (published 2026-11-04).

Source: the official MCP Registry list on 2026-11-04 and on 2026-11-05.

What it is

What does this server offer?

Observed inventory
99tools
17resources
0prompts

None of its 99 tools are described as changing anything. For 99 the reading was uncertain, so no mark is shown.

  • list_tokenson 16 other servers

    “First step for symbol-based swaps, including tokenized stocks and stablecoins: list canonical Ekubo tokens by descending visibility_priority, so the preferred token wins an ambiguous symbol.”

    Publisher declares: read-only yes

    5 inputs
    • chain_idinteger or string“Restrict the list to one EVM chain; omit to list tokens across every indexed chain”
    • searchstring“Case-insensitive token symbol prefix or suffix match; omit to list the whole canonical set.”
    • min_visibility_priorityinteger“Lowest visibility_priority to include; defaults to 0, the interface threshold.”
    • page_sizeinteger“Maximum tokens to return; defaults to 20”
    • after_tokenstring“Keep only tokens whose (chain_id, address) pair sorts after this <chain_id>:<address> identifier.”
  • export_tokenson 8 other servers

    “Return a token_list_reference envelope (chain ID, address, symbol, name, decimals) and its count, with no entries, so a wallet can import token names; pass it unchanged as the wallet tool's reference…”

    Publisher declares: read-only yes

    2 inputs
    • chain_idinteger or string“Export only this chain; almost always pass it, since a wallet holds names for the chain it is on.”
    • max_tokensinteger“Defaults to 1,000, what a wallet accepts in one import; a larger export is refused whole, not truncated”
  • get_tokenon 23 other servers

    “Fetch canonical token metadata for an exact chain and address.”

    Publisher declares: read-only yes

    2 inputs, 2 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • addressstringrequired“EVM or Starknet token address (hex)”
  • get_tokenson 13 other servers

    “Fetch canonical metadata for up to 1,000 token identifiers in one batch request, preserving input order; identifiers absent from the canonical list are omitted.”

    Publisher declares: read-only yes

    1 input, 1 required
    • tokensarrayrequired“Entries may span chains”
  • get_quotes_with_plans

    “A quote, execution plan, simulation or wallet approval is not permission to trade.”

    Publisher declares: read-only yes

    12 inputs, 5 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • destination_chain_idinteger or string“Destination chain; defaults to chain_id for a same-chain swap”
    • token_instringrequired“Raw EVM address or CAIP-10 eip155:<chain_id>:<address>; all-zeroes denotes the native token”
    • token_outstringrequired“Raw EVM address or CAIP-10 eip155:<chain_id>:<address>; all-zeroes denotes the native token”
    • quote_typestringrequired
    • amountstringrequired“Base units (positive decimal integer)”
    • max_output_lossstring“Exact-input loss budget from quoted output, output-token base units as a decimal integer string; requires sender, omit slippage_bps.”
    • senderstring“Transaction sender; pass with exactly one of slippage_bps or max_output_loss for plans (address)”
    • recipientstring“Defaults to sender (address)”
    • slippage_bpsinteger“Whole-bps calldata bound: 0.1% = 10.”
    • swap_deadline_minutesinteger“Ekubo router route deadline; default 30”
    • include_raw_quotesboolean“Echo raw provider responses; only to diagnose a provider”
  • get_value_transfer_status

    “Report whether an executed LayerZero or LI.FI transfer has been delivered; its origin receipt alone does not mean the user has the funds.”

    Publisher declares: read-only yes

    5 inputs
    • sourcestring“The executed quote's source; defaults to layerzero”
    • quote_idstring“The executed option's provider_quote_id; required for layerzero”
    • transaction_hashstring“Origin transaction hash; required for lifi, and pass it for layerzero once known (some routes need it) (bytes32 hex)”
    • origin_chain_idinteger or string“Origin chain; lifi only, narrows the lookup”
    • destination_chain_idinteger or string“Destination chain; lifi only”
  • prepare_ve33_vote

    “Compile one actively voted ve-token into multiple allocations.”

    Publisher declares: read-only yes

    9 inputs, 9 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • source_ve_idstringrequired“decimal integer”
    • source_amountstringrequired“Base units (positive decimal integer)”
    • current_voteobjectrequired“Required active indexed vote; its pool is claimed unconditionally before any split, clear, or replacement vote”
    • allocationsarrayrequired
    • unallocated_permilleintegerrequired
    • salt_noncestringrequired“User-selected nonce used to derive deterministic, replay-detectable split salts (bytes32 hex)”
  • prepare_ve33_extend

    “Prepare a direct extension for an unvoted VeToken or an atomic claim-and-extend call when current_pool_key identifies an active vote, so pending voter fees are preserved.”

    Publisher declares: read-only yes

    7 inputs, 4 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • ve_idstringrequired“decimal integer”
    • duration_secondsinteger
    • max_durationboolean
    • current_pool_keyobject“Active pool key when voted; the MCP claims fees atomically before extension.”
  • prepare_ve33_stake

    “Create a new VeToken stake with an exact stake-token approval.”

    Publisher declares: read-only yes

    8 inputs, 6 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • stake_tokenstringrequired“address”
    • amountstringrequired“Base units (positive decimal integer)”
    • saltstringrequired“User-selected salt for a deterministic, replay-detectable VeToken ID (bytes32 hex)”
    • duration_secondsinteger
    • max_durationboolean“Defaults to true when duration_seconds is omitted; set false only with an explicit duration_seconds”
  • prepare_ve33_split

    “Split a source ve-token with an explicit salt and return the deterministic child token ID; the source vote is preserved with reduced weight and the child starts unvoted with the same lock end.”

    Publisher declares: read-only yes

    6 inputs, 6 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • ve_idstringrequired“decimal integer”
    • amountstringrequired“Base units (positive decimal integer)”
    • saltstringrequired“bytes32 hex”
  • prepare_ve33_claim_fees

    “Generate one call, or an atomic batch of decodable VeToken steps, claiming voter fees from one or more ve-tokens.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • recipientstring“address”
    • claimsarrayrequired
  • prepare_ve33_reinvest

    “Build the safe phased workflow for 'reinvest my fees': automatically claim all active voter fees, prepare one exact-input swap per claimed non-stake token, then increase one VeToken or every existing…”

    Publisher declares: read-only yes

    13 inputs, 4 required
    • phasestringrequired
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • claimsarray
    • stake_tokenstring“address”
    • fee_balancesarray
    • slippage_bpsinteger
    • swap_deadline_minutesinteger“Ekubo router route deadline; default 30”
    • sourcestring
    • ve_idstring“decimal integer”
    • amountstring“Stake token base units (decimal integer)”
    • current_state_idstring“bytes32 hex”
Show 87 more tools
  • prepare_ve33_claim_all_fees

    “Discover every active vote on VeTokens owned by the sender and generate one atomic batch of decodable VeToken steps claiming all indexed pool fees, with ownerOf and voteState validation calldata.”

    Publisher declares: read-only yes

    4 inputs, 3 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“Owner whose indexed VeTokens and active votes should be discovered (address)”
    • recipientstring“Fee recipient; defaults to sender for claimPoolFeesToSelf (address)”
  • prepare_ve33_clear_vote

    “Remove the active vote from one or more ve-tokens, claiming each stake's current pool fees immediately before its clearVote in one atomic batch.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • recipientstring“Fee recipient; defaults to sender for claimPoolFeesToSelf (address)”
    • votesarrayrequired
  • get_ve33_allocations

    “Use for requests such as 'show all my Ekubo STONX allocations'.”

    Publisher declares: read-only yes

    3 inputs, 1 required
    • chain_idinteger or string“Optional with ve_token; omit both for the production Ekubo STONX deployment”
    • ve_tokenstring“Optional with chain_id; omit both for the canonical STONX VeToken 0x9d7008E169D040B6c0140eb92E7cA82B12643497 (address)”
    • ownerstringrequired“Connected EVM wallet whose complete Ekubo STONX/VeToken allocation should be shown; the server cannot infer 'my', so ask the user when no wallet address is ava…”
  • get_stonx_allocation_recommendation

    “Return a provider-neutral STONX allocation recommendation with an emissions_efficiency KPI per pool and an executable target list (exactly 10,000 bps, at most 25 Ve33 pools).”

    Publisher declares: read-only yes

    4 inputs
    • voterobject“With ve33_emission_state, makes targets voter-optimal”
    • ve33_emission_stateobject“{current_timestamp, current_emission_rate, total_remaining_emissions}: decimal strings decoded locally from getEmissionState (rate is Q32) via local_read_requi…”
    • prune_low_efficiencyboolean“Withhold prune candidates and redistribute their weight”
    • max_emission_share_per_fee_sharenumber“Prune above this emission share / retained fee share; default 3”
  • prepare_ve33_reallocation

    “Compile a reviewed current allocation into at most 25 target pool-weight shares as one atomic batch of decodable VeToken steps.”

    Publisher declares: read-only yes

    7 inputs, 6 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“VeToken owner that will execute the atomic batch (address)”
    • current_state_idstringrequired“Exact state_id returned by get_ve33_allocations; preparation fails if indexed state changed (bytes32 hex)”
    • targetsarrayrequired“At most 25 targets.”
    • salt_noncestringrequired“User-selected nonce for deterministic child VeToken IDs created by required splits (bytes32 hex)”
    • strategystring“Defaults to preserve_existing_locks.”
  • get_positions_by_owner

    “Enumerate an owner's indexed Ekubo position NFTs with pool keys, bounds, liquidity, indexed pool state and rewards.”

    Publisher declares: read-only yes

    5 inputs, 1 required
    • ownerstringrequired“address”
    • chain_idinteger or string“EVM chain ID”
    • statestring
    • page_sizeinteger
    • pageinteger
  • get_poolon 8 other servers

    “Resolve a chain/core/pool ID to its verified PoolKey, decoded config and indexed pool state.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • core_addressstringrequired“address”
    • pool_idstringrequired“Pool ID (decimal or 0x-hex integer)”
  • get_pool_liquidityon 1 other server

    “Return tick-level net liquidity deltas for one exact chain/core/pool ID.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • core_addressstringrequired“address”
    • pool_idstringrequired“Pool ID (decimal or 0x-hex integer)”
  • list_pool_keys

    “Discover initialized pools for one chain and Core deployment, ordered by pool_id with keyset pagination, optionally filtered by token, pair or extension.”

    Publisher declares: read-only yes

    7 inputs, 2 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • core_addressstringrequired“Core deployment (address)”
    • token_astring“Pools containing this token (address)”
    • token_bstring“With token_a, the exact pair (address)”
    • extensionstring“Zero address = extensionless”
    • page_sizeinteger“Pools per page”
    • after_pool_idstring“Previous page's next_after_pool_id (decimal or 0x-hex integer)”
  • derive_pool_id

    “Pack or accept an exact PoolKey config and derive pool_id = keccak256(abi.encode(PoolKey)).”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • pool_keyobjectrequired
  • decode_pool_config

    “Decode the packed bytes32 extension, exact uint64 Q64 fee, concentrated/stableswap discriminator, and tick spacing or stableswap parameters.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • configstringrequired“bytes32 hex”
  • get_positionon 5 other servers

    “Hydrate one owner position: pool key, bounds, liquidity, pool state, NFT metadata, history, rewards, token prices, and a pending read of current principal, fees or Ve33 rewards and owner.”

    Publisher declares: read-only yes

    4 inputs, 4 required
    • ownerstringrequired“Current owner (address)”
    • chain_idinteger or stringrequired“EVM chain ID”
    • positions_addressstringrequired“Ekubo Positions or Ve33Positions manager (address)”
    • token_idstringrequired“Position NFT ID (decimal or 0x-hex integer)”
  • get_position_pool_candidates

    “List indexed pools for a token pair with verified PoolKeys and pool IDs, Core generation, pool type, extension, 24-hour TVL/volume/fee stats and the right Positions or Ve33Positions manager.”

    Publisher declares: read-only yes

    7 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • token_astringrequired“Either order (address)”
    • token_bstringrequired“address”
    • min_tvl_usdnumber“TVL floor; default 0 keeps tiny pools visible”
    • core_addressstring“address”
    • extensionstring“address”
    • pool_typestring
  • prepare_lp_position_deposit

    “Prepare a v3 position mint or add_liquidity, initializing a new pool at initial_tick when requested, with every approval, refund and cleanup step.”

    Publisher declares: read-only yes

    14 inputs, 8 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • core_addressstringrequired“v3 Core address”
    • pool_idstring“Omit when pool_key is supplied (decimal or 0x-hex integer)”
    • pool_keyobject“Required for an uninitialized pool.”
    • pool_initializedboolean“false only for a new pool to initialize here”
    • modestring
    • token_idstring“add_liquidity only (decimal or 0x-hex integer)”
    • tick_lowerintegerrequired
    • tick_upperintegerrequired
    • initial_tickinteger“Uninitialized pool only: initializes at this tick”
    • max_amount0stringrequired“Max token0 base units; 0 for single-sided (decimal integer)”
    • max_amount1stringrequired“Max token1 base units; 0 for single-sided (decimal integer)”
    • slippage_bpsintegerrequired“User-selected liquidity slippage”
  • prepare_lp_position_earnings_claim

    “Prepare collection of all accrued fees from an owned standard position or rewards from an owned Ve33 position, keeping its liquidity and NFT.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“Position owner (address)”
    • positions_addressstringrequired“Positions or Ve33Positions manager (address)”
    • token_idstringrequired“Position NFT ID (decimal or 0x-hex integer)”
    • recipientstring“Defaults to sender (address)”
  • prepare_lp_position_withdraw

    “Prepare partial or full withdrawals from one or more owned positions in one plan, collecting fees or Ve33 rewards and keeping the NFTs.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“Owner of every position (address)”
    • withdrawalsarrayrequired“One entry per position”
  • prepare_wrap_unwrap

    “Prepare a direct wrapped-native deposit or withdrawal on a chain with a verified wrapped native token.”

    Publisher declares: read-only yes

    4 inputs, 4 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • directionstringrequired
    • amountstringrequired“Base units (positive decimal integer)”
  • prepare_transfers

    “Prepare one atomic-capable plan of 1 to 4,096 ordered native, ERC-20, ERC-721 and ERC-1155 transfers on one EVM chain, mixed freely.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“Nonzero owner of every asset (address)”
    • transfersarrayrequired“One to 4096 ordered, optionally mixed native, ERC-20, ERC-721, or ERC-1155 transfers”
  • prepare_lp_position_transfer

    “Prepare the exact safeTransferFrom transaction for an owned LP position and include pending ownership validation.”

    Publisher declares: read-only yes

    5 inputs, 5 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • positions_addressstringrequired“address”
    • token_idstringrequired“decimal or 0x-hex integer”
    • recipientstringrequired“address”
  • prepare_fix_pool_price

    “Run the interface-equivalent phased fix-price workflow: provide exact pending pool-price read calldata, then exact router quote calldata, then approvals and target-price execution calldata.”

    Publisher declares: read-only yes

    9 inputs, 6 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • core_addressstringrequired“address”
    • pool_idstringrequired“decimal or 0x-hex integer”
    • base_tokenstringrequired“Token; zero address = native”
    • target_pricestringrequired
    • pending_current_sqrt_ratiostring“decimal integer”
    • quote_resultobject
    • swap_deadline_minutesinteger“Ekubo router route deadline; default 30”
  • prepare_twamm_order

    “Prepare one or more TWAMM order splits with approvals and native value as one atomic batch.”

    Publisher declares: read-only yes

    8 inputs, 6 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • sell_tokenstringrequired“Token; zero address = native”
    • buy_tokenstringrequired“Token; zero address = native”
    • ordersarrayrequired
    • pending_timestampstringrequired“decimal integer”
    • deadline_secondsinteger
    • saltstring“Fixes the order's token id; omit to derive it from the request.”
  • prepare_twamm_order_collection

    “Prepare collection of every selected order key through the exact current or legacy Orders manager, as one atomic batch of decodable steps, with pending owner validation.”

    Publisher declares: read-only yes

    5 inputs, 5 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • orders_addressstringrequired“address”
    • token_idstringrequired“decimal or 0x-hex integer”
    • order_keysarrayrequired
  • prepare_twamm_order_stop

    “Prepare the interface's complete stop flow: collect every selected order and decrease every still-active sale rate in one atomic batch of decodable steps.”

    Publisher declares: read-only yes

    6 inputs, 6 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • orders_addressstringrequired“address”
    • token_idstringrequired“decimal or 0x-hex integer”
    • pending_timestampstringrequired“decimal integer”
    • ordersarrayrequired
  • prepare_twamm_virtual_orders

    “Prepare the permissionless lockAndExecuteVirtualOrders maintenance call for a current or legacy TWAMM pool.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • pool_keyobjectrequired“PoolKey {token0, token1, config}: token addresses (zero = native), bytes32 config”
  • prepare_auction_create

    “Pack the exact interface auction config and prepare mint plus sellAmountByAuction, including approval or native value and deterministic token ID.”

    Publisher declares: read-only yes

    12 inputs, 12 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • sell_tokenstringrequired“Token; zero address = native”
    • buy_tokenstringrequired“Token; zero address = native”
    • sell_amountstringrequired“Base units (positive decimal integer)”
    • creator_fee_q32stringrequired“decimal integer”
    • min_boost_durationintegerrequired
    • graduation_pool_fee_q64stringrequired“decimal integer”
    • graduation_pool_tick_spacingintegerrequired
    • start_timestringrequired“decimal integer”
    • auction_durationintegerrequired
    • saltstringrequired“bytes32 hex”
  • prepare_auction_complete

    “Prepare permissionless auction completion and, when necessary, graduation-pool initialization in the same atomic batch.”

    Publisher declares: read-only yes

    6 inputs, 5 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • token_idstringrequired“decimal or 0x-hex integer”
    • auction_keyobjectrequired“PoolKey {token0, token1, config}: token addresses (zero = native), bytes32 config”
    • graduation_pool_initializedbooleanrequired
    • launch_pool_tickinteger
  • prepare_auction_creator_proceeds

    “Prepare collection of creator proceeds for an auction NFT with pending owner validation.”

    Publisher declares: read-only yes

    4 inputs, 4 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • token_idstringrequired“decimal or 0x-hex integer”
    • auction_keyobjectrequired“PoolKey {token0, token1, config}: token addresses (zero = native), bytes32 config”
  • prepare_manual_pool_boost

    “Compute the exact Q32 boost rates and prepare all token approvals, native value, and boost calldata used by the interface.”

    Publisher declares: read-only yes

    7 inputs, 7 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • pool_keyobjectrequired“PoolKey {token0, token1, config}: token addresses (zero = native), bytes32 config”
    • start_timestringrequired“Unix seconds (decimal integer)”
    • end_timestringrequired“Unix seconds, after start_time (decimal integer)”
    • amount0stringrequired“Total token0 base units over the boost (decimal integer)”
    • amount1stringrequired“Total token1 base units over the boost (decimal integer)”
  • prepare_oracle_capacity_expansion

    “Prepare the interface's permissionless Oracle expandCapacity call for one ERC-20 token.”

    Publisher declares: read-only yes

    4 inputs, 4 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • tokenstringrequired“Token; zero address = native”
    • min_capacityintegerrequired
  • prepare_approval_revocations

    “Prepare every approve(spender,0) as an exact ordered multi-transaction execution plan.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • approvalsarrayrequired
  • get_rewards_claims_by_owner

    “Fetch canonical reward-claim records and supply the exact per-chain isClaimed/isAvailable eth_call list used by the interface before preparing claim transactions.”

    Publisher declares: read-only yes

    1 input, 1 required
    • ownerstringrequired“address”
  • prepare_rewards_claim

    “Prepare one Incentives claim or the interface's allow-failure Multicall3 aggregate for multiple claims.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • claimsarrayrequired
  • prepare_revenue_buybacks

    “Prepare the exact selected ended-order collections, protocol-fee withdrawals, and token rolls in interface order within one atomic batch of decodable steps.”

    Publisher declares: read-only yes

    5 inputs, 5 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“address”
    • ended_order_collectsarrayrequired
    • protocol_fee_pairsarrayrequired
    • roll_tokensarrayrequired
  • prepare_ve33_increase_stake

    “Prepare the exact approval/native value and increaseStakeAmount call while preserving the existing vote and fee accounting.”

    Publisher declares: read-only yes

    6 inputs, 6 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • stake_tokenstringrequired“address”
    • ve_idstringrequired“decimal integer”
    • amountstringrequired“Base units (positive decimal integer)”
  • prepare_ve33_merge

    “Prepare fee-safe merging of one or more source NFTs into a destination, including required claims and the selected resulting vote in one atomic batch of decodable steps.”

    Publisher declares: read-only yes

    7 inputs, 5 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • destination_ve_idstringrequired“decimal integer”
    • destination_pool_keyobject“PoolKey {token0, token1, config} or {token0, token1, fee, tick_spacing, extension, stableswap_params?}, as read from the pool or vote”
    • sourcesarrayrequired
    • resulting_voteobject or null
  • prepare_ve33_withdraw

    “Prepare fee-safe withdrawal of an expired ve-token stake, claiming the active pool first when voted and returning pending owner/stake validation.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“With ve_token, from get_ve33_allocations (STONX: 4663), not the wallet's chain”
    • ve_tokenstringrequired“address”
    • senderstringrequired“address”
    • ve_idstringrequired“decimal integer”
    • current_pool_keyobject“PoolKey {token0, token1, config} or {token0, token1, fee, tick_spacing, extension, stableswap_params?}, as read from the pool or vote”
  • get_liquidity_opportunities

    “Return the interface's boosted-fee, incentive and projected ve(3,3)-emission opportunities ranked by APR, with actionable pools or pool-discovery handoffs, freshness and risk context.”

    Publisher declares: read-only yes

    6 inputs
    • chain_idinteger or string“Omit for every chain”
    • typesarray“Defaults to all”
    • tokenstring“Token in the pair (EVM or Starknet) (hex)”
    • min_aprnumber“APR ratio floor; 1.0 = 100%”
    • limitinteger
    • ve33_emission_stateobject“{current_timestamp, current_emission_rate, total_remaining_emissions}: decimal strings decoded locally from getEmissionState (rate is Q32) via local_read_requi…”
  • prepare_pool_initialization

    “Prepare one permissionless maybeInitializePool transaction for a v3 PoolKey and initial tick; prepare_lp_position_deposit with pool_initialized=false does the same atomically with the mint.”

    Publisher declares: read-only yes

    5 inputs, 5 required
    • chain_idinteger or stringrequired“EVM chain ID”
    • senderstringrequired“Submitting wallet (address)”
    • core_addressstringrequired“v3 Core address”
    • pool_keyobjectrequired“Pool to initialize.”
    • initial_tickintegerrequired“The first initialization permanently sets the price”
  • get_aave_v3_markets

    “Locally return six major Aave V3 core deployments and a bounded set of popular reserve, aToken, and variable-debt-token addresses from a pinned official Aave address-book snapshot.”

    Publisher declares: read-only yes · open-world no

    1 input
    • chain_idinteger or string“Optional exact chain filter.”
  • prepare_aave_v3_supply

    “Prepare a fixed-market Aave V3 Pool supply with an exact ERC-20 approval, supply calldata, and allowance cleanup as one atomic wallet plan.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“Chain of a fixed Aave V3 core market returned by get_aave_v3_markets”
    • senderstringrequired“Wallet that will execute the Aave action (address)”
    • assetstringrequired“Exact underlying ERC-20 address from the selected market's fixed major-reserve list”
    • amountstringrequired“Positive underlying-token amount in base units (positive decimal integer)”
    • on_behalf_ofstring“aToken recipient; defaults to sender (address)”
  • prepare_aave_v3_withdraw

    “Prepare a direct Aave V3 Pool withdrawal for a supported fixed reserve.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“Chain of a fixed Aave V3 core market returned by get_aave_v3_markets”
    • senderstringrequired“Wallet that will execute the Aave action (address)”
    • assetstringrequired“Exact underlying ERC-20 address from the selected market's fixed major-reserve list”
    • amountstringrequired“Positive underlying-token amount in base units; uint256 maximum requests all available balance (positive decimal integer)”
    • recipientstring“Underlying-token recipient; defaults to sender (address)”
  • prepare_aave_v3_borrow

    “Prepare a direct Aave V3 variable-rate borrow from a supported fixed reserve, including optional on-behalf-of credit delegation.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“Chain of a fixed Aave V3 core market returned by get_aave_v3_markets”
    • senderstringrequired“Wallet that will execute the Aave action (address)”
    • assetstringrequired“Exact underlying ERC-20 address from the selected market's fixed major-reserve list”
    • amountstringrequired“Positive borrow amount in base units (positive decimal integer)”
    • on_behalf_ofstring“Debt owner; defaults to sender.”
  • prepare_aave_v3_repay

    “Prepare variable-debt repayment with underlying tokens or sender-owned aTokens.”

    Publisher declares: read-only yes

    6 inputs, 4 required
    • chain_idinteger or stringrequired“Chain of a fixed Aave V3 core market returned by get_aave_v3_markets”
    • senderstringrequired“Wallet that will execute the Aave action (address)”
    • assetstringrequired“Exact underlying ERC-20 address from the selected market's fixed major-reserve list”
    • amountstringrequired“Positive repayment amount in base units; uint256 maximum requests all available variable debt (positive decimal integer)”
    • on_behalf_ofstring“Debt owner; defaults to sender (address)”
    • funding_sourcestring“Use underlying ERC-20 with a temporary exact Pool approval, or burn sender-owned aTokens with repayWithATokens”
  • prepare_aave_v3_collateral

    “Prepare setUserUseReserveAsCollateral for a supported fixed reserve.”

    Publisher declares: read-only yes

    4 inputs, 4 required
    • chain_idinteger or stringrequired“Chain of a fixed Aave V3 core market returned by get_aave_v3_markets”
    • senderstringrequired“Wallet that will execute the Aave action (address)”
    • assetstringrequired“Exact underlying ERC-20 address from the selected market's fixed major-reserve list”
    • use_as_collateralbooleanrequired“True enables this supplied reserve as collateral; false disables it”
  • prepare_aave_v3_emode

    “Prepare setUserEMode with a caller-supplied current uint8 category ID; zero disables eMode.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“Chain of a fixed Aave V3 core market returned by get_aave_v3_markets”
    • senderstringrequired“Wallet whose eMode selection will change (address)”
    • category_idintegerrequired“Current onchain Aave eMode category; zero disables eMode.”
  • get_morpho_vaults

    “Locally return a bounded, pinned catalog of listed Morpho Vault V2 deployments plus official direct-discovery guidance.”

    Publisher declares: read-only yes · open-world no

    1 input
    • chain_idinteger or string“Optional exact chain filter for the fixed Morpho Vault V2 catalog”
  • prepare_morpho_vault_deposit

    “Prepare an exact-approval Morpho Vault V2 deposit through the official SDK's VaultBundlesV1 route.”

    Publisher declares: read-only yes

    7 inputs, 5 required
    • chain_idinteger or stringrequired“Chain returned by get_morpho_vaults”
    • senderstringrequired“Wallet that will execute the Morpho action (address)”
    • vaultstringrequired“Exact Morpho Vault V2 address returned by get_morpho_vaults”
    • amountstringrequired“Positive underlying-asset amount in base units (positive decimal integer)”
    • max_share_price_raystringrequired“Maximum acceptable vault share price in RAY (1e27), derived by the agent from fresh Morpho/onchain vault state plus the user's slippage tolerance (positive dec…”
    • recipientstring“Vault-share recipient; must equal sender if supplied, because VaultBundlesV1 mints shares only to the transaction sender (address)”
    • deadlinestring“Unix timestamp after which VaultBundlesV1 rejects the deposit; defaults to two hours after preparation.”
  • prepare_morpho_vault_withdraw

    “Prepare a direct Morpho Vault V2 withdrawal for an exact underlying-asset amount from a fixed vault.”

    Publisher declares: read-only yes

    6 inputs, 4 required
    • chain_idinteger or stringrequired“Chain returned by get_morpho_vaults”
    • senderstringrequired“Wallet that will execute the Morpho action (address)”
    • vaultstringrequired“Exact Morpho Vault V2 address returned by get_morpho_vaults”
    • amountstringrequired“Exact underlying-asset amount to withdraw in base units (positive decimal integer)”
    • recipientstring“Underlying-asset recipient; defaults to sender (address)”
    • ownerstring“Vault-share owner; defaults to sender (address)”
  • prepare_morpho_vault_redeem

    “Prepare a direct Morpho Vault V2 redemption for an exact share amount.”

    Publisher declares: read-only yes

    6 inputs, 4 required
    • chain_idinteger or stringrequired“Chain returned by get_morpho_vaults”
    • senderstringrequired“Wallet that will execute the Morpho action (address)”
    • vaultstringrequired“Exact Morpho Vault V2 address returned by get_morpho_vaults”
    • sharesstringrequired“Exact vault-share amount to redeem in base units (positive decimal integer)”
    • recipientstring“Underlying-asset recipient; defaults to sender (address)”
    • ownerstring“Vault-share owner; defaults to sender (address)”
  • get_sky_savings_deployment

    “Locally return the canonical Ethereum USDS and sUSDS addresses and direct wallet-read guidance.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • prepare_sky_savings_deposit

    “Prepare an exact USDS approval, ERC-4626 sUSDS deposit, and allowance cleanup as one atomic wallet plan.”

    Publisher declares: read-only yes

    4 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“Wallet that will execute the Sky savings action (address)”
    • amountstringrequired“Exact USDS deposit amount in base units (positive decimal integer)”
    • receiverstring“sUSDS recipient; defaults to sender (address)”
  • prepare_sky_savings_withdraw

    “Prepare a direct sUSDS ERC-4626 withdrawal for an exact USDS amount.”

    Publisher declares: read-only yes

    5 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“Wallet that will execute the Sky savings action (address)”
    • amountstringrequired“Exact USDS amount to withdraw in base units (positive decimal integer)”
    • receiverstring“USDS recipient; defaults to sender (address)”
    • ownerstring“sUSDS owner; defaults to sender (address)”
  • prepare_sky_savings_redeem

    “Prepare a direct sUSDS ERC-4626 redemption for an exact share amount.”

    Publisher declares: read-only yes

    5 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“Wallet that will execute the Sky savings action (address)”
    • sharesstringrequired“Exact sUSDS share amount to redeem in base units (positive decimal integer)”
    • receiverstring“USDS recipient; defaults to sender (address)”
    • ownerstring“sUSDS owner; defaults to sender (address)”
  • get_merkl_deployment

    “Locally return the Merkl Distributor address, the chains it is verified on, and how Merkl's reward fields behave; preparation is limited to those chains.”

    Publisher declares: read-only yes

    1 input
    • chain_idinteger or string“Optional chain to check against the verified Merkl Distributor catalog”
  • prepare_merkl_claim

    “Prepare one Distributor claim for every Merkl reward token the sender holds on a chain, from amounts and proofs fetched from https://api.merkl.xyz/v4/users/{address}/rewards/summary.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“From the Merkl rewards summary”
    • senderstringrequired“Claiming wallet; the leaf's user address”
    • rewardsarrayrequired“One entry per reward token on this chain, all in one claim”
  • get_aerodrome_deployment

    “Locally return Aerodrome's Base contracts (AERO, veAERO, Voter, Router, v2 factory, RewardsDistributor, Slipstream, Sugar lenses), derived on chain from the Voter, plus the protocol behaviour an agen…”

    Publisher declares: read-only yes

    1 input
    • chain_idinteger or string“Optional chain to check against Aerodrome's Base-only deployment”
  • prepare_aerodrome_sugar_reads

    “Build the eth_call bundle and decode plan for one Sugar dataset (pools, positions, veNFTs, epochs, rewards) for the wallet to run against the user's RPC; Sugar has no API.”

    Publisher declares: read-only yes

    7 inputs, 2 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • datasetstringrequired“Sugar dataset”
    • accountstring“Required for positions and venfts_by_account (address)”
    • poolstring“Required for pool_epochs and venft_pool_rewards (address)”
    • venft_idstring“Required for venft_by_id, venft_rewards, and venft_pool_rewards (positive decimal integer)”
    • limitinteger“Page size; at most 500 pools or 200 positions”
    • offsetinteger
  • prepare_aerodrome_liquidity_deposit

    “Prepare a v2 addLiquidity through Aerodrome's Router with exact approvals and allowance cleanup.”

    Publisher declares: read-only yes

    11 inputs, 10 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • token_astringrequired“address”
    • token_bstringrequired“address”
    • stablebooleanrequired“Stable (true) or volatile pool; with the pair it identifies the pool”
    • amount_a_desiredstringrequired“Maximum token_a base units (positive decimal integer)”
    • amount_b_desiredstringrequired“Maximum token_b base units (positive decimal integer)”
    • amount_a_minstringrequired“Slippage bound: minimum token_a base units consumed (positive decimal integer)”
    • amount_b_minstringrequired“Minimum token_b base units consumed (positive decimal integer)”
    • deadlinestringrequired“Near-term unix timestamp; a past one makes the plan revert (positive decimal integer)”
    • recipientstring“Defaults to sender (address)”
  • prepare_aerodrome_liquidity_withdraw

    “Prepare a v2 removeLiquidity that burns LP tokens back into the underlying pair, with the LP-token approval the router needs and an allowance cleanup after.”

    Publisher declares: read-only yes

    11 inputs, 9 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • token_astringrequired“address”
    • token_bstringrequired“address”
    • stablebooleanrequired“Stable (true) or volatile pool”
    • liquiditystringrequired“Exact LP token amount to burn in base units (positive decimal integer)”
    • amount_a_minstringrequired“Minimum token_a base units to receive (positive decimal integer)”
    • amount_b_minstringrequired“Minimum token_b base units to receive (positive decimal integer)”
    • deadlinestringrequired“Near-term unix timestamp; a past one makes the plan revert (positive decimal integer)”
    • recipientstring“Defaults to sender (address)”
    • lp_tokenstring“Pool address from this tool's first-phase read; omit to get that read, supply it for the full plan”
  • prepare_aerodrome_gauge_deposit

    “Stake v2 LP tokens into a pool's gauge to earn AERO emissions, with the LP-token approval the gauge needs and an allowance cleanup after.”

    Publisher declares: read-only yes

    5 inputs, 4 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • gaugestringrequired“Gauge from a Sugar pools read (address)”
    • amountstringrequired“Exact LP token amount to stake in base units (positive decimal integer)”
    • lp_tokenstring“Gauge stakingToken from this tool's first-phase read; omit to get that read, supply it for the full plan (address)”
  • prepare_aerodrome_gauge_withdraw

    “Unstake v2 LP tokens from a gauge.”

    Publisher declares: read-only yes

    4 inputs, 4 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • gaugestringrequired“Gauge from a Sugar pools read (address)”
    • amountstringrequired“Exact LP token amount to unstake in base units (positive decimal integer)”
  • prepare_aerodrome_gauge_claim

    “Claim accrued AERO from a gauge.”

    Publisher declares: read-only yes

    4 inputs, 3 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • gaugestringrequired“Gauge from a Sugar pools read (address)”
    • accountstring“Account whose emissions are claimed; defaults to sender.”
  • prepare_aerodrome_lock

    “Build one veAERO escrow action: create a lock, add AERO to one, extend it, switch permanent locking on or off, or withdraw an expired one.”

    Publisher declares: read-only yes

    6 inputs, 3 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • actionstringrequired“Which veAERO lock action to build”
    • amountstring“AERO amount in base units; required for create and increase_amount (positive decimal integer)”
    • lock_durationstring“Lock length in seconds measured from now, required for create and extend.”
    • venft_idstring“veNFT token id; required for every action but create (positive decimal integer)”
  • prepare_aerodrome_vote

    “Cast one veNFT's gauge vote, or reset it.”

    Publisher declares: read-only yes

    5 inputs, 3 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • venft_idstringrequired“veNFT token id casting the vote (positive decimal integer)”
    • poolsarray“The complete allocation.”
    • resetboolean“Clear this NFT's votes instead of casting new ones; required before withdrawing a voted NFT”
  • prepare_aerodrome_incentive_claim

    “Claim a veNFT's voting rewards — trading fees, bribes, or both — and optionally the RewardsDistributor rebase, as one plan.”

    Publisher declares: read-only yes

    6 inputs, 3 required
    • chain_idinteger or stringrequired“Base (8453) only”
    • senderstringrequired“address”
    • venft_idstringrequired“veNFT token id whose rewards are claimed (positive decimal integer)”
    • feesarray“Fee contracts and their tokens, taken from a Sugar venft_rewards read”
    • bribesarray“Bribe contracts and their tokens, taken from a Sugar venft_rewards read”
    • claim_rebaseboolean“Also claim the RewardsDistributor rebase, which compounds into the lock”
  • decode_uniswap_v4_position_info

    “Decode the packed PositionInfo returned by wallet reads into signed tick bounds, subscriber flag and the truncated pool-ID prefix.”

    Publisher declares: read-only yes · open-world no

    1 input, 1 required
    • infostringrequired“decimal integer”
  • quote_uniswap_liquidity

    “Calculate V3/V4 range liquidity, rounded mint/burn amounts and explicit token bounds from a current sqrt-price snapshot and raw token budgets, or an exact liquidity amount.”

    Publisher declares: read-only yes · open-world no

    8 inputs, 6 required
    • tick_lowerintegerrequired
    • tick_upperintegerrequired
    • tick_spacingintegerrequired
    • sqrt_price_x96stringrequired“decimal integer”
    • amount0stringrequired“decimal integer”
    • amount1stringrequired“decimal integer”
    • liquiditystring“decimal integer”
    • slippage_bpsinteger
  • get_uniswap_deployments

    “Canonical V2/V3/V4 contracts on Ethereum, Optimism, Base, Arbitrum, Unichain and Robinhood, including Permit2 and wrapped native addresses.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • discover_uniswap_pools

    “Fetch indexed V2, V3 or V4 pools ranked by TVL from Uniswap's interface API.”

    Publisher declares: read-only yes

    5 inputs, 2 required
    • chain_idstringrequired
    • versionstringrequired
    • token_addressstring“address”
    • firstinteger
    • tvl_cursornumber
  • get_uniswap_pool

    “Fetch indexed pool details, currencies, fee, TVL, volume and supplies.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idstringrequired
    • versionstringrequired
    • poolstringrequired
  • get_uniswap_pool_ticks

    “Fetch paginated initialized ticks and exact liquidityNet/liquidityGross strings for V3/V4 liquidity depth charts.”

    Publisher declares: read-only yes

    5 inputs, 3 required
    • chain_idstringrequired
    • versionstringrequired
    • poolstringrequired
    • firstinteger
    • skipinteger
  • get_uniswap_charts

    “Fetch timestamped token0/token1 prices and USD volume history over the requested duration from the same GraphQL fields as the open source Uniswap interface.”

    Publisher declares: read-only yes

    4 inputs, 3 required
    • chain_idstringrequired
    • versionstringrequired
    • poolstringrequired
    • durationstring
  • prepare_uniswap_reads

    “Return exact wallet read bundles for pool state, reserves, positions and ownership.”

    Publisher declares: read-only yes

    11 inputs, 4 required
    • chain_idstringrequired
    • versionstringrequired
    • token0stringrequired“address”
    • token1stringrequired“address”
    • feeinteger
    • tick_spacinginteger
    • hooksstring“address”
    • pool_addressstring“address”
    • ownerstring“address”
    • token_idsarray
    • owner_indicesarray
  • prepare_uniswap_v2_add_liquidity

    “Add liquidity or create a V2 pair with exact token approvals and cleanup.”

    Publisher declares: read-only yes

    10 inputs, 9 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • amount0stringrequired“decimal integer”
    • amount1stringrequired“decimal integer”
    • amount0_minstringrequired“decimal integer”
    • amount1_minstringrequired“decimal integer”
    • use_nativeboolean
  • prepare_uniswap_v2_remove_liquidity

    “Burn an exact LP amount through the canonical V2 router; realize accrued fees with principal.”

    Publisher declares: read-only yes

    9 inputs, 8 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • liquiditystringrequired“decimal integer”
    • amount0_minstringrequired“decimal integer”
    • amount1_minstringrequired“decimal integer”
    • unwrap_nativeboolean
  • prepare_uniswap_v3_add_liquidity

    “Mint a ranged NFT or increase token_id with raw desired amounts and minima.”

    Publisher declares: read-only yes

    16 inputs, 13 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • amount0stringrequired“decimal integer”
    • amount1stringrequired“decimal integer”
    • amount0_minstringrequired“decimal integer”
    • amount1_minstringrequired“decimal integer”
    • tick_lowerintegerrequired
    • tick_upperintegerrequired
    • tick_spacingintegerrequired
    • feeintegerrequired
    • token_idstring“decimal integer”
    • use_nativeboolean
    • initialize_sqrt_price_x96string“decimal integer”
  • prepare_uniswap_v3_remove_liquidity

    “Decrease exact uint128 liquidity, collect principal and all accrued fees, and optionally burn a fully emptied NFT.”

    Publisher declares: read-only yes

    11 inputs, 9 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • token_idstringrequired“decimal integer”
    • liquiditystringrequired“decimal integer”
    • amount0_minstringrequired“decimal integer”
    • amount1_minstringrequired“decimal integer”
    • burnboolean
    • unwrap_nativeboolean
  • prepare_uniswap_v3_collect_fees

    “Collect all owed fees without removing liquidity, optionally unwrapping WETH.”

    Publisher declares: read-only yes

    7 inputs, 6 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • token_idstringrequired“decimal integer”
    • unwrap_nativeboolean
  • prepare_uniswap_v4_add_liquidity

    “Mint or increase an exact liquidity amount using raw uint128 token maxima.”

    Publisher declares: read-only yes

    17 inputs, 13 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • pool_idstringrequired“bytes32 hex”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • feeintegerrequired
    • tick_spacingintegerrequired
    • hooksstring“address”
    • hook_datastring“hex bytes”
    • tick_lowerintegerrequired
    • tick_upperintegerrequired
    • liquiditystringrequired“decimal integer”
    • amount0_maxstringrequired“decimal integer”
    • amount1_maxstringrequired“decimal integer”
    • token_idstring“decimal integer”
    • initialize_sqrt_price_x96string“decimal integer”
  • prepare_uniswap_v4_remove_liquidity

    “Remove liquidity and take principal plus fees to the sender.”

    Publisher declares: read-only yes

    15 inputs, 12 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • pool_idstringrequired“bytes32 hex”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • feeintegerrequired
    • tick_spacingintegerrequired
    • hooksstring“address”
    • hook_datastring“hex bytes”
    • token_idstringrequired“decimal integer”
    • liquiditystringrequired“decimal integer”
    • amount0_minstringrequired“decimal integer”
    • amount1_minstringrequired“decimal integer”
    • burnboolean
  • prepare_uniswap_v4_collect_fees

    “Poke a V4 position with zero liquidity decrease then take both currencies to the sender.”

    Publisher declares: read-only yes

    11 inputs, 9 required
    • chain_idstringrequired
    • senderstringrequired“address”
    • deadlinestringrequired“decimal integer”
    • pool_idstringrequired“bytes32 hex”
    • token0stringrequired“address”
    • token1stringrequired“address”
    • feeintegerrequired
    • tick_spacingintegerrequired
    • hooksstring“address”
    • hook_datastring“hex bytes”
    • token_idstringrequired“decimal integer”
  • get_lido_deployment

    “Locally return canonical Ethereum stETH, wstETH, and WithdrawalQueueERC721 addresses plus direct wallet-read guidance.”

    Publisher declares: read-only yes · open-world no

    Takes no inputs.

  • prepare_lido_stake

    “Prepare the canonical Lido submit call with exact native ETH value and an explicit or zero referral.”

    Publisher declares: read-only yes

    4 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“address”
    • amountstringrequired“Exact native ETH stake amount in wei (positive decimal integer)”
    • referralstring“Optional Lido referral address; defaults to zero address”
  • prepare_lido_wrap

    “Prepare an exact stETH approval, wstETH wrap call, and allowance cleanup in one atomic wallet plan.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“address”
    • amountstringrequired“Exact stETH amount to wrap in base units (positive decimal integer)”
  • prepare_lido_unwrap

    “Prepare a direct wstETH unwrap call for an exact share amount, returning rebasing stETH to the sender.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“address”
    • amountstringrequired“Exact wstETH amount to unwrap in base units (positive decimal integer)”
  • prepare_lido_withdrawal_request

    “Prepare one or more bounded stETH withdrawal requests with an exact queue approval and cleanup.”

    Publisher declares: read-only yes

    4 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“address”
    • amountsarrayrequired“One to 64 stETH request amounts, each from 100 wei through 1000 stETH”
    • ownerstring“Recipient/owner of the unstETH request NFTs; defaults to sender (address)”
  • prepare_lido_withdrawal_claim

    “Prepare claimWithdrawal for one finalized, unclaimed unstETH request ID owned by the sender.”

    Publisher declares: read-only yes

    3 inputs, 3 required
    • chain_idinteger or stringrequired“Must be Ethereum chain 1”
    • senderstringrequired“address”
    • request_idstringrequired“Finalized, unclaimed unstETH NFT request ID owned by sender (positive decimal integer)”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-11-05.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
82% of 545
Tools with a description
100% of 99
Typical description length
290 characters

The tool set

Counted from the listing

Tools
99
Size of the list
about 32,690 tokens for an agent to load (characters ÷ 4)
Naming
99 of 99 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 99 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none, comparing tools within groups of 40. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-11-05 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.ekubo.org/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "ekubo": {
      "url": "https://mcp.ekubo.org/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "ekubo": {
      "type": "http",
      "url": "https://mcp.ekubo.org/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"ekubo","type":"http","url":"https://mcp.ekubo.org/mcp"}'
Claude Code
claude mcp add --transport http ekubo https://mcp.ekubo.org/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "ekubo": {
      "type": "streamableHttp",
      "url": "https://mcp.ekubo.org/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "ekubo": {
      "httpUrl": "https://mcp.ekubo.org/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.ekubo]
url = "https://mcp.ekubo.org/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "ekubo": {
      "url": "https://mcp.ekubo.org/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.ekubo.org/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.ekubo.org/mcpSession openedmatchesour test · 2026-11-05
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-11-05
Repository github.com/EkuboProtocol/ekubo-mcp-serverOpens publiclymatchesapi.github.com · 2026-11-05

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.EkuboProtocol · 2 servers
GitHub owner
an organization (EkuboProtocol)
Repository
github.com/EkuboProtocol/ekubo-mcp-server
Stars
1
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-11-05; security policy read from GitHub · 2026-11-05.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: 1 star (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.What changes this check: GitHub's documentation describes adding a SECURITY.md from the repository's security settings: under Reporting, Security policy, Start setup. GitHub: adding a security policy
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-05 (security policy 2026-11-05). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.EkuboProtocol/ekubo

Answered from the data above

Who publishes io.github.EkuboProtocol/ekubo?

The registry ties the namespace io.github.EkuboProtocol to the GitHub account EkuboProtocol; only its owner can publish under it. Its linked repository, github.com/EkuboProtocol/ekubo-mcp-server, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.EkuboProtocol/ekubo safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does io.github.EkuboProtocol/ekubo need an API key or sign-in?

It opened a session without any credential on 2026-11-05. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.github.EkuboProtocol/ekubo been security tested?

Partly. 3 of the 14 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. ProtocolProbe publishes no security verdict for a named server.

Does io.github.EkuboProtocol/ekubo publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.github.EkuboProtocol/ekubo?

In github.com/EkuboProtocol/ekubo-mcp-server, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-11-05
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

3 exercised11 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.

Exercised · 3
  • 1Inventory
    tool-list    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding    Checks resources that hide content from the user.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-11-05, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 1,406 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 99 tools, 17 resources, 0 prompts.
  4. 5,361 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-11-05; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
TypeScript
api.github.com · 2026-11-05
Hosting type
remote (hosted by the publisher)
registry · 2026-11-05
MCP capability
completions, resources, tools
our test · 2026-11-05
Transport
streamable HTTP
registry · 2026-11-05
Required credentials
none declared
registry · 2026-11-05 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-11-05
Lifecycle status
active
registry · 2026-11-05
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
owner: an organization · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-05
Maintenance
active
api.github.com · 2026-11-05
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-11-05

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.EkuboProtocol/ekubo: MCP server record.” Data checked 2026-11-05. https://protocolprobe.com/mcp/servers/io.github.EkuboProtocol/ekubo

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 4 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.EkuboProtocol/ekubo)](https://protocolprobe.com/mcp/servers/io.github.EkuboProtocol/ekubo)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology