MCP Server for Z.AI - A Model Context Protocol server that provides AI capabilities
Nothing to run from here
RightAIChoice — verified AI tool data is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
12
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
What changed, what died, what it costs, what survives: 8,000+ AI tools, verified and dated.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http rightaichoice-verified-ai-tool-data-mcp https://rightaichoice.com/api/mcp
# 2 — ask your agent for something these tools do
# check_tool_status, compare_tools, find_alternatives and 9 more
RightAIChoice — verified AI tool data costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
RIAll 1 server
rightaichoice1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http rightaichoice-verified-ai-tool-data-mcp https://rightaichoice.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
12 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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, a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. | |
| response_format | string | no | concise = verdict + freshness + source link. detailed = adds viability signals, link health, sentiment, pricing, and alternatives. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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. |
| response_format | string | no | concise = per-tool verdict + pricing + editorial verdict. detailed = adds sentiment, viability signals, and link health per 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | The AI tool to find alternatives for — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | The AI tool to get sentiment for — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
| response_format | string | no | concise = label, verdict line, top pro/con, mention count. detailed = adds per-source breakdown, up to 4 pros/cons, and recurring themes. |
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 ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| response_format | string | no | concise = headline mortality figures from both datasets. detailed = adds fastest/slowest-decaying categories and survival splits by launch votes and rank. |
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 a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | The AI tool to assess — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
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 undisclose
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | yes | The AI tool to get pricing for — product name (e.g. "Jasper") or site slug (e.g. "jasper"). |
| response_format | string | no | concise = pricing model + plan prices + top 2 hidden costs. detailed = full plan list with key features and up to 6 hidden costs. |
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 carrie
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | no | Optional. A single AI tool — product name or slug. Omit for a market-wide summary. |
| since | string | no | Optional ISO date (YYYY-MM-DD). Defaults to 7 days ago. Earlier than our coverage floor returns the floor. |
| include | string | no | 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 | no | concise = counts plus the most notable changes. detailed = the individual dated changes. |
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 o
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | 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 | no | Only return tools recorded as offering an API. |
| survival_bar | string | no | 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. no |
| exclude_wrappers | boolean | no | Exclude tools assessed as thin wrappers around a third-party model. |
| limit | integer | no | How many results to return (max 10). |
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 ca
| Parameter | Type | Required | Notes |
|---|---|---|---|
| category | string | yes | The category, in plain words or as a slug — e.g. "image generation", "code-development". |
| response_format | string | no | concise = size, distribution and the strongest few. detailed = adds the weakest end and the decay rate. |
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 RightA
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tools | array | yes | The tools the team pays for — product names or slugs. Between 2 and 15. |
| response_format | string | no | concise = overlapping pairs only. detailed = also lists pairs we found no overlap between. |
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 en
| Parameter | Type | Required | Notes |
|---|---|---|---|
| server | string | yes | The MCP server name or part of it, e.g. "rightaichoice" or "com.example/mcp". Not a URL — only registry-published endpoints are ever contacted. |
| probe | boolean | no | Whether to make one anonymous request to a registry-published endpoint to see if it responds. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install RightAIChoice — verified AI tool data or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish RightAIChoice — verified AI tool data can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.