RightAIChoice — verified AI tool data
REMOTE · RIGHTAICHOICE.COM · SCANNED SEP 21
Verified data on 8,000+ AI tools: live status, pricing, sentiment, alternatives. Free, read-only.
Available components
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · rightaichoice.com
claude mcp add --transport http com-rightaichoice-mcp 'https://rightaichoice.com/api/mcp'
{
"mcpServers": {
"com-rightaichoice-mcp": {
"url": "https://rightaichoice.com/api/mcp"
}
}
} {
"servers": {
"com-rightaichoice-mcp": {
"type": "http",
"url": "https://rightaichoice.com/api/mcp"
}
}
} [mcp_servers.com-rightaichoice-mcp] url = "https://rightaichoice.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-rightaichoice-mcp": {
"type": "remote",
"url": "https://rightaichoice.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add com-rightaichoice-mcp --url 'https://rightaichoice.com/api/mcp' --transport streamable-http
mcp_servers:
com-rightaichoice-mcp:
url: "https://rightaichoice.com/api/mcp" {
"McpServers": {
"com-rightaichoice-mcp": {
"Transport": "http",
"Url": "https://rightaichoice.com/api/mcp"
}
}
} assistant mcp add com-rightaichoice-mcp -t streamable-http -u 'https://rightaichoice.com/api/mcp'
{
"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.
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.
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +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.
- 14 Sept 26 +1
- 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 security
- 12 Sept 26 +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.
- 10 Sept 26 +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.
- 8 Sept 26 +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.
- 6 Sept 26 0
- Tool “market_sentiment” rewrote its description, which is the text the model reads security
- 5 Sept 26 +1
- “recommend_tools” reworded the description of “survival_bar” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
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 21 Sept 2026 · Probed https://rightaichoice.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rightaichoice.com | CN=WE1,O=Google Trust Services,C=US | 27 Jul 2026 | 25 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | 4bdc51ea9de0199c13ebcd91b7234e46 |
| SANs: rightaichoice.com, *.rightaichoice.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rightaichoice.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rightaichoice.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
|---|---|
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://accounts.google.com https://checkout.razorpay.com https://*.razorpay.com https://www.paypal.com https://www.paypalobjects.com https://www.clarity.ms https://*.clarity.ms; style-src 'self' 'unsafe-inline' https://accounts.google.com/gsi/style; img-src 'self' data: blob: https://*.supabase.co https://*.googleusercontent.com https://www.google.com https://*.gstatic.com https://cdn.rightaichoice.com https://cdn.futurepedia.io https://img.youtube.com https://i.ytimg.com https://*.razorpay.com https://*.paypal.com https://*.paypalobjects.com https://*.clarity.ms; font-src 'self'; connect-src 'self' https://accounts.google.com https://*.supabase.co https://api.anthropic.com https://api.mixpanel.com https://api-js.mixpanel.com https://api-eu.mixpanel.com https://*.sentry.io https://*.ingest.sentry.io https://*.razorpay.com https://*.paypal.com https://*.clarity.ms; frame-src 'self' https://accounts.google.com https://*.razorpay.com https://*. |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rightaichoice.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://rightaichoice.com/api/mcp | HTTPS enforced | 301 | https://rightaichoice.com/api/mcp |
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 →
category_landscape The risk landscape of an AI tool category ~258
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).
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | 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. |
No output schema declared.
No examples provided.
check_tool_status Check if an AI tool is alive ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | concise = verdict + freshness + source link. detailed = adds viability signals, link health, sentiment, pricing, and alternatives. |
| tool | – | yes | 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. |
No output schema declared.
No examples provided.
compare_tools Compare two AI tools head-to-head ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | concise = per-tool verdict + pricing + editorial verdict. detailed = adds sentiment, viability signals, and link health per tool. |
| tool_a | string | yes | First AI tool — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
| tool_b | string | yes | Second AI tool — product name or site slug. |
No output schema declared.
No examples provided.
deadpool_digest AI tool mortality statistics ~261
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.
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | concise = headline mortality figures from both datasets. detailed = adds fastest/slowest-decaying categories and survival splits by launch votes and rank. |
No output schema declared.
No examples provided.
find_alternatives Find verified-alive alternatives to an AI tool ~229
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).
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | The AI tool to find alternatives for — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
No output schema declared.
No examples provided.
market_sentiment Real-user market sentiment for an AI tool ~328
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The AI tool to get sentiment for — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
No output schema declared.
No examples provided.
pricing_reality What an AI tool really costs ~259
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | The AI tool to get pricing for — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
No output schema declared.
No examples provided.
recommend_tools Find an AI tool for a job — that will still exist next year ~401
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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… |
No output schema declared.
No examples provided.
viability_score How likely an AI tool is to survive ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| tool | string | yes | The AI tool to assess — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
No output schema declared.
No examples provided.
whats_changed What changed in the AI tool market ~290
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
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.