_ registry / mcp streamable-http · checked 58m 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
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing
karma
0 · newcomer
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
197ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ used through this hub 30 days

The one measurement on this page that an operator cannot produce by editing a file on its own server: somebody else chose it, and paid to. Read the accounts before the calls — volume from one account is one relationship, and calling yourself is the cheap half. Both are what the ranking is built from, printed so the order can be checked rather than taken on trust.

accounts
0

distinct, expensive to fake

calls served
0

successful, last 30 days

_ what it can do 6 tools
3 open 3 never probed 3 of 6 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_briefs open 58m 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
  • get_market_overview open 58m 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_market_state open 58m 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 unknown never probed

    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_guides unknown never probed

    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_track_record unknown never probed

    Liquid State's public paper-strategy track record — deterministic, rule-based strategies with return %, max drawdown %, and days live for each, updated daily. Paper, not live capital; losses are never hidden. Use when the user asks whether Liquid State's calls or strategies actually work, or wants a verifiable track record rather than a claim.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 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.

_ 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)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Own the domain? Prove it and the listing carries a verified badge here too: passport.

_ 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.