
Liqwall MCP server
Which MCP servers are Liqwall's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.liqwall/market-dataverified in the MCP registry
The registry name sits under liqwall.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools4
- Server calls itselfliqwall
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 203 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer641 ms
- Space in an agent's context≈ 728 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
liquidation_mapWhere forced liquidations stand around the current price of one market: USD amounts of long liquidations below the price and of short liquidations above it, on Hyperliquid (crypto, stocks, indices and commodities) and across large…
liquidationsHow much was liquidated: the last 24 hours and the last hour, longs against shorts, for the whole crypto market or for one coin. Use it for questions like "how much was liquidated today", "were longs or shorts liquidated", "which exchange…
derivativesFunding rates, open interest and the long/short ratio of perpetual futures, for one coin or for the ten largest coins by open interest. Use it for questions like "what is the funding rate of ETH", "is open interest growing", "are traders…
fear_greedThe crypto Fear and Greed Index: the mood of the market right now on a scale from 0 (extreme fear) to 100 (extreme greed), for the whole market or for BTC, ETH or SOL, with the values a day, a week and a month ago.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"market-data": {
"type": "http",
"url": "https://liqwall.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http liqwall https://liqwall.com/mcpclaude.ai, ChatGPT and other clients: add https://liqwall.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.