Skip to content

MCP server

SpectralEdge runs a hosted Model Context Protocol server. Add it to an AI assistant and ask about the live 15-minute contest on Bitcoin, Ethereum, Solana or XRP, or how the signals resolved, in plain language. The assistant calls the Public Signals API for you.

https://mcp.cotes.ai/mcp

Transport is Streamable HTTP. Sign in with your Cotes account (OAuth) or send an API key. Either way the account needs a live trial or subscription at app.cotes.ai.

Terminal window
claude mcp add --transport http spectraledge https://mcp.cotes.ai/mcp

Then run /mcp, choose spectraledge and sign in.

The SpectralEdge plugin adds the same server along with five analysis skills:

/plugin marketplace add https://gitlab.com/cotes-ai-public/spectraledge-examples.git
/plugin install spectraledge-signals@spectraledge

Send a key from Account → API keys in any of these headers:

Authorization: Bearer cotes_sk_...
X-API-Token: cotes_sk_...
X-API-Key: cotes_sk_...
{
"mcpServers": {
"spectraledge": {
"url": "https://mcp.cotes.ai/mcp",
"headers": { "Authorization": "Bearer cotes_sk_..." }
}
}
}

All tools are read-only. None of them place orders.

Tool Returns REST equivalent
list_series The crypto catalog (KXBTC15M, KXETH15M, KXSOL15M, KXXRP15M), the contest trading on each and the model behind its newest signal. GET /v1/series
get_active_contest The contest trading now and every signal raised so far. 404 between one contest settling and the next opening, and for a series that isn’t recorded. GET /v1/contests/active
list_contests Settled contests, newest first, signals graded win / loss / void. limit 1–100 with fired_only, at most 10 without it. since / before window on window.expires_at. A full page returns next_cursor; pass it back as cursor for the next older page. fired_only lists only the readings that fired. GET /v1/contests
get_contest One contest by full ticker, live or settled. GET /v1/contests/{ticker}

get_active_contest and list_contests require a series. Name an asset and the assistant passes its series: KXBTC15M, KXETH15M, KXSOL15M or KXXRP15M. The live event stream is not exposed over MCP; use SSE for that.

Resource Returns
spectraledge://guide/reading-signals What each signal field means and how to threshold readings
spectraledge://contests/active The Bitcoin contest trading now
spectraledge://contests/active/{series} The contest trading now for a series
spectraledge://contests/{ticker} One contest by full ticker
Prompt Arguments Does
monitor_live_signals series Summarizes the active contest and its signals
measure_accuracy confidence_threshold (required), series, limit Takes the first signal at or above your threshold in each of the last N settled contests and counts wins and losses

Signals are every reading the model raised, including ones that did not fire. Each reading carries fired: true when it cleared SpectralEdge’s confidence, edge and distance-from-strike thresholds in force when it was raised. Those are SpectralEdge’s calls. To judge readings by your own confidence threshold or edge range instead, ask for it; the assistant applies yours and states the threshold it used. The measure_accuracy prompt always takes your threshold.

  • “What’s the live BTC 15-minute contest and what is SpectralEdge saying?”
  • “Which assets do you cover, and what’s the live ETH contest?”
  • “Over the last 100 settled contests, how often was the first reading at 80% or above right?”
  • “Show every reading for KXBTC15M-26NOV041715-15 and how it settled.”

MCP tool calls are API calls under your account: the same rate limit (1 request/second per IP, burst 20, with each tool call spending two requests) and the same 401 / 402 errors. list_contests returns at most 100 contests per call with fired_only and 10 without it, since each contest then lists every reading raised during it; the assistant pages on with next_cursor. For larger backtests, the agent skills page through history in a script instead of the model’s context.

Research data, not financial advice.