_ registry / mcp streamable-http · checked 1h ago

vault-crypto-intel

https://www.liquidstate.tech

Registry code: 082cce44c06cac74

api record

Free, read-only crypto market intelligence from Liquid State (liquidstate.tech). Information only, not financial advice.

endpoint
https://www.liquidstate.tech/api/mcp
door code
a38bb0c12d1aca09
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
10 · newcomer
_ is it live, free and safe measured by this hub
Is vault-crypto-intel live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is vault-crypto-intel free to use?
Yes — the hub reached it with no key and no payment.
What tools does vault-crypto-intel have?
8 tools: get_guides, get_market_state, get_derivatives, get_pricing, get_market_overview, get_agent_records, get_track_record, get_briefs.
Is vault-crypto-intel 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
98.7%

90 days 99.3%· all time 99.5%

latency
339ms

last good check

priced tools
0

of 8 tools

_ answered our checks, 90 days 1215 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • get crypto market snapshot
  • get perpetual funding rates
  • read crypto market briefs
takes → gives
text → data, text
tools
6 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 11 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
10

distinct

settlements
25

last 2026-11-14

received on chain
0.25 USDC

no flags

_ what it can do 8 tools
8 open 8 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_guides reads open 10h ago

    Liquid State's premium trading guides — title, one-line description, tags, page count, price (USD), url. Paid content, not free — price is always disclosed. Use when the user wants an in-depth trading education resource (risk management, position sizing, trend-following, etc.).

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_market_state reads open 13h ago

    Consolidated live crypto market snapshot designed for AI citation: BTC/ETH/SOL funding rates, prices, open interest, 24h liquidation aggregate, and a derived regime signal (Bullish/Bearish/Neutral). Returns as_of timestamp, source, and citation string. Use when the user asks about current crypto market conditions.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_derivatives reads open 13h ago

    Live perpetual-futures derivatives for one crypto asset from OKX: funding rate (%), open interest (USD), long-account %, and last price. Use when the user asks about funding, open interest, positioning, or the perp price of a specific coin.

    mcp-tool

    {
      "type": "object",
      "required": [
        "symbol"
      ],
      "properties": {
        "symbol": {
          "type": "string",
          "description": "Asset ticker, e.g. BTC, ETH, SOL."
        }
      }
    }
    arguments 12 lines
  • get_pricing open 10h ago

    What Liquid State costs today: the free read-only API and MCP server, The Feed, The Reserve, and the x402 per-call USDC terms. Founding and yearly plans are listed only while /pricing has them on sale, checked when you call the tool. Prices are in the response, not in this description. Use when the user or agent asks about price, plans, or how to pay.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_market_overview reads open 5h ago

    Funding rate + price snapshot for the major crypto assets (BTC, ETH, SOL) in one call. Use for a quick market-wide read.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_agent_records open 5h ago

    Free discovery of currently public Genuine Agent Records, matching the selected public lifecycle projection. Samples are excluded. Maximum 25 per page, 60 reads/minute/client shared with REST. Use slug for one record, or slug plus format=registration for its ERC-8004-shaped export. No public metrics are available in the current lifecycle schema. Tool errors contain error and optional retry_after; rate_limited means wait retry_after seconds. rate_limit_unavailable or discovery_unavailable means retry later.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "slug": {
          "type": "string",
          "pattern": "^[a-z0-9-]{3,48}$"
        },
        "after": {
          "type": "string",
          "pattern": "^[a-z0-9-]{3,48}$",
          "description": "Ascending slug cursor; works even if the prior record is withdrawn."
        },
        "limit": {
          "type": "integer",
          "default": 25,
          "maximum": 25,
          "minimum": 1
        },
        "format": {
          "enum": [
            "registration"
          ],
          "type": "string",
          "description": "Requires slug; cannot combine slug with pagination."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
  • get_track_record reads open 13h ago

    Liquid State's legacy paper-strategy simulation record: returns, drawdown, and equity observation counts. Continuity is not verified. It does not measure paid stance outcomes or live capital. The separate prospective stance history is linked in the response.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_briefs reads open 5h ago

    Recent crypto market-intelligence briefs from Liquid State — analyst write-ups on price action, liquidations, funding, and macro. Returns headline, category, coins, summary, url, publishedAt. Use when the user wants recent crypto news/analysis or what's moving markets.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "limit": {
          "type": "integer",
          "description": "How many recent briefs to return (1-50, default 15)."
        }
      }
    }
    arguments 9 lines
_ try it 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.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 082cce44c06cac74.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/082cce44c06cac74/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

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

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
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.