DAMO Market State
REMOTE · API.DAMOLIVE.COM
Crypto market state, 44 assets: 4 states x 10 timeframes. Recorded, never recomputed, verifiable.
Available components
Last scanned (11 hours ago)
Scores higher than 83% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability58
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1347 tokens (~336/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 90% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +2
- Tool “get_market_state” rewrote its description, which is the text the model reads security
- Tool “get_market_states” rewrote its description, which is the text the model reads security
- Tool “get_state_definitions” rewrote its description, which is the text the model reads security
- Tool “list_symbols” rewrote its description, which is the text the model reads security
- Server version: 1.4.0 → 1.4.1 functional
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.3.8 → 1.4.0 functional
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
- Server version: 1.3.7 → 1.3.8 functional
- “get_market_state” reworded the description of “symbol” cosmetic
- 21 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “get_market_state” rewrote its description, which is the text the model reads security
- Schema quality: 255 → 299 ▼ functional
- Server version: 1.3.6 → 1.3.7 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.damolive.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.damolive.com | CN=WR3,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | RSA 2048 | SHA256-RSA | 56bf559e12c4b2ff0abc1ffdadd22e32 |
| SANs: api.damolive.com | ||||||
| CN=WR3,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7ff005a91568d63abc22861684aa4b5a |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
| CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 1 Sept 1998 | 28 Jan 2028 | RSA 2048 | SHA1-RSA | 40000000001154b5ac394 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.damolive.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| damolive.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31556926 |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.damolive.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.damolive.com/mcp | HTTPS enforced | 301 | https://api.damolive.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_market_state Get DAMO market state ~303
Use when the user asks about the current market state (trend or momentum) of a crypto asset on any timeframe from 1 minute to 1 month. Returns state data only: no prices, forecasts or trade signals. Current DAMO market state of one symbol across 10 timeframes: state name and permanent code per timeframe, plus a 10-value vector in fixed timeframe order. as_of is when DAMO last wrote the record; each timeframe's candle close is in states[tf].candle_close (live: candle_close_expected).
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | compact = symbol, layer, time, vector, short citation and remaining quota only. full = per-timeframe state, seq, hash and engine version (for citing and checking). |
| layer | string | – | verified = closed candles (recorded, never changed); live = forming candles (provisional) |
| proof | boolean | – | Also put DAMO's Ed25519 signature in the result body as 'proof'. |
| symbol | string | yes | Ticker, e.g. BTCUSDT. BTC, btc, BTC/USDT, BTC-PERP and coin names like Bitcoin are also accepted. Not a sentence: on a wrong symbol the error lists did_you_mean. |
| timeframes | array | – | Optional. Only these timeframes are returned and counted against the quota (case-sensitive: 1m = minute, 1M = month). Omit for all 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | verified: when DAMO last wrote this record (UTC). Each timeframe's own close time is states[tf].candle_close |
| chain_head | object | – | – |
| citation | string | yes | – |
| engine_version | string | – | – |
| layer | string | yes | – |
| observed_at | string | – | live: when DAMO observed the forming candles (UTC) |
| proof | object | – | Ed25519 signature when proof=true |
| quota | object | – | – |
| quota_remaining | integer | – | – |
| stale | boolean | – | – |
| states | object | – | full format: per-timeframe state, code, candle status and record fields |
| symbol | string | yes | – |
| vector | array | yes | State codes in timeframe order (1 bull_momentum, 2 weakening, 3 bear_momentum, 4 recovery); null = not requested or not available |
| vector_order | array | – | – |
No examples provided.
get_market_states Get DAMO market state for several symbols ~176
Use when the user asks about several crypto assets at once. Same as get_market_state for up to 50 symbols in one call.
| Name | Type | Req | Description |
|---|---|---|---|
| format | string | – | compact = symbol, layer, time, vector, short citation and remaining quota only. full = per-timeframe state, seq, hash and engine version (for citing and checking). |
| layer | string | – | verified = closed candles (recorded, never changed); live = forming candles (provisional) |
| proof | boolean | – | Also put DAMO's Ed25519 signature in the result body as 'proof'. |
| symbols | array | yes | – |
| timeframes | array | – | Optional. Only these timeframes are returned and counted against the quota (case-sensitive: 1m = minute, 1M = month). Omit for all 10. |
| Name | Type | Req | Description |
|---|---|---|---|
| citation | string | – | – |
| count | integer | – | – |
| errors | array | – | – |
| layer | string | yes | – |
| proof | object | – | – |
| quota | object | – | – |
| quota_remaining | integer | – | – |
| results | array | yes | – |
No examples provided.
get_state_definitions DAMO state definitions ~53
Use when the user asks what DAMO's states, codes or layers mean. The 4 permanent DAMO states and codes, timeframe order, the verified/live layers and what DAMO outputs (state data only).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| codes_are_permanent | boolean | – | – |
| states | array | yes | – |
| timeframes | array | – | – |
No examples provided.
list_symbols List DAMO symbols ~40
Use to check whether DAMO covers an asset and which symbol name to use. Symbols covered by DAMO, with available layers and any timeframe not yet available.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| symbols | array | yes | – |
No examples provided.
How do I install the DAMO Market State MCP server?
DAMO Market State is a hosted endpoint at https://api.damolive.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.damolive.com
claude mcp add --transport http com-damolive-market-state 'https://api.damolive.com/mcp'
What is the DAMO Market State MCP server?
DAMO Market State is an MCP server listed in the public MCP registry as com.damolive/market-state. Crypto market state, 44 assets: 4 states x 10 timeframes. Recorded, never recomputed, verifiable. This page covers its hosted endpoint (https://api.damolive.com/mcp).
Is the DAMO Market State MCP server safe to use?
DAMO Market State scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the DAMO Market State MCP server expose?
DAMO Market State exposes 4 tools: get_market_state, get_market_states, list_symbols, get_state_definitions. Their descriptions and schemas cost roughly 572 tokens of context every time the server is loaded.
Does the DAMO Market State MCP server require authentication?
No. We connected to DAMO Market State without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the DAMO Market State MCP server still maintained?
DAMO Market State is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.