Epsilon
REMOTE · API.EPSILON.EXCHANGE · 2 COMPONENTS · SCANNED SEP 21
Non-custodial limit, stop-loss and DCA trading on Epsilon (Robinhood Chain) for AI agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1242 tokens (~82/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Epsilon MCP server?
Epsilon is a hosted endpoint at https://api.epsilon.exchange/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.epsilon.exchange
claude mcp add --transport http alienbase-xyz-epsilon 'https://api.epsilon.exchange/mcp'
{
"mcpServers": {
"alienbase-xyz-epsilon": {
"url": "https://api.epsilon.exchange/mcp"
}
}
} {
"servers": {
"alienbase-xyz-epsilon": {
"type": "http",
"url": "https://api.epsilon.exchange/mcp"
}
}
} [mcp_servers.alienbase-xyz-epsilon] url = "https://api.epsilon.exchange/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"alienbase-xyz-epsilon": {
"type": "remote",
"url": "https://api.epsilon.exchange/mcp",
"enabled": true
}
}
} openclaw mcp add alienbase-xyz-epsilon --url 'https://api.epsilon.exchange/mcp' --transport streamable-http
mcp_servers:
alienbase-xyz-epsilon:
url: "https://api.epsilon.exchange/mcp" {
"McpServers": {
"alienbase-xyz-epsilon": {
"Transport": "http",
"Url": "https://api.epsilon.exchange/mcp"
}
}
} assistant mcp add alienbase-xyz-epsilon -t streamable-http -u 'https://api.epsilon.exchange/mcp'
{
"mcpServers": {
"alienbase-xyz-epsilon": {
"type": "http",
"url": "https://api.epsilon.exchange/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://api.epsilon.exchange/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.epsilon.exchange | CN=YE1,O=Let's Encrypt,C=US | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 6eada0080f07cadf2b966ed12862f55fe94 |
| SANs: api.epsilon.exchange | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.epsilon.exchange. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| exchange. | present | 46084 | 8 | Verified |
| epsilon.exchange. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains |
| content-security-policy | default-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.epsilon.exchange/mcp | Verified | 200 | |
| http (plaintext) | http://api.epsilon.exchange/mcp | HTTPS enforced | 308 | https://api.epsilon.exchange/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
error_catalog ~27
Machine-readable catalog of every error code the Epsilon API returns, with meanings and retry guidance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_example ~50
Full source code of one Epsilon integration example, by id from list_examples. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | example id from list_examples, e.g. python-dca-cron |
No output schema declared.
No examples provided.
get_market_overview ~53
One-call market snapshot of Epsilon (Robinhood Chain DEX): top tokens by 30-day volume, 24h volume aggregates, and engine-wide order/fill stats. Good first call for market context.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_order_status ~58
Look up an Epsilon order by hash: status (pending/active/filled/cancelled), parameters, and its fills.
| Name | Type | Req | Description |
|---|---|---|---|
| orderHash | string | yes | EIP-712 order hash (0x-hex, 32 bytes) |
No output schema declared.
No examples provided.
get_orderbook ~66
Open (pending/active) limit orders on both sides of a token pair, largest first.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenA | string | yes | first token address of the pair (0x-hex) |
| tokenB | string | yes | second token address of the pair (0x-hex) |
No output schema declared.
No examples provided.
get_quote ~125
Best executable quote for swapping tokenIn → tokenOut on Epsilon (Robinhood Chain, id 4663). Amounts are RAW token units — scale by the token's decimals first. This only quotes; it never executes.
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | amount of tokenIn in RAW token units (decimal string, already scaled by the token's decimals) |
| tokenIn | string | yes | ERC-20 address of the token being sold (0x-hex) |
| tokenOut | string | yes | ERC-20 address of the token being bought (0x-hex) |
No output schema declared.
No examples provided.
get_route ~240
Full routing breakdown for a swap: best venue split, expected and minimum output, price impact (ppm), and the feeLegs a signed order must embed. Read-only. Amounts are RAW token units.
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | amount of tokenIn in RAW token units (decimal string, already scaled by the token's decimals) |
| orderType | string | – | order kind being priced (limit | stop_loss | take_profit | dca | trailing) — selects the fee cell served in feeLegs; omit for a direct swap |
| slippageBps | integer | – | slippage tolerance in basis points (default 100 = 1%) |
| tokenIn | string | yes | ERC-20 address of the token being sold (0x-hex) |
| tokenOut | string | yes | ERC-20 address of the token being bought (0x-hex) |
| triggered | boolean | – | with orderType=dca: the schedule gates on a trigger (triggered DCA fee cell) |
| wallet | string | – | optional maker wallet address — include it to get the exact feeLegs an order for this wallet must embed |
No output schema declared.
No examples provided.
list_examples ~46
List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_orders ~104
List Epsilon orders by maker wallet, status, and/or type — the portfolio view. Newest first.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max rows (default 100, cap 500) |
| status | string | – | order status filter, e.g. active, filled, cancelled |
| type | string | – | order type filter, e.g. limit, dca, trailing |
| wallet | string | – | maker wallet address to filter by (0x-hex) |
No output schema declared.
No examples provided.
market_stats ~26
Engine-wide Epsilon stats: order counts by status, fill counts, and volume aggregates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
order_preflight ~118
Check whether a limit/DCA order for this pair and size would be executable: oracle support, liquidity, minimum size. Run this before signing an order. Amounts are RAW token units.
| Name | Type | Req | Description |
|---|---|---|---|
| amountIn | string | yes | amount of tokenIn in RAW token units (decimal string, already scaled by the token's decimals) |
| tokenIn | string | yes | ERC-20 address of the token being sold (0x-hex) |
| tokenOut | string | yes | ERC-20 address of the token being bought (0x-hex) |
No output schema declared.
No examples provided.
recent_swaps ~60
Most recent swaps executed through Epsilon, optionally filtered to one wallet. Amounts are RAW token units.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max rows (default 100, cap 500) |
| wallet | string | – | optional wallet address to filter by |
No output schema declared.
No examples provided.
search_docs ~98
Search the Epsilon developer documentation (API, auth, order signing, webhooks, rev-share, SDKs, MCP). Returns the most relevant doc sections. No API key required.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max sections to return (default 5, cap 10) |
| query | string | yes | what to look for in the Epsilon developer docs, e.g. 'sign an order', 'rate limits', 'webhooks signature' |
No output schema declared.
No examples provided.
search_tokens ~106
Resolve a token symbol or name to its address and decimals — call this FIRST when the user names a token; every other tool takes addresses. volume30dUsd disambiguates same-symbol tokens: the real one has volume.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | max rows (default 20, cap 100) |
| search | string | – | symbol or name fragment (e.g. USDG), or an exact 0x address; empty returns the top tokens by 30-day volume |
No output schema declared.
No examples provided.
token_volume ~65
Per-token and total swap volume over a window (1h, 24h, 7d, 30d, all).
| Name | Type | Req | Description |
|---|---|---|---|
| window | string | – | aggregation window: 1h, 24h (default), 7d, 30d, or all |
No output schema declared.
No examples provided.
What is the Epsilon MCP server?
Epsilon is an MCP server listed in the public MCP registry as io.github.alienbase-xyz/epsilon. Non-custodial limit, stop-loss and DCA trading on Epsilon (Robinhood Chain) for AI agents. This page covers its hosted endpoint (https://api.epsilon.exchange/mcp).
Is the Epsilon MCP server safe to use?
Epsilon scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Epsilon MCP server expose?
Epsilon exposes 15 tools: error_catalog, get_example, get_market_overview, get_order_status, get_orderbook, and 10 more. Their descriptions and schemas cost roughly 1,242 tokens of context every time the server is loaded.
Does the Epsilon MCP server require authentication?
No. We connected to Epsilon without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Epsilon MCP server still maintained?
Epsilon is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.