# com.thecryptoport/cryptoport-port (remote · cryptoport-mcp.cryptoport-port.workers.dev)

Daily board of what crypto YouTube channels said: coin calls, stances, catalysts. Free, no key.

- Trust score: 68/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `cryptoport-mcp.cryptoport-port.workers.dev`: 68/100 (this document), [markdown](https://verifymcp.io/servers/com-thecryptoport-cryptoport-port/cryptoport-mcp.md), [page](https://verifymcp.io/servers/com-thecryptoport-cryptoport-port/cryptoport-mcp)

## Channel facts

- Endpoint: `https://cryptoport-mcp.cryptoport-port.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## 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-09-20.

- **Endpoint Security**: 46/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 6 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 enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 68/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1270 tokens (~211/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 70/100
  - Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 com.thecryptoport/cryptoport-port MCP server?

com.thecryptoport/cryptoport-port is a hosted endpoint at https://cryptoport-mcp.cryptoport-port.workers.dev/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-thecryptoport-cryptoport-port 'https://cryptoport-mcp.cryptoport-port.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-thecryptoport-cryptoport-port": {
      "url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-thecryptoport-cryptoport-port": {
      "type": "http",
      "url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-thecryptoport-cryptoport-port]
url = "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-thecryptoport-cryptoport-port": {
      "type": "remote",
      "url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-thecryptoport-cryptoport-port --url 'https://cryptoport-mcp.cryptoport-port.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-thecryptoport-cryptoport-port:
    url: "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-thecryptoport-cryptoport-port": {
      "Transport": "http",
      "Url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-thecryptoport-cryptoport-port -t streamable-http -u 'https://cryptoport-mcp.cryptoport-port.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-thecryptoport-cryptoport-port": {
      "type": "http",
      "url": "https://cryptoport-mcp.cryptoport-port.workers.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-09-19 (score 68, +1)

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

### 2026-09-16 (score 67, +1)

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

### 2026-09-14 (score 66, +1)

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

### 2026-09-12 (score 65, +1)

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

### 2026-09-10 (score 64, +1)

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

### 2026-09-08 (score 63, +1)

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

### 2026-09-07 (score 62, 0)

- [functional regression] Schema quality: 179 → 211
- [cosmetic] “board_snapshot” reworded the description of “payment”
- [cosmetic] “catalysts” reworded the description of “payment”
- [cosmetic] “coin” reworded the description of “payment”
- [cosmetic] “stance_history” reworded the description of “payment”

### 2026-09-04 (score 62, +1)

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

## MCP tools (6)

### `latest_board` (~124 tokens)

Latest board

FREE. The whole current board: every coin row named in the latest videos of the tracked crypto YouTube channels, with the stance, the call and the dated specifics. Free. Upstream briefs land on about 71% of days; board content is same-day roughly half the time and is never more than three days old. Not real-time. Every payload carries stale / stale_days / built_from_brief_date — read them. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

### `search` (~112 tokens)

Search the board

FREE. Substring search across the published columns (ticker, canonical name, call, specifics, tier, channel, stance) of the current board. Returns matches with the per-coin URL. Free. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Input parameters:

- `limit` (integer): Max results, default 25
- `q` (string, required): Substring to look for, e.g. 'ETF' or 'SOL'

### `coin` (~282 tokens)

One coin's current row

FREE. One ticker's full current record — tier, channel, call, specifics, stance and previous stance, breadth, first/last seen — plus its catalysts and its anchor proof. The same facts are also free as static JSON at /coins/<TICKER>.json; this tool is the queryable form, not privileged content. Upstream briefs land on about 71% of days; board content is same-day roughly half the time and is never more than three days old. Not real-time. Every payload carries stale / stale_days / built_from_brief_date — read them. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Input parameters:

- `payment` (string): Optional x402 payment payload: the value you would send in the PAYMENT-SIGNATURE header (base64 JSON, x402 v2). Call without it first: the tool answers with the 402 terms and carries the verbatim PAY…
- `ticker` (string, required): Ticker as published, e.g. BTC

### `stance_history` (~278 tokens)

Stance arc as a dated series

FREE. The full stance arc for one ticker parsed into a dated series — one point per brief date with the movement (up / flat / down) — plus first and last brief, mention count and the flip flag. Derived from the published `arc` string; it is a parsed shape, not withheld data. Upstream briefs land on about 71% of days; board content is same-day roughly half the time and is never more than three days old. Not real-time. Every payload carries stale / stale_days / built_from_brief_date — read them. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Input parameters:

- `payment` (string): Optional x402 payment payload: the value you would send in the PAYMENT-SIGNATURE header (base64 JSON, x402 v2). Call without it first: the tool answers with the 402 terms and carries the verbatim PAY…
- `ticker` (string, required): Ticker as published, e.g. SOL

### `catalysts` (~250 tokens)

Dated catalysts, windowed

FREE. Dated, falsifiable events named on the board, optionally limited to those due within N days. Past-due events are excluded when a window is given. Upstream briefs land on about 71% of days; board content is same-day roughly half the time and is never more than three days old. Not real-time. Every payload carries stale / stale_days / built_from_brief_date — read them. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Input parameters:

- `payment` (string): Optional x402 payment payload: the value you would send in the PAYMENT-SIGNATURE header (base64 JSON, x402 v2). Call without it first: the tool answers with the 402 terms and carries the verbatim PAY…
- `window` (integer): Look-ahead window in days; omit for all catalysts

### `board_snapshot` (~224 tokens)

Historical daily board (not yet available)

FREE. The whole board as it stood on a past date, with that day's anchor proof. NOT YET AVAILABLE: only the current board is emitted, and no dated snapshot series has been anchored yet. The tool answers with available:false and is NOT charged while that is true. Commentary on public statements, not advice. This tool does not accept portfolio, position or risk-profile inputs and will refuse them with HTTP 400.

Input parameters:

- `date` (string, required): ISO date, e.g. 2026-08-20
- `payment` (string): Optional x402 payment payload: the value you would send in the PAYMENT-SIGNATURE header (base64 JSON, x402 v2). Call without it first: the tool answers with the 402 terms and carries the verbatim PAY…

## Diagnostics

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

## Score history

- 2026-09-20: 68
- 2026-09-19: 68
- 2026-09-18: 67
- 2026-09-17: 67
- 2026-09-16: 67
- 2026-09-15: 66
- 2026-09-14: 66
- 2026-09-13: 65
- 2026-09-12: 65
- 2026-09-11: 64
- 2026-09-10: 64
- 2026-09-09: 63
- 2026-09-08: 63
- 2026-09-07: 62
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 62
- 2026-09-03: 61
- 2026-09-02: 61
- 2026-09-01: 60
- 2026-08-31: 60
- 2026-08-30: 59

## Common questions

### What is the com.thecryptoport/cryptoport-port MCP server?

com.thecryptoport/cryptoport-port is an MCP server listed in the public MCP registry as com.thecryptoport/cryptoport-port. Daily board of what crypto YouTube channels said: coin calls, stances, catalysts. Free, no key. This page covers its hosted endpoint (https://cryptoport-mcp.cryptoport-port.workers.dev/mcp).

### Is the com.thecryptoport/cryptoport-port MCP server safe to use?

com.thecryptoport/cryptoport-port scores 68 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 com.thecryptoport/cryptoport-port MCP server expose?

com.thecryptoport/cryptoport-port exposes 6 tools: latest_board, search, coin, stance_history, catalysts, board_snapshot. Their descriptions and schemas cost roughly 1,270 tokens of context every time the server is loaded.

### Does the com.thecryptoport/cryptoport-port MCP server require authentication?

No. We connected to com.thecryptoport/cryptoport-port without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.thecryptoport/cryptoport-port MCP server still maintained?

com.thecryptoport/cryptoport-port is still listed as active in the MCP registry. We last reached this channel on 20 September 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://cryptoport-mcp.cryptoport-port.workers.dev/mcp
- Repository: https://github.com/thecryptoport-mcp/cryptoport-port
- Website: https://thecryptoport.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-thecryptoport-cryptoport-port/cryptoport-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-thecryptoport-cryptoport-port/cryptoport-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-thecryptoport-cryptoport-port/cryptoport-mcp