com.thecryptoport/cryptoport-port
REMOTE · CRYPTOPORT-MCP.CRYPTOPORT-PORT.WORKERS.DEV · SCANNED SEP 20
Daily board of what crypto YouTube channels said: coin calls, stances, catalysts. Free, no key.
Available components
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- 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 Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
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'
{
"mcpServers": {
"com-thecryptoport-cryptoport-port": {
"url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
}
}
} {
"servers": {
"com-thecryptoport-cryptoport-port": {
"type": "http",
"url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
}
}
} [mcp_servers.com-thecryptoport-cryptoport-port] url = "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
{
"$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 mcp add com-thecryptoport-cryptoport-port --url 'https://cryptoport-mcp.cryptoport-port.workers.dev/mcp' --transport streamable-http
mcp_servers:
com-thecryptoport-cryptoport-port:
url: "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp" {
"McpServers": {
"com-thecryptoport-cryptoport-port": {
"Transport": "http",
"Url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
}
}
} assistant mcp add com-thecryptoport-cryptoport-port -t streamable-http -u 'https://cryptoport-mcp.cryptoport-port.workers.dev/mcp'
{
"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.
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.
- 19 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 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
- 4 Sept 26 +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.
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 20 Sept 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 | 27 Aug 2026 | 25 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | c7a1b2bb4b5d5a4b0e046ec8ba7a01a5 |
| 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.
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.