# NythosX Market Data (remote · market.nythosx.com)

Crypto/stock trade setups, signal bias, levels, regime, odds. Free track record. Pay per call, x402.

- Trust score: 61/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `market.nythosx.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-nythosx-market-market-data/market.md), [page](https://verifymcp.io/servers/com-nythosx-market-market-data/market)

## Channel facts

- Endpoint: `https://market.nythosx.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-10-23.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1355 tokens (~135/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the NythosX Market Data MCP server?

NythosX Market Data is a hosted endpoint at https://market.nythosx.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-nythosx-market-market-data 'https://market.nythosx.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nythosx-market-market-data": {
      "url": "https://market.nythosx.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nythosx-market-market-data": {
      "type": "http",
      "url": "https://market.nythosx.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nythosx-market-market-data]
url = "https://market.nythosx.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-nythosx-market-market-data --url 'https://market.nythosx.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nythosx-market-market-data:
    url: "https://market.nythosx.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nythosx-market-market-data": {
      "Transport": "http",
      "Url": "https://market.nythosx.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nythosx-market-market-data -t streamable-http -u 'https://market.nythosx.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-nythosx-market-market-data": {
      "type": "http",
      "url": "https://market.nythosx.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-10-23 (score 61, 0)

- [security] Tool “arm_price_trigger” rewrote its description, which is the text the model reads
- [security] Tool “get_free_snapshot” rewrote its description, which is the text the model reads
- [security] Tool “get_market_regime” rewrote its description, which is the text the model reads
- [security] Tool “get_support_resistance” rewrote its description, which is the text the model reads
- [security] Tool “get_target_probability” rewrote its description, which is the text the model reads
- [security] Tool “get_track_record” rewrote its description, which is the text the model reads
- [security] Tool “get_trigger_status” 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 regression] Schema quality: pass → fail

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

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

- [functional improvement] Stability: unverified → 0.03

### 2026-10-20 (score 60)

First indexed and scored.

## MCP tools (10)

### `list_symbols` (~46 tokens)

List supported symbols, timeframes, the per-call USDC price of each paid tool (not asset prices — call get_signal_bias etc. for those), and the payment network (free).

### `get_track_record` (~79 tokens)

Graded accuracy of every published signal bias: hit rate by confidence, bias and symbol, Wilson intervals, Brier score, independent samples (free). Omit symbol for the all-symbols report; pass it to filter to one instrument. Returns 404 if nothing has been graded yet for that filter.

Input parameters:

- `symbol` (string): Instrument symbol

### `get_free_snapshot` (~127 tokens)

Market regime (trend, volatility, RSI, ATR%) and nearest support/resistance for BTC and ETH only, refreshed every 15 minutes (free). Returns {price, regime, nearestSupport, nearestResistance}. Pick this over the paid siblings when you just need a quick read on BTC/ETH; use get_signal_bias ($0.01) for a trade direction, get_trade_plan ($0.03) for full setup levels and odds, or get_market_regime/get_support_resistance ($0.005 each) for other symbols or deeper history.

Input parameters:

- `symbol` (string, required)

### `get_trigger_status` (~100 tokens)

Status of a trigger armed with arm_price_trigger (free). Returns {id, status, symbol, direction, price, created_at, expires_at, fired_at, fired_price, delivered_at, delivery_attempts, last_error}, where status is one of armed, fired_delivering, delivered, delivery_failed (after 5 webhook attempts) or expired. Returns 404 if id is unknown or its payment never settled.

Input parameters:

- `id` (string, required)

### `get_trade_plan` (~124 tokens)

Complete trade setup in one call. One call instead of four: signal bias, market regime, nearest support/resistance, setup levels (entry, stop, target, R:R), probability of reaching the target before the stop, odds of touching the target within 7 days, an estimated time to target, invalidation conditions, and this symbol's graded track record. Neutral bias returns the odds of hitting resistance before support. Costs $0.03 USDC per call (x402).

Input parameters:

- `symbol` (string, required): Instrument symbol
- `tf` (string): Candle timeframe

### `get_signal_bias` (~135 tokens)

Signal bias with setup levels and invalidation. Rules-based signal bias (bullish / lean_bullish / neutral / lean_bearish / bearish) with score, confidence, setup levels (entry, stop, target, risk-reward), weighted factors (trend, RSI, ATR, ADX, divergences, candle patterns, macro regime) and explicit invalidation conditions. Same output for every caller; accuracy is published free at /api/v1/track-record. Costs $0.01 USDC per call (x402).

Input parameters:

- `symbol` (string, required): Instrument symbol
- `tf` (string): Candle timeframe

### `get_support_resistance` (~126 tokens)

Support and resistance map. Up to five support and five resistance levels from clustered daily swing pivots, high-volume nodes and round numbers, each with kind, strength (1-5) and touch count, plus the nearest level on each side. Computed from the last 30 daily candles (cached 15 minutes). Use nearestSupport/nearestResistance as stop-loss/take-profit anchors for a position already open; higher strength and touch count mean a more reliable level. Costs $0.005 USDC per call (x402).

Input parameters:

- `symbol` (string, required): Instrument symbol

### `get_market_regime` (~134 tokens)

Trend and volatility regime. Market regime from the last 24 hours of hourly candles (cached 5 minutes): trend (up / down / range, EMA50 vs EMA200), volatility bucket (low / normal / high / extreme by ATR%), RSI, EMAs. Use this for risk sizing or entry timing (e.g. avoid new entries while volatility is 'extreme') alongside get_signal_bias for direction and get_support_resistance for levels — on its own it gives context, not a trade direction. Costs $0.005 USDC per call (x402).

Input parameters:

- `symbol` (string, required): Instrument symbol

### `get_target_probability` (~150 tokens)

Probability of reaching a target price. Probability that the price closes beyond a target within 1, 7 and 30 days, and the approximate probability of touching it, from 14-day ATR volatility (normal approximation; touch ~ 2x close-beyond by the reflection principle). symbol must be one of the supported list (see list_symbols) and target must be a positive number, or the call returns 400 and is not charged; if volatility can't be computed from recent candles it returns 502 and is not charged. Costs $0.005 USDC per call (x402).

Input parameters:

- `symbol` (string, required): Instrument symbol
- `target` (number, required): Target price in the quote currency

### `arm_price_trigger` (~234 tokens)

Arm a price trigger with webhook delivery. Arms a single-fire price trigger. NythosX checks the price every minute and POSTs a JSON event to your HTTPS webhook on the first crossing: {event:"trigger.fired", id, symbol, direction, price, fired_price, fired_at}, signed with HMAC-SHA256 (header X-NythosX-Signature: sha256=<hex> over the raw body, key = returned secret). Retries up to 5 times (8s timeout per attempt, until your endpoint returns 2xx); after 5 failed attempts delivery is marked failed — poll status free at GET /api/v1/triggers/status?id= to see delivery_attempts/last_error. Expires after ttl_hours (default 168, max 720). Costs $0.02 USDC per call (x402).

Input parameters:

- `direction` (string, required)
- `price` (number, required)
- `symbol` (string, required): Instrument symbol
- `ttl_hours` (integer)
- `webhook_url` (string, required): Public HTTPS URL that receives the signed trigger.fired event

## Diagnostics

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

## Score history

- 2026-10-23: 61
- 2026-10-22: 61
- 2026-10-21: 60
- 2026-10-20: 60

## Common questions

### What is the NythosX Market Data MCP server?

NythosX Market Data is an MCP server listed in the public MCP registry as com.nythosx.market/market-data. Crypto/stock trade setups, signal bias, levels, regime, odds. Free track record. Pay per call, x402. This page covers its hosted endpoint (https://market.nythosx.com/mcp).

### Is the NythosX Market Data MCP server safe to use?

NythosX Market Data scores 61 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 NythosX Market Data MCP server expose?

NythosX Market Data exposes 10 tools: list_symbols, get_track_record, get_free_snapshot, get_trigger_status, get_trade_plan, and 5 more. Their descriptions and schemas cost roughly 1,255 tokens of context every time the server is loaded.

### Does the NythosX Market Data MCP server require authentication?

No. We connected to NythosX Market Data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the NythosX Market Data MCP server still maintained?

NythosX Market Data is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://market.nythosx.com/mcp
- Website: https://market.nythosx.com/docs/api#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-nythosx-market-market-data/market.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nythosx-market-market-data/market.json
- HTML version of this page: https://verifymcp.io/servers/com-nythosx-market-market-data/market