Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Assistant Hub

REMOTE · RMASSISTANTHUB.IO

Ranked crypto setups with a graded track record, and trading skills with public records.

+11 this week 85 Trust /100

Last scanned (15 hours ago)

Scores higher than 92% of remote servers

Reachable. Last reached 25 Oct 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security83
Transport & Reachability100
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 (good).Pass
  • Tool/resource definitions use about 1199 tokens (~70/item across 17 items; 12 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
  • Stability observed for 22 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 24 Oct 26 +9
    • Authorization: unverified → partial ▲ security
    • Tool “best_setups” rewrote its description, which is the text the model reads security
    • Tool “get_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_skill_regime” rewrote its description, which is the text the model reads security
    • Tool “install_trading_skill” rewrote its description, which is the text the model reads security
    • Schema quality: excellent → good functional
    • MCP protocol version: 2024-11-05 → 2025-06-18 functional
    • Tool “best_setups” changed its title: Ranked crypto setups (fixed formula) cosmetic
    • Tool “get_forecast” changed its title: Indicator snapshot for a coin cosmetic
    • Tool “get_setups_track_record” changed its title: Setups track record vs BTC cosmetic
    • Tool “get_skill_regime” changed its title: Check a skill's regime gate (paper) cosmetic
    • Tool “get_trading_skill” changed its title: Get a paper trading skill cosmetic
    • Tool “get_whale_intel” changed its title: Recent transfers note (narrow) cosmetic
    • Tool “install_trading_skill” changed its title: Get a paper skill bundle cosmetic
    • Tool “list_trading_skills” changed its title: List paper trading skills cosmetic
    • Tool “pulse_deep_dive” changed its title: Daily Pulse deep-dive cosmetic
    • Tool “research_coin” changed its title: Multi-model research note cosmetic
    • Tool “search_signals” changed its title: Browse community signals cosmetic
    • Tool “strategy_analysis” changed its title: Strategy Lab backtest cosmetic
  • 22 Oct 26 +1

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

  • 20 Oct 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.

  • 18 Oct 26 +1
    • Server version: 0.9.8 → 0.9.9 functional
  • 16 Oct 26 +1
    • Server version: 0.9.7 → 0.9.8 functional
  • 14 Oct 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.

  • 12 Oct 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.

  • 10 Oct 26 +1

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

Diagnostics

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 25 Oct 2026 · Probed https://rmassistanthub.io/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=rmassistanthub.io CN=YE1,O=Let's Encrypt,C=US 3 Sept 2026 2 Dec 2026 ECDSA 256 ECDSA-SHA384 6452ff369bb1d987afa7e7675d8088aacb4
SANs: *.rmassistanthub.io, rmassistanthub.io
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of rmassistanthub.io. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
io. present 38690, 57355 8, 8 Verified
rmassistanthub.io. present 2371 13 Verified
rmassistanthub.io. Verified address RRset verified with the apex keys
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=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://s3.tradingview.com https://cdn.jsdelivr.net https://accounts.google.com https://static.cloudflareinsights.com/beacon.min.js https://static.cloudflareinsights.com/beacon.min.js/; style-src 'self' 'unsafe-inline' https://cdn.jsdelivr.net https://fonts.googleapis.com https://accounts.google.com; font-src 'self' https://cdn.jsdelivr.net https://fonts.gstatic.com; worker-src 'self' blob:; frame-src 'self' https://s.tradingview.com https://www.tradingview.com https://accounts.google.com; img-src 'self' data: https:; connect-src 'self' https://accounts.google.com https://oauth2.googleapis.com; base-uri 'self'; form-action 'self'; object-src 'none'; frame-ancestors 'none'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 3 probes
Transport URL Outcome Status Location
streamable-http https://rmassistanthub.io/mcp Verified 200
sse https://rmassistanthub.io/mcp Verified 200
http (plaintext) http://rmassistanthub.io/mcp HTTPS enforced 301 https://rmassistanthub.io/mcp
MCP tools · 12 exposed · ~1,027 tokens

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 →

Tool Tokens
best_setups ~111

Up to eight ranked setups for one window (1m, 1h, 1d, 1w or 1y), each with its score, the scored inputs, why now, what would invalidate it, a risk posture and an as-of time. Deterministic: no LLM touches the score. An empty window says why. The ranking has no proven edge yet, and its graded record is public. Free.

NameTypeReqDescription
windowstring–Time window (default 1d)

No output schema declared.

No examples provided.

get_forecast ~52

Indicator snapshot for a coin (SMA, RSI, Bollinger Bands) with a short written note. Not a price prediction.

NameTypeReqDescription
coinstringyesCoin symbol (BTC, ETH, SOL, etc.)

No output schema declared.

No examples provided.

get_setups_track_record ~68

How the desk's past setups turned out, per window: every published card graded as a buy over its window's horizon, close to close from exchange candles, against BTC over the same span. Hit rate withheld below 30 graded calls; the method is in the payload. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_skill_regime ~115

Whether a skill may open a position on each of its pairs now: the pair's regime from closed hourly bars, whether the skill allows it, for a feature-gated skill whether the newest bar's stored feature row and Fear & Greed (as readable at its close) pass the gate, whether the bars are fresh, and whether the skill is halted. Free.

NameTypeReqDescription
idstringyesSkill id
pairstring–One pair, e.g. BTC (default: all the skill's pairs)

No output schema declared.

No examples provided.

get_trading_skill ~75

One skill's full manifest (rules, parameters with bounds, risk contract, allowed regimes, engine config) and its card: the rules run on stored hourly bars before and since listing, next to buy-and-hold, with drawdown and round trips won after fees. Free.

NameTypeReqDescription
idstringyesSkill id

No output schema declared.

No examples provided.

get_whale_intel ~89

AI commentary on recent Etherscan transfers plus macro context. The on-chain input is narrow: for ETH, one well-known wallet's latest transactions; for LINK, the token contract's latest transfers; neither is size-filtered or market-wide. Other coins get no on-chain data, and the answer says so.

NameTypeReqDescription
coinstring–Coin symbol to analyze (default: ETH)

No output schema declared.

No examples provided.

install_trading_skill ~46

The installable bundle for a skill, pinned to its hash: manifest, run loop and risk contract. Paper trading only. Free.

NameTypeReqDescription
idstringyesSkill id

No output schema declared.

No examples provided.

list_trading_skills ~75

Installable trading skills: versioned, hashed rule sets an agent runs on paper in its own loop. Each lists its label (experimental, forward-tested, proven, halted), the regimes it may trade in, its pairs and install count. Also lists community uploads: unverified, paper-only, no card. Free.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pulse_deep_dive ~91

Deep-dive on the current Daily Macro Pulse, written by an AI from the pulse text alone: for each opportunity, the reasoning, what would invalidate it, risk level, catalysts to watch and a trade thesis framed as conditions to check. It has no on-chain, whale, order-book or live price data and says so rather than inventing any. Premium — x402 $0.30.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

research_coin ~83

Run the 3-agent orchestration pipeline (Sentiment: Grok, Technical: Groq, Synthesis: Gemini; Gemini stands in when Grok or Groq is unavailable) on a crypto research question.

NameTypeReqDescription
coinsarray–Coin symbols to focus on (e.g. ['BTC', 'ETH'])
questionstringyesResearch question to analyze

No output schema declared.

No examples provided.

search_signals ~100

Browse community trade signals and how they resolved (win/loss is checked against CoinGecko prices at expiry). Signals whose creator anchored them on Base carry an on-chain transaction hash; the rest do not. Signals appear here an hour after they are posted. Filter by coin and status.

NameTypeReqDescription
coinstring–Filter by coin (optional)
limitnumber–Max results (default 20)
statusstring–Signal status

No output schema declared.

No examples provided.

strategy_analysis ~122

Strategy Lab: backtest a trading strategy on historical OHLCV plus Monte Carlo and Walk-Forward robustness analysis. Strategies: dca, grid, momentum, custom. Premium — x402 $0.50.

NameTypeReqDescription
coinstringyesCoin symbol (BTC, ETH, SOL, ...)
fromstring–Start date/epoch (optional)
paramsobject–Strategy params: capital, fee %, periods, grid levels, etc.
strategystringyesStrategy id
tostring–End date/epoch (optional)

No output schema declared.

No examples provided.

Install

How do I install the Assistant Hub MCP server?

Assistant Hub is a hosted endpoint at https://rmassistanthub.io/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 · rmassistanthub.io

# add to Claude Code
claude mcp add --transport http io-rmassistanthub-assistant-hub 'https://rmassistanthub.io/mcp'
Common questions

What is the Assistant Hub MCP server?

Assistant Hub is an MCP server listed in the public MCP registry as io.rmassistanthub/assistant-hub. Ranked crypto setups with a graded track record, and trading skills with public records. This page covers its hosted endpoint (https://rmassistanthub.io/mcp).

Is the Assistant Hub MCP server safe to use?

Assistant Hub scores 85 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 Assistant Hub MCP server expose?

Assistant Hub exposes 12 tools: research_coin, get_forecast, get_whale_intel, strategy_analysis, pulse_deep_dive, and 7 more. Their descriptions and schemas cost roughly 1,027 tokens of context every time the server is loaded.

Does the Assistant Hub MCP server require authentication?

No. We connected to Assistant Hub without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Assistant Hub MCP server still maintained?

Assistant Hub is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.