agentgates.aiVerified
Confidential computers for AI swarms: sealed VMs (Intel TDX) by the hour, USDC over x402.
Finance & CryptoPayments & trading
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 514 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Payments & trading
Crypto market state, 44 assets: 4 states x 10 timeframes. Recorded, never recomputed, verifiable.
2 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 2 | 2 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using DAMO Market State
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http damo-market-state https://api.damolive.com/mcpCapabilities
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).
DiscoveredUse when the user asks about several crypto assets at once. Same as get_market_state for up to 50 symbols in one call.
DiscoveredUse 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).
DiscoveredUse 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 1254 ms | 4 |