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.
Available components
Last scanned (7 hours ago)
Scores higher than 79% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Schema quality: 179 → 211 ▼ functional
- “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” cosmetic
- 31 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 30 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://cryptoport-mcp.cryptoport-port.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cryptoport-port.workers.dev | CN=WE1,O=Google Trust Services,C=US | 25 Oct 2026 | 23 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | da0973f0b79222540ecf397d917c1916 |
| SANs: cryptoport-port.workers.dev, *.cryptoport-port.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cryptoport-mcp.cryptoport-port.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cryptoport-mcp.cryptoport-port.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://cryptoport-mcp.cryptoport-port.workers.dev/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
board_snapshot Historical daily board (not yet available) ~224
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 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… |
No output schema declared.
No examples provided.
catalysts Dated catalysts, windowed ~250
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
coin One coin's current row ~282
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Ticker as published, e.g. BTC |
No output schema declared.
No examples provided.
latest_board Latest board ~124
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search Search the board ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results, default 25 |
| q | string | yes | Substring to look for, e.g. 'ETF' or 'SOL' |
No output schema declared.
No examples provided.
stance_history Stance arc as a dated series ~278
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Ticker as published, e.g. SOL |
No output schema declared.
No examples provided.
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.
remote · cryptoport-mcp.cryptoport-port.workers.dev
claude mcp add --transport http com-thecryptoport-cryptoport-port 'https://cryptoport-mcp.cryptoport-port.workers.dev/mcp'
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 79 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.