Jarvis Market Signals — MCP server
Live crypto-derivatives and market signals for AI agents: perp liquidations, funding-rate crowding, open-interest positioning, safe stablecoin yield, and FX — fresh streaming data a static model can't know, served over a metered MCP endpoint.
Endpoint: https://jarvis.tail12fa6b.ts.net:8443/mcp (streamable HTTP)
Free tier: 100 calls/day — open an issue to get a key.
Discovery is open: initialize and tools/list need no key, so any MCP client or registry scanner can inspect the tools before authenticating.
Tools
Liquidation and positioning tools query a rolling 24-hour buffer fed by always-on ingesters; window_minutes is capped to that buffer.
Quick start
Claude Code
claude mcp add --transport http jarvis-market-signals https://jarvis.tail12fa6b.ts.net:8443/mcp --header "Authorization: Bearer YOUR_KEY"
Cursor / generic MCP client config
{
"mcpServers": {
"jarvis-market-signals": {
"url": "https://jarvis.tail12fa6b.ts.net:8443/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" }
}
}
}
curl (no key needed for discovery)
curl -s -X POST https://jarvis.tail12fa6b.ts.net:8443/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
tools/call requires Authorization: Bearer <key> (or x-api-key). Without one you get a plain JSON 401.
Auth and limits
- Anonymous:
initialize,tools/list— open for discovery. - Keyed:
tools/call—Authorization: Bearer jvk_…, free tier 100 calls/day (rolling 24h), HTTP 429 over quota. - No OAuth; keys are issued manually via GitHub issue while the service is small.
Notes
- Market data is informational only — not financial advice. Yield figures are estimates from public feeds; verify before acting.
- The server runs on dedicated home infrastructure behind a Tailscale Funnel TLS relay; brief maintenance windows can occur.
- Source for the gateway lives in a private repo; this repo is the public listing, key-request channel, and issue tracker.