cryptoport-port
Daily board of what crypto YouTube channels said: coin calls, stances, catalysts. Free, no key.
Should I use this
Quality & Safety
Based on automated analysis of tool definitions and protocol compliance.
Context Cost
This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.
Install
One-Click Install
Add this to your `claude_desktop_config.json` file:
{
"mcpServers": {
"cryptoport-port": {
"url": "https://cryptoport-mcp.cryptoport-port.workers.dev/mcp"
}
}
}Remote endpoints
https://cryptoport-mcp.cryptoport-port.workers.dev/mcpstreamable-httpWhat it can do
Tool inventory
Tools (6)
🟢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.
Input Schema
{
"type": "object",
"properties": {},
"required": [],
"additionalProperties": false
}🟢search(q, limit)
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 Schema
{
"type": "object",
"properties": {
"q": {
"type": "string",
"description": "Substring to look for, e.g. 'ETF' or 'SOL'"
},
"limit": {
"type": "integer",
"description": "Max results, default 25",
"minimum": 1,
"maximum": 100
}
},
"required": [
"q"
],
"additionalProperties": false
}🟢coin(ticker, payment)
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 Schema
{
"type": "object",
"properties": {
"ticker": {
"type": "string",
"description": "Ticker as published, e.g. BTC"
},
"payment": {
"type": "string",
"description": "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 PAYMENT-REQUIRED header value in `x402` — hand that to an x402 client to build the payload, which settles testnet USDC on Base Sepolia — then call again with this field. The receipt (tx_hash, payer, network) comes back in `settlement`."
}
},
"required": [
"ticker"
],
"additionalProperties": false
}🟢stance_history(ticker, payment)
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 Schema
{
"type": "object",
"properties": {
"ticker": {
"type": "string",
"description": "Ticker as published, e.g. SOL"
},
"payment": {
"type": "string",
"description": "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 PAYMENT-REQUIRED header value in `x402` — hand that to an x402 client to build the payload, which settles testnet USDC on Base Sepolia — then call again with this field. The receipt (tx_hash, payer, network) comes back in `settlement`."
}
},
"required": [
"ticker"
],
"additionalProperties": false
}🟢catalysts(window, payment)
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 Schema
{
"type": "object",
"properties": {
"window": {
"type": "integer",
"description": "Look-ahead window in days; omit for all catalysts",
"minimum": 0
},
"payment": {
"type": "string",
"description": "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 PAYMENT-REQUIRED header value in `x402` — hand that to an x402 client to build the payload, which settles testnet USDC on Base Sepolia — then call again with this field. The receipt (tx_hash, payer, network) comes back in `settlement`."
}
},
"required": [],
"additionalProperties": false
}🟢board_snapshot(date, payment)
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 Schema
{
"type": "object",
"properties": {
"date": {
"type": "string",
"description": "ISO date, e.g. 2026-08-20"
},
"payment": {
"type": "string",
"description": "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 PAYMENT-REQUIRED header value in `x402` — hand that to an x402 client to build the payload, which settles testnet USDC on Base Sepolia — then call again with this field. The receipt (tx_hash, payer, network) comes back in `settlement`."
}
},
"required": [
"date"
],
"additionalProperties": false
}Community
Evidence