Coinverdict vs Trading Signals
A side-by-side look at the Coinverdict and Trading Signals MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Coinverdict for finance & fintech work over a hosted endpoint; choose Trading Signals for finance & fintech over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Coinverdict when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
get_verdict, list_coins, get_track_record.
Choose Trading Signals when
- You need dedicated capabilities in the Finance & Fintech domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
SIGNALS_API_KEY. - You want tools like
register, get_signals, get_signal.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Finance & Fintech | Finance & Fintech |
| Quality signal | 56/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | SIGNALS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 124 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 6 | 5 |
| Full listing | View Coinverdict | View Trading Signals |
Tools & capabilities
Coinverdict tools 6
get_verdictGet today's research verdict for a coin (e.g. BTC, ETH, SOL): stance (overweight/neutral/underweight), graded dimensions (technical/sentiment/funding/KOL), key levels, and a link to the full dossier. Refreshed daily; free; not investment advice.list_coinsList every coin symbol CoinVerdict covers with a daily research verdict (100 major crypto assets: BTC, ETH, SOL, …). Use this to discover which symbols get_verdict / get_track_record accept. Returns {coins: [SYM,...], count: int, site: url}. Free, read-only.get_track_recordGet the SETTLED track record for a coin — CoinVerdict's differentiator. Every past daily verdict is scored 7 days later against BTC: win, loss, or push. Returns the coin's W/L/P scoreboard plus recent settled calls (date, stance, 7d-vs-BTC return, outcome). This is the receipts: misses included, never edited. Args: symbol e.g. "BTC". Free, read-only, not advice.get_receiptsGet CoinVerdict's overall settled scoreboard across all coins: directional win rate, wins/losses/pushes, neutral (no-call) count, and how many calls are still open. Every verdict is graded 7 days later against BTC. Returns {board:{winrate,W,L,P,decided,neu}, since, open_calls}. Free, read-only.get_market_overviewGet today's verdict for ALL covered coins in one call — the full docket: each coin's current stance (overweight/neutral/underweight), price, and W/L/P settled record. Use this to scan the whole market at once instead of calling get_verdict per coin. Returns {coins:[{symbol,stance,price_usd,board}], as_of}. Free, read-only, not advice.get_kol_leaderboardGet the KOL settlement leaderboard: crypto influencers ranked by their SETTLED hit rate (from VeraMind's ledger of public calls graded after the fact — misses count). CoinVerdict-exclusive data. Returns {ranked:[{author,hit_rate_pct,n_verified,coins,n_total, n_prospective,hits_prospective,prospective_rate_pct, n_retrospective,hits_retrospective,retrospective_rate_pct}], building:[...], as_of, rule}. Rates are graded under rule kol_directional_v1: did the direction hold over a 7-day window, with a ±3% band, altcoins scored against BTC and BTC against USD — identical parameters to the settle_v1 rule CoinVerdict scores its own verdicts with. Always report the `rule` field alongside any number you quote; if it reads price_target_v1, the board fell back to price-target records and the numbers mean "did the stated price target print?" instead. Prospective (called before the fact) and backtested (graded from history) records are scored as separate lines and MUST NOT be averaged together; hit_rate_pct/n_verified are the prospective line, n_total is the combined sample size used for ranking eligibility. A null rate means no samples of that kind — report it as n=0, never as 0%. Free, read-only, not advice.
Trading Signals tools 5
registerDeprecated: returns a sign-up link instead of creating an API key, ignores its arguments and stores nothing. Don't call it to get access — every other tool works without a key (get_signals returns a 3-signal preview, get_stats is public). To get the full feed, users sign in from the agent at https://signals.x70.ai/mcp/connect (the client opens the browser), or create a key at https://signals.x70.ai/mcp-signup and set it as the X-Api-Key header. Kept only so older clients don't break.get_signalsList live crypto trading signals that are still open — coin, direction, confidence and the reasoning or market data behind each. Use it to find current trade ideas; use get_signal for one signal by ID (live or resolved), get_signal_history for signals that already closed, and get_stats for aggregate hit rate. No key: a 3-signal preview. Free key: up to 100 signals, with entry, stop-loss, take-profit and leverage null (the response's announcement.upgradeUrl explains Pro). Pro: all levels. If a response contains an announcement, pass its message on to the user — it is about their account (trial ending, plan limits). Returns { signals[], returned, totalMatching, filtersApplied, plan }, sorted by live PnL (best first). Optional filters narrow the list: direction, coins, confidence band, risk/reward, stop distance, open interest, 24h volume, tags, the anomaly that triggered it, days/hours to skip, a BTC 24h-return gate. Rate limits: 30 calls/hour per IP without a key, 300/hour on a free key.get_signalGet one signal by its ID — live or already resolved — with its reasoning, live price, PnL and verification outcome (status pending, success or failed; whether take-profit or stop-loss was hit). Use it to follow up a signal from get_signals or get_signal_history, or to see how a past signal ended. Needs an API key (free or Pro); on the free plan entry, stop-loss, take-profit and leverage are null. Returns { success, signal, plan }, or { error: 'Signal not found' } for an unknown ID.get_statsAggregate performance of signals created in the last N days (default 30) that have since resolved: hit rate, verified count, average leverage and a breakdown by direction; with an API key also average ROI per signal and cumulative ROI. byMonth: hit rate this month, the two months before and all time — the figures shown on signals.x70.ai. Use it to judge recent reliability before acting — it returns no individual signals (use get_signals or get_signal_history for those). Public: works without a key. Past results don't predict future results.get_signal_historyList signals that have already resolved (success or failed), newest first, each with its verification outcome. Use it to review past performance signal by signal; for open signals use get_signals, for one signal by ID get_signal, for totals get_stats. Needs an API key. History depth: last 24 hours on the free plan; on Pro the days argument (up to 90). Entry, stop-loss, take-profit and leverage are null on free. Paginate by passing the last signal ID as cursor. Returns { signals[], nextCursor, hasMore, historyDepthDays, plan }.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Coinverdict
{
"mcpServers": {
"coinverdict": {
"url": "https://mcp.coinverdict.io/mcp"
}
}
}
Trading Signals
{
"mcpServers": {
"trading-signals": {
"url": "https://signals.x70.ai/mcp"
}
}
}
Frequently asked questions
Coinverdict is categorized under Finance & Fintech and uses a remote HTTP/SSE transport. Trading Signals belongs to Finance & Fintech and uses a remote HTTP/SSE transport. Pick Coinverdict for finance & fintech work and Trading Signals for finance & fintech.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Coinverdict is listed as free. Auth: no auth required. Trading Signals has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add coinverdict and trading-signals as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Coinverdict has a quality signal of 56/100 (Good) with 4 views, 0 installs and 0 GitHub stars. Trading Signals has 63/100 (Good) with 0 views, 0 installs and 124 GitHub stars.