Home / MCP registry index / fi.ophis/mcp
Ophis MCP
fi.ophis/mcp in the official MCP registry.
Endpoint https://mcp.ophis.fi/mcp. Source: github.com/ophis-fi/ophis.
The registry describes it as: Gasless, MEV-protected onchain token swaps for AI agents on 14 EVM chains, built on CoW Protocol.
We read its 13 tools on 2026-10-26. Nothing in them matched our tool-poisoning rules.
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 every week.
Tools it advertises
parse_intent get_quote build_order submit_order get_integrator_earnings list_chains get_balances get_portfolio get_gas get_token_chart expected_surplus resolve_token validate_order
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/fi-ophis-mcp)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. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.