# RightAIChoice — verified AI tool data (remote · rightaichoice.com)

Verified data on 8,000+ AI tools: live status, pricing, sentiment, alternatives. Free, read-only.

- Trust score: 84/100 (high trust)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `rightaichoice.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-rightaichoice-mcp/api-mcp.md), [page](https://verifymcp.io/servers/com-rightaichoice-mcp/api-mcp)

## Channel facts

- Endpoint: `https://rightaichoice.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2818 tokens (~281/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the RightAIChoice — verified AI tool data MCP server?

RightAIChoice — verified AI tool data is a hosted endpoint at https://rightaichoice.com/api/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.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.com-rightaichoice-mcp]
url = "https://rightaichoice.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rightaichoice-mcp": {
      "type": "remote",
      "url": "https://rightaichoice.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rightaichoice-mcp --url 'https://rightaichoice.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rightaichoice-mcp:
    url: "https://rightaichoice.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rightaichoice-mcp": {
      "Transport": "http",
      "Url": "https://rightaichoice.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rightaichoice-mcp -t streamable-http -u 'https://rightaichoice.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-rightaichoice-mcp": {
      "type": "http",
      "url": "https://rightaichoice.com/api/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-18 (score 84, +1)

- [security] Stability: 0.97 → pass

### 2026-09-16 (score 83, +1)

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

### 2026-09-14 (score 82, +1)

- [security] Tool “category_landscape” rewrote its description, which is the text the model reads
- [security] Tool “check_tool_status” rewrote its description, which is the text the model reads
- [security] Tool “compare_tools” rewrote its description, which is the text the model reads
- [security] Tool “find_alternatives” rewrote its description, which is the text the model reads
- [security] Tool “recommend_tools” rewrote its description, which is the text the model reads

### 2026-09-12 (score 81, +1)

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

### 2026-09-10 (score 80, +1)

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

### 2026-09-08 (score 79, +1)

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

### 2026-09-06 (score 78, 0)

- [security] Tool “market_sentiment” rewrote its description, which is the text the model reads

### 2026-09-05 (score 78, +1)

- [cosmetic] “recommend_tools” reworded the description of “survival_bar”

## MCP tools (10)

### `check_tool_status` (~313 tokens)

Check if an AI tool is alive

Use this when the user asks whether a specific AI tool is alive, dead, shut down, still maintained, safe to adopt, or trustworthy — or asks for its current health, viability, or verification status. Returns a verified verdict (healthy / monitor / at-risk / shut down / delisted) with evidence: link-health probe results, a 5-signal viability assessment, real-user market sentiment, pricing reality, and verified-alive alternatives. Data comes from the RightAIChoice verification engine: 8,000+ AI tools with every vendor link re-probed on a rolling weekly cycle. Every answer states BOTH dates it stands on and does not merge them: when we last probed the vendor links (what the verdict is built on) and when our catalog record was last rebuilt. Not for: tools outside the AI/software space, historical company research, or legal/financial advice. "Not in the catalog" and a verdict of UNKNOWN are DIFFERENT answers: the first means we hold no entry, the second means we hold one whose signals are not measured yet. Neither is evidence the tool is dead.

Input parameters:

- `response_format` (string): concise = verdict + freshness + source link. detailed = adds viability signals, link health, sentiment, pricing, and alternatives.
- `tool` (required): The AI tool to check — product name (e.g. "Jasper") or site slug (e.g. "jasper"). Pass an ARRAY of up to 20 names to assess a whole stack at once.

### `compare_tools` (~251 tokens)

Compare two AI tools head-to-head

Use this when the user asks how two specific AI tools compare, which of two tools to choose, or "X vs Y". Returns live verification status for BOTH tools side by side (alive/at-risk/shut-down verdict, the vendor-link probe date AND the separate catalog-rebuild date, pricing reality, market sentiment) plus an editorial head-to-head verdict when a reviewed comparison exists for the pair. Data comes from the RightAIChoice verification engine: 8,000+ AI tools with every vendor link re-probed on a rolling weekly cycle, and 19,000+ maintained comparison analyses. Not for: single-tool checks (use check_tool_status), comparing more than two tools, or category browsing. If either tool is reported as not in the catalog, that is not evidence it is dead.

Input parameters:

- `response_format` (string): concise = per-tool verdict + pricing + editorial verdict. detailed = adds sentiment, viability signals, and link health per tool.
- `tool_a` (string, required): First AI tool — product name (e.g. "Jasper") or site slug (e.g. "jasper").
- `tool_b` (string, required): Second AI tool — product name or site slug.

### `find_alternatives` (~229 tokens)

Find verified-alive alternatives to an AI tool

Use this when the user asks what to use instead of a specific AI tool, for its alternatives or competitors, or for a replacement because the tool shut down, got acquired, raised prices, or is unreliable. Returns up to 3 verified-alive alternatives from the same category, each with a one-line description, current health verdict, the date our record of it was last rebuilt, and pricing model. If the asked-about tool shut down, says so (with the recorded reason) and returns live replacements. Alternatives come from the RightAIChoice verification engine (8,000+ AI tools, every vendor link re-probed on a rolling weekly cycle), ranked by category and identity-tag match — never filler from unrelated categories. The response states whether results are curated matches or a category roll-up. Not for: comparing two named tools (use compare_tools) or checking a single tool's status (use check_tool_status).

Input parameters:

- `tool` (string, required): The AI tool to find alternatives for — product name (e.g. "Jasper") or site slug (e.g. "jasper").

### `market_sentiment` (~328 tokens)

Real-user market sentiment for an AI tool

Use this when the user asks what people actually think of a specific AI tool, whether users like it, its reputation, reviews, community feedback, common complaints, or praised strengths. Returns a synthesized sentiment report from real user discussions (Reddit, Hacker News, GitHub, YouTube, Product Hunt and more): overall sentiment label, per-source positivity, top pros and cons, recurring themes, and mention volume — always stamped with the scan date. Reports come from the RightAIChoice sentiment engine and are served from the verified cache (usability gate: completed scans under 180 days old). If no usable scan is on file, this tool says so honestly instead of guessing. SUBJECT GATE: where we hold a scan but cannot establish that the posts are about this product rather than something else sharing its name, NO score, count or breakdown is returned and the reply says so explicitly. That reply means "we checked and disproved the subject" — it is not an absence of data and not a negative signal about the product. Not for: checking whether a tool is alive (use check_tool_status) or head-to-head choices (use compare_tools). Sentiment reflects public discussion volume, not product quality rankings.

Input parameters:

- `response_format` (string): concise = label, verdict line, top pro/con, mention count. detailed = adds per-source breakdown, up to 4 pros/cons, and recurring themes.
- `tool` (string, required): The AI tool to get sentiment for — product name (e.g. "Jasper") or site slug (e.g. "jasper").

### `deadpool_digest` (~261 tokens)

AI tool mortality statistics

Use this when the user asks how many AI tools die, AI startup failure or shutdown rates, which AI categories decay fastest, how risky the AI tool market is, or for data behind "most AI tools fail" claims. Returns two clearly separated datasets: (1) LIVE catalog decay — 8,000+ verified AI tools with broken vendor-link rates, dead-homepage counts, pricing opacity, and the fastest/slowest-decaying categories, updated daily; (2) a FROZEN dated survival study of 2,291 top Product Hunt launches (of the 2,066 with a determinable outcome, 24.4% are dead within ~2 years). Every figure carries its as-of date. Data comes from the RightAIChoice verification engine; link-decay figures count only VENDOR-published links (site/docs/changelog/repo), never our own derived URLs. Not for: checking one specific tool (use check_tool_status) or predicting a specific tool's future (use viability_score). Decay rates describe categories and cohorts, not individual products.

Input parameters:

- `response_format` (string): concise = headline mortality figures from both datasets. detailed = adds fastest/slowest-decaying categories and survival splits by launch votes and rank.

### `viability_score` (~228 tokens)

How likely an AI tool is to survive

Use this when the user asks whether a specific AI tool is safe to adopt or build on, likely to still exist next year, well-maintained, gaining or losing momentum — or asks about its long-term viability or abandonment risk. Returns a viability BAND (safe bet / moderate / at risk) with the five measured drivers behind it: what the vendor publishes, site health, traction, user sentiment, and recent activity — plus which signal is weakest and why, in plain language. Assessments come from the RightAIChoice verification engine (8,000+ AI tools, every vendor link re-probed on a rolling weekly cycle). A null driver means "not yet measured", which is different from a bad score. Bands are NOT a leaderboard: they classify risk, they do not rank tools against each other. Not for: comparing two tools (use compare_tools), liveness checks alone (use check_tool_status), or investment decisions.

Input parameters:

- `tool` (string, required): The AI tool to assess — product name (e.g. "Jasper") or site slug (e.g. "jasper").

### `pricing_reality` (~259 tokens)

What an AI tool really costs

Use this when the user asks what a specific AI tool costs, its pricing model, plans and tiers, whether it has a free tier, hidden costs, or whether the vendor even publishes prices. Returns the recorded pricing model, per-plan prices exactly as the vendor lists them, and — unique to this catalog — documented HIDDEN COSTS: annual-commitment markups, seat minimums, paywalled features, and undisclosed usage fees. Data comes from the RightAIChoice verification engine (8,000+ AI tools re-verified on a rolling weekly cycle). The response distinguishes "the vendor publishes no prices" (their choice — sales call required) from "not recorded in our catalog" (our gap), and never converts currencies. Not for: negotiating quotes, historical price tracking, or financial advice. Prices change frequently — treat the verification date as part of the answer.

Input parameters:

- `response_format` (string): concise = pricing model + plan prices + top 2 hidden costs. detailed = full plan list with key features and up to 6 hidden costs.
- `tool` (string, required): The AI tool to get pricing for — product name (e.g. "Jasper") or site slug (e.g. "jasper").

### `whats_changed` (~290 tokens)

What changed in the AI tool market

Use this when the user asks what has changed recently in AI tools — whether a specific tool has changed its pricing, links, domain or health, or what has moved across the market since a given date. Returns dated, field-level changes we actually observed: vendor pricing-page edits, recorded price changes, link health moving, domain and certificate changes, and vendors moving their site. Each carries the date we observed it and how. Reports only VENDOR-OBSERVABLE changes by default — our own editorial rewrites are excluded and the response says so, because our writing changing is not the market moving. Our change record begins on a fixed date stated in every answer; asking about an earlier period returns that date rather than an empty result. Not for: predicting future changes, or a tool's current status (use check_tool_status).

Input parameters:

- `include` (string): vendor_changes = only what the vendor did. vendor_and_our_assessment = also our survival re-scores. Our editorial rewrites are never included.
- `response_format` (string): concise = counts plus the most notable changes. detailed = the individual dated changes.
- `since` (string): Optional ISO date (YYYY-MM-DD). Defaults to 7 days ago. Earlier than our coverage floor returns the floor.
- `tool` (string): Optional. A single AI tool — product name or slug. Omit for a market-wide summary.

### `recommend_tools` (~401 tokens)

Find an AI tool for a job — that will still exist next year

Use this when the user describes what they need an AI tool to DO rather than naming one — "something to transcribe interviews", "an image generator with an API", "a writing tool for a small team". Returns a verified shortlist matched on the described need, filtered by constraints the caller sets, and — unique to this catalog — screened against a survival bar: tools failing our link-health probes or scoring badly on the 5-signal viability model can be excluded outright. Each result carries its own health verdict, the date our record of it was last rebuilt, and pricing model. Matching is keyword and fuzzy text search over 8,000+ verified tools; the response states this. Tools with no viability measurement yet are listed separately by name rather than silently dropped. Not for: questions about a tool the user already named (use check_tool_status), head-to-head choices (use compare_tools), or filtering by price amount — prices are recorded verbatim in mixed currencies and are never converted or compared numerically.

Input parameters:

- `exclude_wrappers` (boolean): Exclude tools assessed as thin wrappers around a third-party model.
- `limit` (integer): How many results to return (max 10).
- `need` (string, required): What the tool must do, in the user's own words. e.g. "transcribe podcast interviews with speaker labels".
- `pricing_model` (string): Filter by recorded pricing model. has_free_option = free or freemium. There is no price-amount filter: prices are verbatim strings in mixed currencies.
- `requires_api` (boolean): Only return tools recorded as offering an API.
- `survival_bar` (string): exclude_at_risk = drop tools scoring below the at-risk threshold, with a failing main site, or whose published website now redirects to a different company. safe_bet_only = only the strongest band. n…

### `category_landscape` (~258 tokens)

The risk landscape of an AI tool category

Use this when the user asks what a whole category of AI tools looks like — how crowded it is, how healthy or risky it is overall, which tools in it are strongest, or which are in trouble. Examples: "how risky is the AI video generation market", "what does the code assistant category look like". Returns the number of tools we track in that category, how they distribute across survival bands, the category's vendor-link decay rate, and named examples at both the strongest and weakest ends — each with its own survival score and the date our record of it was last rebuilt. Categories are our own classification and tools belong to several at once, so category sizes overlap and never sum to the catalog total. Bands classify risk, not quality — the model has no notion of company size. Not for: choosing between named tools (use compare_tools), finding a tool for a job (use recommend_tools), or market-wide mortality statistics (use deadpool_digest).

Input parameters:

- `category` (string, required): The category, in plain words or as a slug — e.g. "image generation", "code-development".
- `response_format` (string): concise = size, distribution and the strongest few. detailed = adds the weakest end and the decay rate.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rightaichoice-mcp/api-mcp#diagnostics

## Score history

- 2026-09-21: 84
- 2026-09-20: 84
- 2026-09-19: 84
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 80
- 2026-09-10: 80
- 2026-09-09: 79
- 2026-09-08: 79
- 2026-09-07: 78
- 2026-09-06: 78
- 2026-09-05: 78
- 2026-09-04: 77
- 2026-09-03: 77
- 2026-09-02: 76
- 2026-09-01: 76
- 2026-08-31: 76
- 2026-08-30: 75
- 2026-08-29: 75
- 2026-08-28: 74
- 2026-08-27: 74
- 2026-08-26: 73
- 2026-08-25: 72
- 2026-08-24: 71
- 2026-08-23: 71

## Common questions

### What is the RightAIChoice — verified AI tool data MCP server?

RightAIChoice — verified AI tool data is an MCP server listed in the public MCP registry as com.rightaichoice/mcp. Verified data on 8,000+ AI tools: live status, pricing, sentiment, alternatives. Free, read-only. This page covers its hosted endpoint (https://rightaichoice.com/api/mcp).

### Is the RightAIChoice — verified AI tool data MCP server safe to use?

RightAIChoice — verified AI tool data scores 84 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 RightAIChoice — verified AI tool data MCP server expose?

RightAIChoice — verified AI tool data exposes 10 tools: check_tool_status, compare_tools, find_alternatives, market_sentiment, deadpool_digest, and 5 more. Their descriptions and schemas cost roughly 2,818 tokens of context every time the server is loaded.

### Does the RightAIChoice — verified AI tool data MCP server require authentication?

No. We connected to RightAIChoice — verified AI tool data without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the RightAIChoice — verified AI tool data MCP server still maintained?

RightAIChoice — verified AI tool data is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://rightaichoice.com/api/mcp
- Repository: https://github.com/right-ai-choice/mcp-server
- Website: https://rightaichoice.com/mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-rightaichoice-mcp/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rightaichoice-mcp/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-rightaichoice-mcp/api-mcp