Remote MCP server exposing DAMO's recorded crypto market states for 44 assets across 10 timeframes, with verifiable citations.
What you can do
Look up the current DAMO market state of one symbol across 10 fixed timeframes, with state codes and a 10-value vector
Fetch the same state for up to 50 symbols in a single call
List covered symbols, their available layers and any missing timeframes
Read the permanent state definitions, timeframe order and layer descriptions
Choose verified (closed candles, recorded once) or live (forming candles, provisional) layers, and full or compact output
When to use it
Useful when an assistant needs a fixed, rule-based classification of crypto market conditions per asset and timeframe, and answers should be citable and checkable later against recorded, hash-chained values. Not suited for prices, candles, forecasts or trading signals.
Requirements
Remote streamable HTTP endpoint; no key or environment variables declared. Free tier allows 500 state values per client per UTC day (one value = one symbol times one timeframe). Network access to the provider's API is required.
Before you install
Free tier is quota-limited per client per UTC day; optional timeframe selection and compact format change what is returned and counted. Live-layer values are provisional and never recorded. Terms prohibit reverse engineering the state engine, training models that reproduce its states, and systematic collection beyond your application's needs. Outputs are state data only, not investment advice.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.damolive%2Fmarket-state/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
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).
Symbols covered by DAMO, with available layers and any timeframe not yet available.
Takes no parameters.
get_state_definitions
DAMO state definitions
The 4 permanent DAMO states and codes, timeframe order, the verified/live layers and what DAMO outputs (state data only).
Takes no parameters.
Version history
7
v1.4.0LatestOct 26, 2026
v1.3.8Oct 22, 2026
v1.3.7Oct 21, 2026
v1.3.6Oct 16, 2026
v1.3.5Oct 15, 2026
v1.3.2Oct 12, 2026
v1.3.1Oct 11, 2026
Score
83%
83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Reached in the last 30 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.