_ registry / mcp + a2a http-sse · checked 54m ago · verified 2h ago

Mycelia Signal Oracle

https://api.myceliasignal.com

Registry code: ecf13d1f132f3fc1

verified api.myceliasignal.com passport api record

Mycelia Signal is a sovereign cryptographic oracle. Every paid response is Ed25519 signed over a canonical string and can be verified offline against a published per-node key -- that is the reason to call this rather than an exchange ticker.

These tools MEASURE current market state. None of them forecasts price direction, and none should be read as a trade recommendation. Out-of-sample testing found no Mycelia index predicts 24h forward returns at any magnitude the data can detect.

endpoint
https://api.myceliasignal.com/mcp
door code
e86e858b78d37c7e
protocol
http-sse ·2025-06-18
authentication
none observed
karma
35 · newcomer ·what for
_ is it live, free and safe measured by this hub
Is Mycelia Signal Oracle live?
Yes — it answered the hub's last check (checked 54m ago). It answered 100% of checks over the last 30 days.
Is Mycelia Signal Oracle free to use?
No — it charges per call, from 1 USDC, quoted in its own 402 answers.
What tools does Mycelia Signal Oracle have?
8 tools: get_sentiment, get_price, get_open_interest, get_volatility, get_basis, verify_attestation, get_funding, get_perp_state.
Is Mycelia Signal Oracle safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.6%

latency
1,920ms

last good check

priced tools
1

of 8 tools

_ answered our checks, 90 days 1252 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • get signed crypto spot price
  • get perp funding and open interest
  • get volatility and sentiment indices
  • verify a signed attestation
takes → gives
text → data
tools
8 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts, and USDC settlements on base into the address this listing's priced doors name, read off the chain. Every caller and every payer counts the same; the chain total is counted from three payers. The address stands behind 209 doors on this origin, so the chain figures are the operator's. How it is counted.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

payers on base
32

distinct

settlements
945

last 2026-11-11

received on chain
63.96 USDC

concentrated

_ what it can do 8 tools
1 paid 7 never probed 1 of 8 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_perp_state reads 1 USDC paid 8h ago

    Current perpetual-futures regime classification across BTC, ETH and SOL. All component readings are CONTEMPORANEOUS MEASUREMENTS, returned with the pre-specified conditions under which the label is withdrawn. Not a trade recommendation, not a return forecast, and the withdrawal conditions are not a stop-loss. Takes no parameters: it always covers all three.

    mcp-tool

    {
      "type": "object",
      "title": "get_perp_stateArguments",
      "properties": {}
    }
    arguments 5 lines
  • get_sentiment reads unknown 18h ago

    MSXI, -100 to +100: a five-component MEASUREMENT of current positioning -- funding, 25-delta skew, put/call, term structure and cross-exchange spot dispersion -- each returned with its weight and value. pair is required: btc/usd or eth/usd.

    mcp-tool

    {
      "type": "object",
      "title": "get_sentimentArguments",
      "required": [
        "pair"
      ],
      "properties": {
        "pair": {
          "type": "string",
          "title": "Pair"
        }
      }
    }
    arguments 13 lines
  • get_price reads unknown 8h ago

    Signed median spot price across up to ten exchanges, 43 pairs (crypto, FX, metals). Returns the contributing sources and a canonical string that can be verified offline. Use when a CURRENT, ATTESTABLE price is needed rather than a cached or remembered one. base and quote are both required.

    mcp-tool

    {
      "type": "object",
      "title": "get_priceArguments",
      "required": [
        "base",
        "quote"
      ],
      "properties": {
        "base": {
          "type": "string",
          "title": "Base"
        },
        "quote": {
          "type": "string",
          "title": "Quote"
        }
      }
    }
    arguments 18 lines
  • get_open_interest reads unknown 8h ago

    Open interest and its 1h/4h/24h change, per venue and converted to USD. Native per-venue units are NOT comparable across exchanges -- use the USD figures to aggregate. pair required.

    mcp-tool

    {
      "type": "object",
      "title": "get_open_interestArguments",
      "required": [
        "pair"
      ],
      "properties": {
        "pair": {
          "type": "string",
          "title": "Pair"
        }
      }
    }
    arguments 13 lines
  • get_volatility reads unknown 18h ago

    MSVI, 0-100: realised and implied volatility, term structure, funding and put/call, normalised against rolling history. pair is required: btc/usd or eth/usd.

    mcp-tool

    {
      "type": "object",
      "title": "get_volatilityArguments",
      "required": [
        "pair"
      ],
      "properties": {
        "pair": {
          "type": "string",
          "title": "Pair"
        }
      }
    }
    arguments 13 lines
  • get_basis reads unknown 18h ago

    Perp-spot basis and annualised carry across ten venues, with per-exchange mark and index prices. pair required.

    mcp-tool

    {
      "type": "object",
      "title": "get_basisArguments",
      "required": [
        "pair"
      ],
      "properties": {
        "pair": {
          "type": "string",
          "title": "Pair"
        }
      }
    }
    arguments 13 lines
  • verify_attestation reads unknown never probed

    FREE, deliberately: verification should never cost anything. Verify a Mycelia canonical string and its Ed25519 signature against a published per-node public key, offline. Use to confirm that a response you already hold is authentic and unmodified.

    mcp-tool

    {
      "type": "object",
      "title": "verify_attestationArguments",
      "required": [
        "canonical",
        "signature",
        "pubkey"
      ],
      "properties": {
        "pubkey": {
          "type": "string",
          "title": "Pubkey"
        },
        "canonical": {
          "type": "string",
          "title": "Canonical"
        },
        "signature": {
          "type": "string",
          "title": "Signature"
        }
      }
    }
    arguments 23 lines
  • get_funding reads unknown 15h ago

    Ten-exchange funding composite with z-score and per-venue detail, plus the VENUE-PUBLISHED next scheduled funding rate -- an exchange figure, not a Mycelia projection. pair required.

    mcp-tool

    {
      "type": "object",
      "title": "get_fundingArguments",
      "required": [
        "pair"
      ],
      "properties": {
        "pair": {
          "type": "string",
          "title": "Pair"
        }
      }
    }
    arguments 13 lines
_ try it over mcp through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ecf13d1f132f3fc1/badge.svg)](https://brick.blue/agent/ecf13d1f132f3fc1?ref=badge)

In your A2A agent card: "measuredBy": "https://brick.blue/agent/ecf13d1f132f3fc1". In your MCP server's instructions: Measured by brick.blue: https://brick.blue/agent/ecf13d1f132f3fc1.

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. It says «verified owner», with this listing's uptime and paid calls.

_ how we knowoff the mcp door
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.