Exchange Arbitrage Agent
REMOTE · API-PRODUCTION-0B04.UP.RAILWAY.APP
Prediction-market quotes, fill estimates and odds trends, paid per call with x402 USDC on Base.
Available components
Last scanned (23 hours ago)
Scores higher than 43% of remote servers
Unreachable for 1 day in a row. Last reached 3 Nov 2026.
Category Finance and Payments
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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 4 Nov 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 59
First indexed and scored.
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 4 Nov 2026 · Probed https://api-production-0b04.up.railway.app/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api-production-0b04.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api-production-0b04.up.railway.app/mcp | Unreachable | ||
| http (plaintext) | http://api-production-0b04.up.railway.app/mcp | HTTPS enforced |
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 →
estimate_fill ~64
Fill estimate for buying a number of shares of one outcome: VWAP, total cost and partial-fill status within a slippage cap. $0.01 USDC per call on Base. Not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| shares | number | yes | – |
| token_id | string | yes | – |
No output schema declared.
No examples provided.
get_odds_trends ~55
Stored odds-comparison snapshots from the arbitrage worker for trend analysis. $0.01 USDC per call on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
| team | – | – | – |
No output schema declared.
No examples provided.
get_odds_trends_summary ~60
Aggregated edge trends per event from stored snapshots: min/max/avg taker edge and best expected maker edge. $0.01 USDC per call on Base.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_quote ~55
Order-book quote for one outcome: best bid and ask, mid, spread and top five levels of depth. $0.005 USDC per call on Base. Live data, not advice.
| Name | Type | Req | Description |
|---|---|---|---|
| token_id | string | yes | – |
No output schema declared.
No examples provided.
get_status ~24
Free: agent status, trading mode and kill-switch state. No account data.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_markets ~34
Free: search open prediction markets by text. Returns market ids, outcomes and token ids.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Exchange Arbitrage Agent MCP server?
Exchange Arbitrage Agent is a hosted endpoint at https://api-production-0b04.up.railway.app/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-production-0b04.up.railway.app
claude mcp add --transport http lkennedyshare-exchange-arbitrage-agent 'https://api-production-0b04.up.railway.app/mcp'
What is the Exchange Arbitrage Agent MCP server?
Exchange Arbitrage Agent is an MCP server listed in the public MCP registry as io.github.LKennedyShare/exchange-arbitrage-agent. Prediction-market quotes, fill estimates and odds trends, paid per call with x402 USDC on Base. This page covers its hosted endpoint (https://api-production-0b04.up.railway.app/mcp).
Is the Exchange Arbitrage Agent MCP server safe to use?
Exchange Arbitrage Agent scores 61 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 Exchange Arbitrage Agent MCP server expose?
Exchange Arbitrage Agent exposes 6 tools: get_status, search_markets, get_quote, estimate_fill, get_odds_trends, get_odds_trends_summary. Their descriptions and schemas cost roughly 292 tokens of context every time the server is loaded.
Does the Exchange Arbitrage Agent MCP server require authentication?
Its publisher declares no required credentials for Exchange Arbitrage Agent. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Exchange Arbitrage Agent MCP server still maintained?
Exchange Arbitrage Agent is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.