# io.github.junct-bot/binance-mcp (remote · binance.mcp.junct.dev)

Binance - 340 tools for market data, order books, and trading pairs

- Trust score: 11/100 (low)
- Change this week: −3
- Registry status: active
- Liveness: degraded
- Owner verified: no
- Last scored: 2026-08-03

> **Degraded**: one or more channels of this server are currently unreachable; their trust score is decaying and will reach 0 if they stay down.

## Components

- remote · `binance.mcp.junct.dev`: 11/100 (this document), [markdown](https://verifymcp.io/servers/junct-bot-binance-mcp/binance.md), [page](https://verifymcp.io/servers/junct-bot-binance-mcp/binance)

## Channel facts

- Endpoint: `https://binance.mcp.junct.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.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-08-03.

- **Endpoint Security**: 0/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - 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.
- **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.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 4 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

### Claude

```bash
claude mcp add --transport http junct-bot-binance-mcp https://binance.mcp.junct.dev/mcp
```

### Codex

```toml
[mcp_servers.junct-bot-binance-mcp]
url = "https://binance.mcp.junct.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "junct-bot-binance-mcp": {
      "type": "remote",
      "url": "https://binance.mcp.junct.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add junct-bot-binance-mcp --url https://binance.mcp.junct.dev/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  junct-bot-binance-mcp:
    url: "https://binance.mcp.junct.dev/mcp"
```

### Other

```json
{
  "mcpServers": {
    "junct-bot-binance-mcp": {
      "type": "http",
      "url": "https://binance.mcp.junct.dev/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-08-02 (score 11, −3)

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

### 2026-07-31 (score 14, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 14, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 14, 0)

- [security regression] HSTS header: fail → unverified
- [security regression] HTTPS: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security] Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- [security] Transport: Transport check failed: declared streamable-http, but we couldn't connect to verify it.

### 2026-07-27 (score 14, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 14)

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/junct-bot-binance-mcp/binance#diagnostics

## Score history

- 2026-08-03: 11
- 2026-08-02: 11
- 2026-08-01: 14
- 2026-07-31: 14
- 2026-07-30: 14
- 2026-07-29: 14
- 2026-07-28: 14
- 2026-07-27: 14
- 2026-07-26: 14

## Links

- Remote endpoint: https://binance.mcp.junct.dev/mcp
- Repository: https://github.com/junct-bot/binance-mcp
- Website: https://binance.mcp.junct.dev/
- Changelog RSS feed: https://verifymcp.io/servers/junct-bot-binance-mcp/binance/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/junct-bot-binance-mcp/binance/changelog.json
- HTML version of this page: https://verifymcp.io/servers/junct-bot-binance-mcp/binance