DAMO Market State MCP server
com.damolive/market-statedamolive.comstreamable-httpv1.4.0Scanned
Crypto market state, 44 assets: 4 states x 10 timeframes. Recorded, never recomputed, verifiable.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the DAMO Market State MCP server can do
The DAMO Market State MCP server is published by damolive.com, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.4.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
get_market_stateUse 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.No findings
Why it is in this group
- The name "get_market_state" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: Get DAMO market state
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_market_statesUse when the user asks about several crypto assets at once.No findings
Why it is in this group
- The name "get_market_states" says "get": a word for reading.
Description, as the server wrote it Use when the user asks about several crypto assets at once. Same as get_market_state for up to 50 symbols in one call.
Annotations the server declares
- title: Get DAMO market state for several symbols
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_state_definitionsUse when the user asks what DAMO's states, codes or layers mean.No findings
Why it is in this group
- The name "get_state_definitions" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: DAMO state definitions
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_symbolsUse to check whether DAMO covers an asset and which symbol name to use.No findings
Why it is in this group
- The name "list_symbols" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List DAMO symbols
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools4 changed.~4 changedView diff
- Changed:get_market_stateOnly readsdescriptionannotations
- Changed:get_market_statesOnly readsdescriptionannotations
- Changed:get_state_definitionsOnly readsdescriptionannotations
- Changed:list_symbolsOnly readsdescriptionannotations
Tools2 changed.~2 changedView diff
- Changed:get_market_stateOnly readsinputSchema
- Changed:get_market_statesOnly readsinputSchema
Install
Pinned to version 1.4.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http market-state https://api.damolive.com/mcpclaude mcp add --transport http market-state https://api.damolive.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__market-state__get_market_state",
"mcp__market-state__get_market_states",
"mcp__market-state__list_symbols",
"mcp__market-state__get_state_definitions"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as market-state. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.damolive/market-state/verify?hash=38d55ed8a6ffeb3bfee9ddfa3b1d05dd231f4f894193e482c1c78a7f21276012" | jq -e '.changed == false'Pinned hash 38d55ed8a6ff, from Nov 9, 2026, 08:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.damolive/market-state/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.damolive/market-state)Source: MCP Registry. Synced Oct 26, 2026, 03:17 UTC.
DAMO Market State MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the DAMO Market State MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the DAMO Market State MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the DAMO Market State MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the DAMO Market State MCP server have?
- 4 tools: 4 read. get_market_state, get_market_states, list_symbols and get_state_definitions.
Does the DAMO Market State MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the DAMO Market State MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the DAMO Market State MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.