Free · no API key · read-only

The MCP server for AI tools: verified status, pricing and sentiment for any AI assistant

Connect Claude, ChatGPT, Cursor or any MCP-capable agent to the RightAIChoice verification engine and it stops recommending dead AI tools. Ten read-only tools answer the questions that matter before adopting anything — is it alive, what does it really cost, what do users think, what should I use instead— and every answer is dated: when we last probed the vendor's links, and when we last rebuilt our record.

Endpoint

https://rightaichoice.com/api/mcp

Add to Claude Code

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

GitHub · Listed on the official MCP registry as com.rightaichoice/mcp

AI tools under verification
8,183
Dead homepages right now
155
PH launches dead (of known outcomes)
24.4%
Re-verification cycle
Weekly

Live figures as of 2026-09-15; survival study probed 2026-07-18.

Why AI assistants need a verification layer

  • LLMs recommend products that don't exist. Slopsquatting research measured 19.7% of packages recommended by code models as nonexistent — over 205,000 phantom names.
  • The AI tool market has real mortality. Our survival study of 2,291 top Product Hunt launches (2023–2025) found that of the 2,066 with a determinable outcome, 24.4% are already dead. Training data never catches up: a model's knowledge of "good AI tools" is months to years stale.
  • One wrong answer ends trust. An assistant that recommends a shut-down product, quotes retired pricing, or invents a tool loses the user. One MCP call before the recommendation prevents all three.

The ten tools

check_tool_status

"Is this AI tool still alive?"

Healthy / monitor / at-risk verdict from weekly probes of every vendor link, with the last-verified date and evidence.

compare_tools

"X vs Y — which should I pick?"

Live side-by-side verification of both tools plus our reviewed editorial verdict when one exists for the pair.

find_alternatives

"What should I use instead?"

Same-category alternatives, each carrying its own health verdict, verified age and pricing — never unverified filler.

market_sentiment

"What do users actually think?"

Synthesized real-user reports from Reddit, HN, YouTube, Product Hunt and more — per-source positivity, top pros and cons, scan date.

pricing_reality

"What does it really cost?"

Plan-by-plan prices exactly as the vendor lists them, plus documented hidden costs: annual markups, seat minimums, paywalled features.

viability_score

"Is it safe to build on?"

A viability band (safe bet / moderate / at risk) with five measured drivers and the weakest signal explained in plain language.

deadpool_digest

"How many AI tools die?"

Live catalog decay rates by category plus our frozen survival study of 2,291 Product Hunt launches. Every figure dated.

recommend_tools

"Find me a tool that does X — that won't disappear"

A verified shortlist matched on what you need it to DO, screened against a survival bar so nothing on the list is already failing our checks. Tools with no measurement yet are named, never silently dropped.

category_landscape

"What does this whole category look like?"

How crowded a category is, how its tools distribute across survival bands, its vendor-link decay rate, and named examples at both the strongest and weakest ends.

whats_changed

"What changed in the AI tool market?"

Dated, field-level changes we actually observed — vendor pricing-page edits, price changes, link health, domains and certificates. Our own editorial rewrites are excluded on purpose.

Connect in under a minute

  1. 1. Claude Code (one command)

    claude mcp add --transport http rightaichoice https://rightaichoice.com/api/mcp
  2. 2. Claude Desktop / claude.ai

    Settings → Connectors → Add custom connector → paste https://rightaichoice.com/api/mcp
  3. 3. Cursor / Windsurf (mcp.json)

    { "mcpServers": { "rightaichoice": { "url": "https://rightaichoice.com/api/mcp" } } }
  4. 4. ChatGPT (developer mode)

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

Works with any MCP client over streamable HTTP — including the OpenAI Agents SDK, Vercel AI SDK and LangChain MCP adapters. No local install; it's a remote server.

The honesty contract

  • Every answer carries two dates, kept apart — when we last probed the vendor's links, and when we last rebuilt our record — plus the method behind each. Never an undated claim, and never one date standing in for the other.
  • Unknown tools are reported as not in the catalog, which is not evidence they are dead.
  • Fuzzy name matches are disclosed — the server names what it matched so your assistant can reject a wrong match.
  • "Vendor publishes no prices" and "we haven't recorded prices" are two different answers, never merged.
  • Viability comes as a band with named drivers, not a leaderboard number.
  • Live decay statistics and the dated survival study are never mixed in one figure.

The server reads from the same engine as the public tool checker and the AI Tools Deadpool report, so an MCP answer can never contradict the website. Method details: methodology.

Frequently asked questions

What is the RightAIChoice MCP server?

A free Model Context Protocol (MCP) server at https://rightaichoice.com/api/mcp that gives any AI assistant — Claude, ChatGPT, Cursor and every MCP-capable agent — verified answers about 8,000+ AI tools: live status, pricing reality, user sentiment, viability and alternatives. Every vendor link is re-probed on a rolling weekly cycle (measured 2026-09-14: 100% of published tools probed within 7 days, median 2), and every answer states both that probe date and the separate, slower date our catalog record was last rebuilt.

Is it free, and do I need an API key?

Yes, free — and no API key or sign-up. The server is read-only and rate-limited per IP (30 requests/minute). All ten tools are annotated read-only, so assistants like Claude can call them without confirmation prompts.

Why should my AI assistant verify tools before recommending them?

Because models hallucinate products: research on "slopsquatting" found 19.7% of packages recommended by code LLMs do not exist, and our own survival study found 24.4% of 2,066 top Product Hunt launches from 2023-2025 are already dead. A one-call check prevents recommending a dead or imaginary tool.

How fresh is the data?

Two clocks, and we keep them apart. Every published vendor link (website, docs, changelog, repository) is re-probed on a rolling weekly cycle — that probe is what the alive/at-risk verdict is built on, and as of 14 Sep 2026 it had covered 100% of published tools within 7 days (median 2). Separately, the full catalog record — pricing, features, verdict prose — is rebuilt on a slower cycle, median 16 days. Mortality statistics recompute daily. Every MCP answer states both dates rather than merging them into one "last verified", so the assistant — and you — can judge each claim against the check that actually backs it.

What happens when a tool is not in the catalog?

The server says so honestly: "not in the catalog" with an explicit note that this is NOT evidence the tool is dead. When it resolves a fuzzy name it names the match it made, so the assistant can reject a wrong match instead of confidently answering about the wrong product.

Can it run live scans or modify anything?

No. All ten tools are read-only and serve pre-verified data from the RightAIChoice verification engine — the same engine behind rightaichoice.com. Nothing an assistant does through this server can trigger a scrape, an LLM call, or any change to the catalog. We do log the call itself — which tool, the query, the answer served, latency, and a salted hash of the client IP (never the raw IP) — for rate limiting and to see which tools people actually ask about.

Which AI assistants and clients support it?

Any MCP-capable client over streamable HTTP: Claude Code, Claude Desktop and claude.ai custom connectors, Cursor, Windsurf, ChatGPT (developer mode connectors), and agent SDKs like the OpenAI Agents SDK and Vercel AI SDK. No local install is needed — it is a remote server.