# Entry Risk Score (remote · entryriskscore.com)

Entry-risk score for Binance USDT-M perpetuals: how risky is entering now. Not a signal.

- Trust score: 0/100 (low)
- Change this week: −36
- Registry status: active
- Liveness: dead
- Owner verified: no
- Last scored: 2026-10-19

> **Dead**: every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically.

## Components

- remote · `entryriskscore.com`: 0/100 (this document), [markdown](https://verifymcp.io/servers/entryriskscore-entry-risk-score/api-v1-mcp.md), [page](https://verifymcp.io/servers/entryriskscore-entry-risk-score/api-v1-mcp)

## Channel facts

- Endpoint: `https://entryriskscore.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `required`
- 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-10-19.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Entry Risk Score MCP server?

Entry Risk Score is a hosted endpoint at https://entryriskscore.com/api/v1/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 entryriskscore-entry-risk-score 'https://entryriskscore.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "entryriskscore-entry-risk-score": {
      "url": "https://entryriskscore.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "entryriskscore-entry-risk-score": {
      "type": "http",
      "url": "https://entryriskscore.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.entryriskscore-entry-risk-score]
url = "https://entryriskscore.com/api/v1/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add entryriskscore-entry-risk-score --url 'https://entryriskscore.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  entryriskscore-entry-risk-score:
    url: "https://entryriskscore.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "entryriskscore-entry-risk-score": {
      "Transport": "http",
      "Url": "https://entryriskscore.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add entryriskscore-entry-risk-score -t streamable-http -u 'https://entryriskscore.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "entryriskscore-entry-risk-score": {
      "type": "http",
      "url": "https://entryriskscore.com/api/v1/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-19 (score 0, −7)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-18 (score 7, −7)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-17 (score 14, −8)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-16 (score 22, −7)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-15 (score 29, −7)

The score moved with no change recorded against any check. We would rather say so than guess.

### 2026-10-13 (score 36, 0)

- [security regression] Transport: unverified → fail
- [security regression] Authorization: fail → unverified
- [security regression] HSTS header: pass → unverified
- [security] Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- [functional] Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities.
- [functional] Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.

### 2026-10-09 (score 36)

First indexed and scored.

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/entryriskscore-entry-risk-score/api-v1-mcp#diagnostics

## Score history

- 2026-10-19: 0
- 2026-10-18: 7
- 2026-10-17: 14
- 2026-10-16: 22
- 2026-10-15: 29
- 2026-10-14: 36
- 2026-10-13: 36
- 2026-10-12: 36
- 2026-10-10: 36
- 2026-10-09: 36

## Common questions

### What is the Entry Risk Score MCP server?

Entry Risk Score is an MCP server listed in the public MCP registry as io.github.entryriskscore/entry-risk-score. Entry-risk score for Binance USDT-M perpetuals: how risky is entering now. Not a signal. This page covers its hosted endpoint (https://entryriskscore.com/api/v1/mcp).

### Is the Entry Risk Score MCP server safe to use?

Entry Risk Score scores 0 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.

### Does the Entry Risk Score MCP server require authentication?

Its publisher declares that Entry Risk Score requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.

### Is the Entry Risk Score MCP server still maintained?

Entry Risk Score has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 12 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://entryriskscore.com/api/v1/mcp
- Authorisation metadata: https://entryriskscore.com/.well-known/oauth-protected-resource/api/v1/mcp
- Website: https://entryriskscore.com/docs/mcp
- Changelog RSS feed: https://verifymcp.io/servers/entryriskscore-entry-risk-score/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/entryriskscore-entry-risk-score/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/entryriskscore-entry-risk-score/api-v1-mcp