# DAMO Market State (remote · api.damolive.com)

Crypto market state, 44 assets: 4 states x 10 timeframes. Recorded, never recomputed, verifiable.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.damolive.com`: 81/100 (this document), [markdown](https://verifymcp.io/servers/com-damolive-market-state/api.md), [page](https://verifymcp.io/servers/com-damolive-market-state/api)

## Channel facts

- Endpoint: `https://api.damolive.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http com-damolive-market-state 'https://api.damolive.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-damolive-market-state": {
      "url": "https://api.damolive.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-damolive-market-state": {
      "type": "http",
      "url": "https://api.damolive.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-damolive-market-state]
url = "https://api.damolive.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-damolive-market-state": {
      "type": "remote",
      "url": "https://api.damolive.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-damolive-market-state --url 'https://api.damolive.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-damolive-market-state:
    url: "https://api.damolive.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-damolive-market-state": {
      "Transport": "http",
      "Url": "https://api.damolive.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-damolive-market-state -t streamable-http -u 'https://api.damolive.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-damolive-market-state": {
      "type": "http",
      "url": "https://api.damolive.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +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.

### 2026-11-01 (score 80, +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.

### 2026-10-31 (score 79, +2)

- [security] 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
- [functional] Server version: 1.4.0 → 1.4.1

### 2026-10-29 (score 77, +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.

### 2026-10-26 (score 76, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 1.3.8 → 1.4.0

### 2026-10-24 (score 75, +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.

### 2026-10-22 (score 74, +1)

- [functional] Server version: 1.3.7 → 1.3.8
- [cosmetic] “get_market_state” reworded the description of “symbol”

### 2026-10-21 (score 73, 0)

- [security] 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
- [functional regression] Schema quality: 255 → 299
- [functional] Server version: 1.3.6 → 1.3.7

## MCP tools (4)

### `get_market_state` (~303 tokens)

Get DAMO market state

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

Input parameters:

- `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, required): 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.

Output parameters:

- `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)
- `engine_version` (string)
- `layer` (string)
- `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)
- `vector` (array): State codes in timeframe order (1 bull_momentum, 2 weakening, 3 bear_momentum, 4 recovery); null = not requested or not available
- `vector_order` (array)

### `get_market_states` (~176 tokens)

Get DAMO market state for several symbols

Use when the user asks about several crypto assets at once. Same as get_market_state for up to 50 symbols in one call.

Input parameters:

- `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, required)
- `timeframes` (array): Optional. Only these timeframes are returned and counted against the quota (case-sensitive: 1m = minute, 1M = month). Omit for all 10.

Output parameters:

- `citation` (string)
- `count` (integer)
- `errors` (array)
- `layer` (string)
- `proof` (object)
- `quota` (object)
- `quota_remaining` (integer)
- `results` (array)

### `list_symbols` (~40 tokens)

List DAMO symbols

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.

Output parameters:

- `count` (integer)
- `symbols` (array)

### `get_state_definitions` (~53 tokens)

DAMO state definitions

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

Output parameters:

- `codes_are_permanent` (boolean)
- `states` (array)
- `timeframes` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-damolive-market-state/api#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 77
- 2026-10-29: 77
- 2026-10-28: 76
- 2026-10-27: 76
- 2026-10-26: 76
- 2026-10-25: 75
- 2026-10-24: 75
- 2026-10-23: 74
- 2026-10-22: 74
- 2026-10-21: 73
- 2026-10-20: 73
- 2026-10-19: 73
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 71
- 2026-10-15: 71
- 2026-10-14: 71
- 2026-10-13: 70
- 2026-10-12: 70

## Common questions

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

### What did VerifyMCP test on the DAMO Market State MCP server?

VerifyMCP ran 13 checks on DAMO Market State, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.damolive.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-damolive-market-state/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-damolive-market-state/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-damolive-market-state/api.json
- HTML version of this page: https://verifymcp.io/servers/com-damolive-market-state/api