# ophis-fi/ophis [Health: Active]

**Category:** 💰 Finance & Fintech  
**Repository:** https://github.com/ophis-fi/ophis  
**GitHub Stars:** 4  
**Views:** 4  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/ophis-fi-ophis

## Description
Agent-first intent-based DEX aggregator (self-hosted CoW Protocol). Remote Streamable HTTP at https://mcp.ophis.fi/mcp, no auth, holds no keys. 12 tools: parseintent (natural-language swap to structured intent), resolvetoken (symbol to canonical address, fails closed), listchains, getquote, expectedsurplus, buildorder (bounded, ready-to-sign EIP-712 CoW order with the receiver pinned to the owner), submitorder, lookuptier (fee-rebate tier), getbalances, getportfolio, getgas, gettokenchart. Live across 11 EVM chains: Ethereum, Optimism, BNB Chain, Gnosis, Polygon, Base, Arbitrum, Avalanche, Plasma, Ink, Linea.

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

```json
"mcpServers": {
  "ophis": {
    "url": "https://mcp.ophis.fi/mcp"
  }
}
```

## Documentation

## What ophis-fi/ophis MCP server does

The ophis-fi/ophis MCP server gives agents an interface for intent-based token swaps and related wallet data. An agent can turn a natural-language trade request into a structured intent, resolve token symbols to canonical addresses, identify supported chains, request a quote, compare expected surplus, and construct a bounded CoW Protocol order.

The service is non-custodial. It does not receive private keys, sign orders, or hold user funds. The `buildorder` capability returns an EIP-712 order that is ready for the user or agent to sign, with the receiver fixed to the owner. Submission can happen afterward through the MCP tools once the order has been signed externally.

## How it works

Connect an MCP client to the hosted Streamable HTTP endpoint at `https://mcp.ophis.fi/mcp`. No account or authentication token is required. The ophis-fi/ophis MCP server handles the off-chain steps around a CoW-style trade, while signing remains on the client side.

Supported networks include Ethereum, Optimism, BNB Chain, Gnosis, Polygon, Base, Arbitrum, Avalanche, Plasma, Ink, and Linea. Settlement infrastructure differs by chain: Optimism uses Ophis-operated infrastructure, while several other networks route through CoW Protocol’s hosted network. Clients should use chain discovery rather than assuming that orderbook hosts or settlement contracts are identical across networks.

The natural-language intent API can normalize a request such as swapping an amount of one token for another on a named chain, but that API only parses the text. It does not sign or execute a trade. The MCP workflow adds token resolution, quoting, order construction, and submission around that intent.

## Tools and capabilities

The documented tool set covers:

- `parseintent` for converting natural-language swap requests into structured intent data.
- `resolvetoken` for mapping token symbols to canonical addresses and failing closed when resolution is uncertain.
- `listchains` for discovering supported chains and their network-specific details.
- `getquote` and `expectedsurplus` for quote and execution-improvement information.
- `buildorder` for creating a bounded, ready-to-sign EIP-712 CoW order.
- `submitorder` for submitting a signed order.
- `lookuptier` for checking fee-rebate tier information.
- `getbalances` and `getportfolio` for wallet balances and portfolio views.
- `getgas` for gas information and `gettokenchart` for token chart data.

The repository describes additional intent, rebate, integrator, and lookup capabilities in the MCP tool reference. Tool naming may appear in snake_case in some documentation, such as `build_order` and `list_chains`.

## Limitations and notes

The ophis-fi/ophis MCP server does not remove the need for signing policy. Agents that sign automatically should enforce controls outside the server, including approved tokens, receiver restrictions, spending limits, and price bounds. The server’s safety helpers are not an authorization boundary because a prompt-injected agent could ignore them.

A client must handle the MCP transport correctly; requests that omit an `Accept: text/event-stream` header may receive HTTP 406 during transport negotiation. The server supports EVM-chain trading described by the project, while cross-chain destinations such as Solana and Bitcoin are surfaced through NEAR Intents rather than represented as ordinary EVM settlement networks.

_Full upstream README: https://allmcps.com/mcp/ophis-fi-ophis/readme_