Schema | Ekubo MCP server

Ekubo MCP server

Official

Describes the environment variables required to run the server.

Name	Required	Description
`DUNE_API_KEY`	Yes	API key for Dune's SQL execution endpoint, used internally by the STONX allocation-recommendation snapshot. Never returned or identified by the public MCP surface.
`LI_FI_API_KEY`	Yes	API key for the LI.FI API (https://li.quest/v1), sent as `x-lifi-api-key` for cross-chain quotes and transfer status.
`ACROSS_API_KEY`	Yes	Bearer token for the Across `GET /swap/approval` endpoint, used for cross-chain bridging quotes.
`ZERO_X_API_KEY`	Yes	API key for 0x Swap API v2 (AllowanceHolder endpoints), used for same-chain quote comparison against Ekubo.
`ALLOWED_ORIGINS`	No	Optional comma-separated list of allowed origins for cross-origin browser MCP clients. The request's own hostname is always accepted as a browser origin.
`ALLOWED_HOSTNAMES`	No	Optional comma-separated list of allowed hostnames, set if the deployment needs a stricter host list.
`LAYER_ZERO_API_KEY`	Yes	API key for the LayerZero Value Transfer API (https://transfer.layerzero-api.com/v1), sent as `x-api-key` for cross-chain quotes and transfer status.
`ACROSS_INTEGRATOR_ID`	Yes	Across integrator ID sent with authenticated Across bridge requests.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Server capabilities have not been inspected yet.

Functions exposed to the LLM to take actions

Name	Description
No tools

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

This server cannot be deployed

ActivityActive

ResponsivenessResponsive