Skip to content

RightAIChoice — verified AI tool data MCP server

com.rightaichoice/mcprightaichoice.comstreamable-httpv1.2.0Scanned

What changed, what died, what it costs, what survives: 8,000+ AI tools, verified and dated.

13 tools: 10 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 10 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

10 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RightAIChoice — verified AI tool data MCP server can do

The RightAIChoice — verified AI tool data MCP server is published by rightaichoice.com, a domain the MCP Registry verified. It has 13 tools. It can create or change data (10 tools: market_sentiment, deadpool_digest, viability_score, pricing_reality and 6 more), but cannot delete data. 3 tools only read.

1 tool brings in text other people can write (check_mcp_server).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 15, 2026, version 1.2.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

13 tools

Changes things 10Claude Code: ask
  • best_forUse this when the user asks for the best AI tools for a task, niche or category — "best AI meeting notes tools", "top AI video editors", "what should I use for logo design".No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use this when the user asks for the best AI tools for a task, niche or category — "best AI meeting notes tools", "top AI video editors", "what should I use for logo design". Returns our ranked list for the topic: the same ranking our "Best AI tools for X" pages use — topic match, real-user mentions, how often AI engines read each tool, and viability, with a founder-reviewed consensus list as a sanity gate. A #1 is named ONLY when the leader clears that gate; otherwise the answer says no single top pick is warranted. Every tool carries its pricing model, viability score and page. Not for: a single named tool (use check_tool_status), two named tools (compare_tools), or a described need with hard filters (recommend_tools).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • category_landscapeUse 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 t…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • check_mcp_serverUse this when the user asks about a specific Model Context Protocol server — whether it is listed in the official MCP registry, what endpoint it publishes, how current its listing …Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Use this when the user asks about a specific Model Context Protocol server — whether it is listed in the official MCP registry, what endpoint it publishes, how current its listing is, or whether that endpoint responds. Returns the registry record (name, version, publish and update dates, declared remote endpoints, registry status) plus the result of one anonymous request to a registry-published endpoint. Reports observations only. It does NOT assess whether a server is safe, trustworthy, well-built or suitable — we cannot see what a server does with data, and reachability is not safety. Many listed servers require authentication and cannot be queried anonymously; that is normal and is not a fault. Absence from the registry is not evidence a server does not exist. Not for: security assessment, recommending which MCP server to install, or checking AI tools in the RightAIChoice catalog (use check_tool_status).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • deadpool_digestUse 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 "mos…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • market_sentimentUse 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 stre…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • pricing_realityUse 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…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • recommend_toolsUse 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 fo…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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 combines meaning-based search (text embeddings of each listing) with keyword search over 8,000+ verified tools; the response states which methods ran. 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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • stack_overlapUse this when the user asks whether the AI tools they pay for duplicate each other — "are we paying twice", "does our stack overlap", "can we consolidate these".No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Use this when the user asks whether the AI tools they pay for duplicate each other — "are we paying twice", "does our stack overlap", "can we consolidate these". Give it the tools they actually pay for. Returns the pairs we classify the same way, with the shared categories and shared capability tags named for each pair so the user can judge the claim themselves. IMPORTANT: this compares how RightAIChoice classifies two products — not their features, their APIs, or what a team does with them. It is a prompt to review a pair, never evidence that either is redundant. It never recommends cancelling anything and never totals cost, because plan and seat count are unknown. Not for: feature-by-feature comparison of two named tools (use compare_tools), finding a replacement (use find_alternatives), or calculating spend.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • viability_scoreUse 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 it…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • whats_changedUse 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 si…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 3Show 3 read-only tools
  • check_tool_statusUse 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 ve…No findings

    Why it is in this group

    • The name "check_tool_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • compare_toolsUse this when the user asks how two specific AI tools compare, which of two tools to choose, or "X vs Y".No findings

    Why it is in this group

    • The name "compare_tools" says "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • find_alternativesUse 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 pr…No findings

    Why it is in this group

    • The name "find_alternatives" says "find": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:45 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (10 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://rightaichoice.com/api/mcp: tools/list returned 13 tools to an anonymous client, including market_sentiment (write), deadpool_digest (write), viability_score (write), pricing_reality (write), whats_changed (write) and 5 more

    What this check looks for

Posture changes

  1. Oct 29, 2026
    • Tools that change things, listed without credentials: 9 to 10

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 10.View diff
    • Tools that change things, listed without credentials: 9 to 10
  2. Tools1 added, 1 changed.+1 added~1 changedView diff

Install

Pinned to version 1.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rightaichoice__check_tool_status",
      "mcp__rightaichoice__compare_tools",
      "mcp__rightaichoice__find_alternatives"
    ],
    "ask": [
      "mcp__rightaichoice__market_sentiment",
      "mcp__rightaichoice__deadpool_digest",
      "mcp__rightaichoice__viability_score",
      "mcp__rightaichoice__pricing_reality",
      "mcp__rightaichoice__whats_changed",
      "mcp__rightaichoice__recommend_tools",
      "mcp__rightaichoice__best_for",
      "mcp__rightaichoice__category_landscape",
      "mcp__rightaichoice__stack_overlap",
      "mcp__rightaichoice__check_mcp_server"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rightaichoice. Review it before you use it.

Capability tags behind 1 rule
  • mcp__rightaichoice__check_mcp_server untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.rightaichoice/mcp/verify?hash=95789d6405e9543272982a61f79be34a198f04a99e9b3c711fc1cf74953490b3" | jq -e '.changed == false'

Pinned hash 95789d6405e9, from Nov 15, 2026, 00:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.rightaichoice/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.rightaichoice/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.rightaichoice/mcp.svg)](https://radar.anlyon.com/servers/com.rightaichoice/mcp)

Source: MCP Registry · repository. Synced Nov 1, 2026, 22:17 UTC.

RightAIChoice — verified AI tool data MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 13 tools, 10 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RightAIChoice — verified AI tool data MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RightAIChoice — verified AI tool data MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RightAIChoice — verified AI tool data MCP server have?

13 tools: 10 write, 3 read. market_sentiment, deadpool_digest, viability_score, pricing_reality, whats_changed, recommend_tools, best_for, category_landscape and 5 more.

Does the RightAIChoice — verified AI tool data MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RightAIChoice — verified AI tool data MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RightAIChoice — verified AI tool data MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 29, 2026. Every change is on this page and in its Atom feed.