# SignalStates (remote · signalstates.com)

Crypto futures data: funding, open interest, liquidation maps, liquidation and position-size math.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `signalstates.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-signalstates-signalstates/api-mcp.md), [page](https://verifymcp.io/servers/com-signalstates-signalstates/api-mcp)

## Channel facts

- Endpoint: `https://signalstates.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 790 tokens (~79/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 25% 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**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SignalStates MCP server?

SignalStates is a hosted endpoint at https://signalstates.com/api/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-signalstates-signalstates 'https://signalstates.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-signalstates-signalstates": {
      "url": "https://signalstates.com/api/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  com-signalstates-signalstates:
    url: "https://signalstates.com/api/mcp"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "com-signalstates-signalstates": {
      "type": "http",
      "url": "https://signalstates.com/api/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-20 (score 70, +1)

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

### 2026-11-18 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 68)

First indexed and scored.

## MCP tools (10)

### `market_overview` (~52 tokens)

Market overview

List USDT perpetual contracts with price, 24h change, 24h volume and funding rate, sorted by volume, change or funding.

Input parameters:

- `limit` (integer)
- `sort` (string)

### `coin_snapshot` (~78 tokens)

Coin snapshot

One contract now: mark price, funding rate and APR, next funding time, open interest and its 24h change, long/short account ratios, taker buy/sell ratio, max leverage.

Input parameters:

- `symbol` (string, required): Coin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

### `funding_history` (~69 tokens)

Funding history

Funding rate history of one contract over up to 30 days, with latest, average, min, max and average APR.

Input parameters:

- `days` (integer)
- `symbol` (string, required): Coin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

### `liquidation_map` (~66 tokens)

Liquidation map (estimated)

Estimated liquidation clusters above and below the current price for one contract: totals, the largest clusters and their price levels. Estimates, not actual orders.

Input parameters:

- `symbol` (string, required): Coin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

### `fear_greed_index` (~32 tokens)

Crypto Fear & Greed Index

Today's 0-100 crypto Fear & Greed reading built from futures data, with its four component scores.

### `altcoin_season_index` (~40 tokens)

Altcoin Season Index

Share of the 100 most traded altcoins beating Bitcoin over 90 days (75+ altcoin season, 25 or less Bitcoin season).

### `market_report_today` (~30 tokens)

Daily market report

Today's crypto futures market state (trend, volatility, liquidity, breadth, funding) from fixed numeric rules.

### `liquidation_price` (~100 tokens)

Liquidation price calculator

Liquidation price of an isolated-margin futures position, using the contract's real maintenance-margin tiers. Give margin_usdt or quantity.

Input parameters:

- `entry` (number, required)
- `leverage` (number, required)
- `margin_usdt` (number)
- `quantity` (number)
- `side` (string, required)
- `symbol` (string, required): Coin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

### `position_size` (~116 tokens)

Position size calculator

Position size from entry, stop and the USDT you are willing to lose, rounded to the contract's step, with margin, fees, loss at the stop and a warning if liquidation comes before the stop.

Input parameters:

- `entry` (number, required)
- `leverage` (number, required)
- `risk_usdt` (number, required)
- `side` (string, required)
- `stop` (number, required)
- `symbol` (string, required): Coin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).

### `preflight_link` (~107 tokens)

Pre-Flight check link

A link that opens SignalStates Pre-Flight with a planned trade filled in; it checks the stop against normal noise, liquidation, holding cost, crowding and size.

Input parameters:

- `entry` (number)
- `leverage` (number)
- `side` (string, required)
- `stop` (number)
- `symbol` (string, required): Coin of a USDT perpetual contract, e.g. BTC, ETH, SOL (BTCUSDT also works).
- `target` (number)

## Diagnostics

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

## Score history

- 2026-11-21: 70
- 2026-11-20: 70
- 2026-11-19: 69
- 2026-11-18: 69
- 2026-11-17: 68

## Common questions

### What is the SignalStates MCP server?

SignalStates is an MCP server listed in the public MCP registry as com.signalstates/signalstates. Crypto futures data: funding, open interest, liquidation maps, liquidation and position-size math. This page covers its hosted endpoint (https://signalstates.com/api/mcp).

### Is the SignalStates MCP server safe to use?

SignalStates scores 70 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 SignalStates MCP server expose?

SignalStates exposes 10 tools: market_overview, coin_snapshot, funding_history, liquidation_map, fear_greed_index, and 5 more. Their descriptions and schemas cost roughly 690 tokens of context every time the server is loaded.

### Does the SignalStates MCP server require authentication?

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

### Is the SignalStates MCP server still maintained?

SignalStates is still listed as active in the MCP registry. We last reached this channel on 21 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 SignalStates MCP server?

VerifyMCP ran 13 checks on SignalStates, 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://signalstates.com/api/mcp
- Website: https://signalstates.com/tools
- Changelog RSS feed: https://verifymcp.io/servers/com-signalstates-signalstates/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-signalstates-signalstates/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-signalstates-signalstates/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-signalstates-signalstates/api-mcp
