Nota
REMOTE · NOTA-RYO.VERCEL.APP · SCANNED SEP 20
Read-only crypto research skills that check a price, RSI and ATR against independent sources.
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 Security80
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2103 tokens (~105/item across 20 items; 9 tools + 11 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 Management33
- Stability observed for 10 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
How do I install the Nota MCP server?
Nota is a hosted endpoint at https://nota-ryo.vercel.app/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 · nota-ryo.vercel.app
claude mcp add --transport http pugarhuda-nota 'https://nota-ryo.vercel.app/mcp'
{
"mcpServers": {
"pugarhuda-nota": {
"url": "https://nota-ryo.vercel.app/mcp"
}
}
} {
"servers": {
"pugarhuda-nota": {
"type": "http",
"url": "https://nota-ryo.vercel.app/mcp"
}
}
} [mcp_servers.pugarhuda-nota] url = "https://nota-ryo.vercel.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pugarhuda-nota": {
"type": "remote",
"url": "https://nota-ryo.vercel.app/mcp",
"enabled": true
}
}
} openclaw mcp add pugarhuda-nota --url 'https://nota-ryo.vercel.app/mcp' --transport streamable-http
mcp_servers:
pugarhuda-nota:
url: "https://nota-ryo.vercel.app/mcp" {
"McpServers": {
"pugarhuda-nota": {
"Transport": "http",
"Url": "https://nota-ryo.vercel.app/mcp"
}
}
} assistant mcp add pugarhuda-nota -t streamable-http -u 'https://nota-ryo.vercel.app/mcp'
{
"mcpServers": {
"pugarhuda-nota": {
"type": "http",
"url": "https://nota-ryo.vercel.app/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.
- 20 Sept 26 +10
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “narrative_convergence” rewrote its description, which is the text the model reads security
- Tool “news_verify” rewrote its description, which is the text the model reads security
- Tool “positioning_check” rewrote its description, which is the text the model reads security
- Tool “price_crosscheck” rewrote its description, which is the text the model reads security
- Tool “technicals_crosscheck” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- MCP protocol: fail → pass ▲ functional
- Tool “move_base_rate” now declares an output schema ▲ functional
- Tool “narrative_convergence” now declares an output schema ▲ functional
- Tool “news_verify” now declares an output schema ▲ functional
- Tool “positioning_check” now declares an output schema ▲ functional
- Tool “price_crosscheck” now declares an output schema ▲ functional
- Tool “technicals_crosscheck” now declares an output schema ▲ functional
- Tool “verdict_track_record” now declares an output schema ▲ functional
- First check of Capabilities: pass functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- MCP protocol version: 2025-03-26 → 2026-07-28 functional
- New resource “BTC receipt 6a0e951bdeeb” functional
- New resource “ETH receipt 775ba11a7cd3” functional
- New resource “Receipt card” functional
- New resource “SOL receipt ef3a11aea080” functional
- Server version: 0.1.0 → 0.2.0 functional
- New tool “crowd_odds” functional
- New tool “liquidity_check” functional
- “positioning_check” added an optional parameter “atr_stop_pct” cosmetic
- “narrative_convergence” reworded the description of “tokens” cosmetic
- “positioning_check” reworded the description of “peer_derivatives” cosmetic
- “positioning_check” reworded the description of “reference_derivatives” cosmetic
- “technicals_crosscheck” reworded the description of “days” cosmetic
- Tool “move_base_rate” changed its title: Move Base Rate cosmetic
- Tool “narrative_convergence” changed its title: Narrative Convergence cosmetic
- Tool “news_verify” changed its title: News Verify cosmetic
- Tool “positioning_check” changed its title: Positioning Check cosmetic
- Tool “price_crosscheck” changed its title: Price Crosscheck cosmetic
- Tool “technicals_crosscheck” changed its title: Technicals Crosscheck cosmetic
- Tool “verdict_track_record” changed its title: Verdict Track Record cosmetic
- 19 Sept 26 0
- Schema quality: 91 → 103 ▼ functional
- New resource “ETH receipt cd5ada18b179” functional
- New resource “SOL receipt 29d5ca390412” functional
- New tool “move_base_rate” functional
- New tool “positioning_check” functional
- New tool “verdict_track_record” functional
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 10 Sept 26 66
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 20 Sept 2026 · Probed https://nota-ryo.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 29 Aug 2026 | 27 Nov 2026 | RSA 2048 | SHA256-RSA | f7911168ffa7d0f4135e24792e7a52a8 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nota-ryo.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; media-src 'self'; connect-src 'self'; frame-ancestors 'none'; base-uri 'none'; form-action 'self'; object-src 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nota-ryo.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://nota-ryo.vercel.app/mcp | HTTPS enforced | 308 | https://nota-ryo.vercel.app/mcp |
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 →
crowd_odds Crowd Odds ~155
Prediction-market implied probability that a token trades higher than now at a horizon: the Polymarket 'above $K on <date>' ladder (Kalshi's KX<coin>D ladder as fallback) expiring within a day of now + horizon, liquid strikes only, made monotone and interpolated at spot. BTC, ETH, SOL, XRP (and DOGE on Kalshi); null when no market.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_days | integer | – | 1 to 14 (default 7) |
| spot | number | – | Price to read the ladder at (default: Binance spot, which is what Polymarket's crypto ladders resolve on) |
| symbol | string | yes | Token symbol, e.g. BTC |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
liquidity_check Liquidity Check ~107
Macro liquidity from DefiLlama (no key): 7-day and 30-day change of the total USD stablecoin supply, and of DeFi TVL on the token's own chain (ETH, SOL, BNB, AVAX and other L1/L2 tokens). Each leg reports its own as_of and availability; a token without a chain of its own gets no TVL rather than a borrowed one.
| Name | Type | Req | Description |
|---|---|---|---|
| symbol | string | yes | Token symbol, e.g. SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
move_base_rate Move Base Rate ~215
Empirical probability that a token moves k ATRs (up or down, touched or closed beyond) within h days, counted from ~400 days of OKX daily candles on days in the same ATR tercile as today, with a time-split holdout. Pass RYO's atr_14_pct to measure the distance in RYO's ATR; k=0 with event=close gives the plain 'higher after h days' rate.
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | – | YYYY-MM-DD: use only candles closed before this day (scoring a past call) |
| atr_14_pct | number | – | RYO's ATR(14) as % of price (analyze_token or deep_analysis) |
| direction | string | – | Default up |
| event | string | – | Default touch |
| horizon_days | integer | – | 1 to 14 (default 3) |
| k | number | – | Distance in ATRs (default 1) |
| symbol | string | yes | Token symbol, e.g. SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
narrative_convergence Narrative Convergence ~145
Monitor up to 20 user-selected voices (Telegram public channels, Bluesky and X handles) and report which tokens they mention, lexicon-scored sentiment per token, conviction and urgency, and whether the voices converge: at least two voices carry a non-zero net sentiment on the token and every one of them has the same sign.
| Name | Type | Req | Description |
|---|---|---|---|
| hours | integer | – | Look-back window in hours (default 24) |
| tokens | array | – | Symbols to track; default = every cashtag, ticker or name of a known major found |
| voices | array | yes | Up to 20 ids like tg:WatcherGuru, bs:handle.bsky.social or x:handle |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
news_verify News Verify ~114
Verify a crypto news claim: count independent domains reporting it (four outlets' RSS headlines plus Tavily or Venice web search), count those whose headline leans the opposite way, and attach the token's RYO analyze_token evidence so the story and the market read sit side by side.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | yes | The story to verify, in one sentence |
| max_results | integer | – | Search results to inspect (default 6, max 20) |
| symbol | string | – | Token symbol to attach market evidence for |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
positioning_check Positioning Check ~277
Decide, field by field, whether RYO's deep_analysis derivatives block can be cited as evidence about this token (identical values across other tokens, sign conflicts with OKX coin-terms open interest), and report OKX perp positioning: premium over spot on OKX and Hyperliquid, 24 h open-interest change in coins, long/short account ratio and its 100-hour percentile, and for BTC/ETH Deribit's DVOL implied 7-day move as a check on stop distance.
| Name | Type | Req | Description |
|---|---|---|---|
| atr_stop_pct | number | – | Stop distance in % of price (e.g. RYO's 1.5 x atr_14_pct), checked against the DVOL implied 7-day move |
| peer_derivatives | array | – | Same-day RYO derivatives blocks for other symbols: [{symbol, funding_rate_bps, open_interest_change_24h_pct}]; taken from the day's scorecard locks when omitted |
| reference_derivatives | object | – | RYO deep_analysis data.derivatives for this symbol; fetched from RYO when omitted and a RYO key is set |
| ryo_btc_funding_bps | number | – | Latest BTC funding from RYO monitor_market_sentiment_shift (evidence.funding.latest_bps) |
| symbol | string | yes | Token symbol, e.g. SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
price_crosscheck Price Crosscheck ~146
Fetch independent USD spot prices for a symbol from CoinGecko, Coinbase, Kraken, Binance and DefiLlama (no keys), drop a source that disagrees with the rest as an outlier, report median and spread, and flag how far a reference price (e.g. RYO's) deviates from them.
| Name | Type | Req | Description |
|---|---|---|---|
| reference_fear_greed | number | – | A Fear & Greed value to compare with alternative.me |
| reference_path | string | – | Where the reference price came from |
| reference_price | number | – | Price to compare against, e.g. RYO deep_analysis price |
| symbol | string | yes | Token symbol, e.g. SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
technicals_crosscheck Technicals Crosscheck ~164
Recompute RSI(14) and ATR(14) (Wilder smoothing) from 200 closed UTC-day candles (OKX, else Binance, else CoinGecko 4h OHLC aggregated to days) plus 1d/7d/30d performance, and report how far reference values (e.g. RYO's) deviate from the independent calculation.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | lookback for performance, 7..90 (indicators always use 200 closed daily candles) |
| reference_atr_14 | number | – | ATR(14) in USD to compare against |
| reference_rsi_14 | number | – | RSI(14) to compare against |
| symbol | string | yes | Token symbol, e.g. SOL |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
verdict_track_record Verdict Track Record ~120
How RYO's own deep_analysis plans have fared: locked daily for 25 majors and settled on OKX hourly candles (stop or +1R target first, 24 h or 72 h). Returns counts by verdict and by confluence state, plans whose verdict leans against their own direction, and the latest locked verdict. Omit the symbol for all tokens.
| Name | Type | Req | Description |
|---|---|---|---|
| horizon_hours | integer | – | 24 (default) or 72 |
| symbol | string | – | Token symbol, e.g. SOL; omit for every token |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | – | – | – |
| availability | object | – | – |
| data | object | – | – |
| data_mode | string | – | – |
| request | object | – | – |
| schema_version | – | – | – |
| status | string | yes | – |
| summary | – | – | – |
| tool | string | yes | – |
| trace_id | – | – | – |
| warnings | array | – | – |
No examples provided.
What is the Nota MCP server?
Nota is an MCP server listed in the public MCP registry as io.github.PugarHuda/nota. Read-only crypto research skills that check a price, RSI and ATR against independent sources. This page covers its hosted endpoint (https://nota-ryo.vercel.app/mcp).
Is the Nota MCP server safe to use?
Nota scores 80 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 Nota MCP server expose?
Nota exposes 9 tools: narrative_convergence, news_verify, price_crosscheck, technicals_crosscheck, positioning_check, and 4 more. Their descriptions and schemas cost roughly 1,443 tokens of context every time the server is loaded.
Does the Nota MCP server require authentication?
No. We connected to Nota without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Nota MCP server still maintained?
Nota 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.