Ophis
Pay per useActively maintained
≈ 2visits/mo
Emerging · estimate, read Oct 14, 2026
- For
- Traders swapping stablecoins and tokenized assets, and developers or agents integrating swaps into their own tools.
- Price
- Pay per usepricing page, read Oct 21, 2026
- Activity
- Actively maintainedrelease 4 days ago · site updated 9 days ago
- Used for
- Swap stablecoins across supported chains from your own wallet
- Compare stablecoin routes before signing a swap
- Turn a plain-language trade into structured swap fields via API
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsophis.fi ↗
Pay per use
- Security contactsecurity.txt
These are Ophis's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverfi.ophis/mcpverified in the MCP registry
- Stateanswers, 13 toolschecked 2026-10-21
- Address to connectmcp.ophis.fi/mcp
- OpenAPI spec1 pathsthe spec ↗
- Status pagelinked from the homepagedocs.ophis.fi/status ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Ophis for?
Sign in to leave a noteWhat is Ophis?
Routes token swaps through solver-driven DEX venues with MEV protection, exposed via an intent API and SDK.
Who is Ophis for?
Traders swapping stablecoins and tokenized assets, and developers or agents integrating swaps into their own tools.
How much does Ophis cost?
Ophis charges per use, per its pricing page on 2026-10-21.
Is Ophis free?
No. Its pricing page showed no free plan on 2026-10-21.
Do people use Ophis?
Emerging: ≈ 2 visits/mo · estimate, 2026-10 · 1.4k installs/mo (npm).
Is Ophis still maintained?
Actively maintained: release 4 days ago · site updated 9 days ago.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.