MCP Server

Model Context Protocol integration for AI agents. Query signed oracle data natively from Claude, GPT, and other LLMs.

Attach this URL

https://api.myceliasignal.com/mcp — Streamable HTTP. No account, no API key, nothing to install. Paste it as a custom MCP connector and the tools arrive with their own descriptions and prices.

What it is

The Model Context Protocol lets an agent call external tools during a conversation. This server exposes Mycelia Signal's oracle data as MCP tools over Streamable HTTP. tools/list is free; paid tools answer an unpaid call with an x402 challenge naming the amount, asset, network and recipient, and the agent's own wallet settles it.

Prices are identical to the HTTP API for the same object. There is no MCP premium. x402 only on this transport — the L402 (Lightning) rail serves the HTTP API.

Attaching

grok.com · Claude · Cursor

Settings → Connectors → New → Custom, then paste:

https://api.myceliasignal.com/mcp

Grok Bot — one sentence in chat

Add a custom MCP server called mycelia at https://api.myceliasignal.com/mcp

python — xAI SDK

from xai_sdk.tools import mcp

tools = [mcp(
    server_url="https://api.myceliasignal.com/mcp",
    server_label="mycelia",
    allowed_tool_names=[
        "get_price", "get_sentiment", "get_volatility", "get_perp_state",
        "get_funding", "get_basis", "get_open_interest", "verify_attestation",
    ],
)]

json — OpenAI-compatible Responses API

{
  "type": "mcp",
  "server_label": "mycelia",
  "server_url": "https://api.myceliasignal.com/mcp",
  "require_approval": "never"
}

The eight tools advertised by default

Tool	Price	What it measures
`get_price`	$0.01	Signed median spot across up to ten exchanges, 43 pairs (crypto, FX, metals). Requires `base` and `quote`.
`get_sentiment`	$0.05	MSXI, −100…+100: funding, 25-delta skew, put/call, term structure and cross-exchange dispersion, each with its weight. Requires `pair`.
`get_volatility`	$0.05	MSVI, 0…100: realised and implied volatility, term structure, funding, put/call. Requires `pair`.
`get_perp_state`	$1.00	Perp regime across BTC, ETH and SOL with the component readings behind it and the conditions under which the label is withdrawn. No parameters.
`get_funding`	$0.05	Ten-exchange funding composite with z-score and the venue-published next scheduled rate.
`get_basis`	$0.02	Perp-spot basis and annualised carry across ten venues.
`get_open_interest`	$0.01	Open interest and its 1h/4h/24h change, per venue and in USD.
`verify_attestation`	free	Verify any Mycelia canonical string and signature against a published per-node key, offline.

Eight of 214 priced endpoints are advertised by default; more are registered. Synopsis, macro risk, IV surface, term structure, support and resistance, regime change and persistence, prediction-market odds, economic indicators and COT all exist on the server — name them in allowed_tool_names to use them. The default eight are kept short so a tool picker stays readable.

A first prompt that actually calls a tool

Ask for something a chat answer cannot satisfy:

prompt

Using Mycelia, return the signed BTC/USD price and the current MSVI
reading, then verify the attestation on the price.

That exercises three tools and ends on verification — the thing an exchange ticker cannot do. A vaguer prompt (“what's bitcoin doing?”) is usually answered from the model's own knowledge without touching the server.

These tools measure. They do not forecast.

Out-of-sample testing on 2026-09-25 put MSVI's 24-hour forward correlation with BTC returns at −0.287, against +0.104 in the fitting window and −0.020 over the full period — a sign flip, which is what a dead signal looks like. No Mycelia index has evidence of predicting direction at any magnitude the data can detect, and nothing here should be read as a trade recommendation.

What you get instead is a current, signed, independently verifiable measurement: attested at the moment it was taken, checkable offline against a published key, and the same number for every caller.

Payment

x402 on Base, USDC, per call. An unpaid tools/call on a priced tool returns a challenge with the amount in micro-USDC, the asset contract, the network and the recipient. Your client signs and retries; the payment is verified through the same facilitator as the HTTP API. One settlement covers one tool call — so set a client-side spending ceiling before looping.

No account. No API key. No signup.

Prefer Python callables?

The LangChain plugin exposes the same data as Python tools with automatic x402 payment. Use the MCP server when your framework speaks MCP; use the plugin for LangChain agents.