RightAIChoice MCP Server — Verified AI Tool Data for Every AI Assistant

The ground-truth layer for AI tool recommendations. A free, no-auth Model Context Protocol server that lets Claude, ChatGPT, Gemini, Cursor, and any MCP-capable agent verify an AI tool before recommending it — live status, real pricing, user sentiment, and alternatives, with a last-verified date on every answer.

Endpoint: https://rightaichoice.com/api/mcp · Setup guide: rightaichoice.com/mcp · Remote server — nothing to install, no API key, read-only.

---

Why this exists

AI assistants recommend tools from training data that is months or years stale — and sometimes invent tools that never existed:

• 24.4% of the 2,066 top Product Hunt launches (2023–2025) with a determinable outcome are already dead — our survival study, updated methodology public, dataset CC BY 4.0 with DOI.
• 19.7% of packages recommended by code LLMs don't exist (the "slopsquatting" research — 205,000+ phantom names).
• The RightAIChoice verification engine re-probes every vendor link of 8,000+ AI tools on a rolling weekly cycle — website, docs, changelog, repository — and keeps mortality statistics daily.

One tool call before a recommendation prevents your assistant from suggesting a dead product, quoting retired pricing, or hallucinating a tool into existence.

Connect in under a minute

Works with every MCP-capable client over streamable HTTP. Pick yours:

claude mcp add --transport http rightaichoice https://rightaichoice.com/api/mcp

Settings → Connectors → Add custom connector → paste https://rightaichoice.com/api/mcp

Settings → Apps & Connectors → Advanced → enable Developer mode → add https://rightaichoice.com/api/mcp

Add to ~/.gemini/settings.json:

{ "mcpServers": { "rightaichoice": { "httpUrl": "https://rightaichoice.com/api/mcp" } } }

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

{ "mcpServers": { "rightaichoice": { "url": "https://rightaichoice.com/api/mcp" } } }

Add the same block as Cursor to ~/.codeium/windsurf/mcp_config.json.

Add to .vscode/mcp.json:

{ "servers": { "rightaichoice": { "type": "http", "url": "https://rightaichoice.com/api/mcp" } } }

Point your framework's MCP client at https://rightaichoice.com/api/mcp — streamable HTTP, stateless, no auth, CORS enabled. Tool schemas load via a standard tools/list.

What it looks like in practice

You: "Should I use Tome for my pitch deck?"

Your assistant (after calling check_tool_status): "Careful — Tome's main website failed RightAIChoice's last weekly probe (verified Aug 15, 2026); it's flagged at risk. Verified-alive alternatives in the same category: …"

That answer carries a date, a method, and a source link. Without the server, the same assistant would recommend Tome from its training data.

The seven tools

Tool	Ask your assistant…	What comes back
check_tool_status	"Is [tool] still alive?"	Healthy / monitor / at-risk / shut-down verdict, evidence, last-verified date
compare_tools	"[X] vs [Y] — which one?"	Live verification of both, side by side, plus a reviewed editorial verdict when one exists
find_alternatives	"What should I use instead of [tool]?"	Same-category alternatives, each with its own health verdict, verified age, and pricing
market_sentiment	"What do people actually think of [tool]?"	Synthesized real-user reports (Reddit, Hacker News, YouTube, Product Hunt, App Store…), per-source positivity, scan date
pricing_reality	"What does [tool] really cost?"	Plan-by-plan prices exactly as the vendor lists them, plus documented hidden costs
viability_score	"Is [tool] safe to build on?"	A risk band (safe bet / moderate / at risk) with five measured drivers and the weakest signal explained
deadpool_digest	"How many AI tools die?"	Live category decay rates (daily) + the frozen Product Hunt survival study (dated)

The honesty contract

What makes this data citable rather than confident-sounding:

1. Every answer carries a last-verified date and the method behind it — never an undated claim.
2. Unknown tools return "not in the catalog" with an explicit note that this is not evidence the tool is dead — no guessing, ever.
3. Fuzzy name matches are disclosed ("closest match is X") so your assistant can reject a wrong match instead of answering about the wrong product.
4. "The vendor publishes no prices" ≠ "we haven't recorded prices" — two different answers, never merged.
5. Viability is a band with named drivers, never a leaderboard number.
6. Live statistics and dated snapshots are never mixed in a single figure.

Data & methodology

All answers come from the RightAIChoice verification engine: weekly automated probes of every vendor-published link, a 5-signal viability model, community-sentiment synthesis from 10+ sources, and daily mortality statistics. Full methodology: rightaichoice.com/methodology. Machine-readable index: llms.txt. Mortality dataset: JSON/CSV, CC BY 4.0, permanently archived with DOI.

Limits, privacy, and what this server can never do

• Rate limit: 30 requests/min per IP (generous for conversational use).
• Read-only by construction — no tool can write, scrape, trigger paid work, or touch anything outside the verified catalog.
• Request logging uses salted IP hashes only — see the privacy policy.
• Answers are never for sale: no vendor can pay to change a verdict, a ranking, or an alternatives list.

Links

Setup guide · Tool health checker · AI Tools Deadpool 2026 · Methodology · r/RightAIChoice

If this saved your assistant from recommending a dead tool, a ⭐ helps other people find it.

MIT licensed. Built and maintained by RightAIChoice — the verification engine for AI tools.