Openocean

Created By
openocean-finance6 months ago
An MCP server for executing token swaps across multiple decentralized exchanges using OpenOcean's aggregation API.
Overview

What is Openocean?

Openocean is an MCP server designed for executing token swaps across multiple decentralized exchanges (DEXs) using OpenOcean's aggregation API.

How to use Openocean?

To use Openocean, you can run the server using pnpm dlx for easy integration with MCP clients, or install it globally via npm. Configuration is required for the MCP client to run the server.

Key features of Openocean?

  • CHAIN_LIST: Fetches the list of available chains.
  • GAS_PRICE: Retrieves the current gas price for a specified chain.
  • QUOTE: Provides a quote for a token swap.
  • SWAP: Executes a swap transaction.
  • GET_TRANSACTION: Fetches information about a specific transaction.
  • TOKEN_LIST: Lists available tokens on a specified chain.
  • DEX_LIST: Lists available DEXs on a specified chain.

Use cases of Openocean?

  1. Facilitating token swaps across various DEXs for better rates.
  2. Integrating with AI assistants or IDE extensions for automated trading.
  3. Providing developers with tools to build custom applications that require token swap functionalities.

FAQ from Openocean?

  • Can Openocean handle swaps on all DEXs?

Yes! Openocean aggregates data from multiple DEXs to provide the best swap rates.

  • Is Openocean free to use?

Yes! Openocean is open-source and free for everyone to use.

  • What are the prerequisites for running Openocean?

You need Node.js (v18 or newer) and pnpm installed to run the server.

Project Info
Created At
6 months ago
Updated At
6 months ago
Author Name
openocean-finance
Star
-
Language
-
License
-

Recommend Servers

View All
Gpt Scrambler

2 days ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

2 hours ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago