MCP server for advanced web search using Tavily
FutureSmart AI Demos 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.
What it does
Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http futuresmart-ai-demos-mcp https://mcp.aidemos.com/mcp
# 2 — ask your agent for something these tools do
# answer, list_use_cases, list_rankings and 14 more
FutureSmart AI Demos costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
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.
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 futuresmart-ai-demos-mcp https://mcp.aidemos.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
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.
17 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.
ANSWER a buyer question in ONE call: which tool is best at a specific capability, with proof. Returns the resolved verdict our testing team's evidence supports — a named winner FOR THE ASKED CRITERION, every tested tool ranked with a comparable score /5, the CONDITIONS each result holds under (e.g. 'clean tables yes; nested headers no'), dissenting observations preserved as openable links, the tie
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | no | The buyer question in natural language, e.g. 'Which document extraction tool best preserves table structure from scanned PDFs?'. Alternative: pass ranking + criterion explicitly. |
| ranking | string | no | Ranking slug (skips routing). |
| criterion | string | no | Criterion slug or exact name (with ranking). |
| scenario | string | no | Optional scenario/condition of interest. |
List published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max items to return. Omit for all. |
| offset | integer | no | Items to skip (paging). |
List published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max items to return. Omit for all. |
| offset | integer | no | Items to skip (paging). |
List published AI tool pages: id, name, slug, url, domain, personas[], categories[].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max items to return. Omit for all. |
| offset | integer | no | Items to skip (paging). |
List published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max items to return. Omit for all. |
| offset | integer | no | Items to skip (paging). |
List published toolkit pages (curated bundles): id, title, slug, url, category.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | integer | no | Max items to return. Omit for all. |
| offset | integer | no | Items to skip (paging). |
List personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}. The slugs are valid input for get_persona.
No parameter schema on file.
List the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.
No parameter schema on file.
Search the published catalogue across use cases, rankings, tools, comparisons, and toolkits. Returns ranked light refs [{ kind, id, title, slug, url, snippet, score, meta }] — then call get_tool / get_ranking / get_use_case for full detail. mode: keyword (substring), semantic (meaning, via embeddings — finds pages by what they cover), or hybrid (default, fuses both). Optional filters: type[], pe
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Free-text search query. |
| mode | string | no | Search mode. |
| type | array | no | Restrict to these kinds (default: all). |
| persona | string | no | Restrict to items tagged with this persona slug. |
| category | string | no | Restrict to this category (case-insensitive). |
| limit | integer | no | Max results (default 20). |
Given a ranking id, return the ranking {id,title,slug} and its ranked tools [{id,name,slug,url,rank,badge}] (badge: Best/Usable/Needs work/Unstable/Failed).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ranking_id | string/integer | yes | Ranking id (from list_rankings). |
Given a tool id, return the tool {id,name,slug} and every ranking it appears in [{id,title,slug,url,use_case,rank,badge}].
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool_id | string/integer | yes | Tool id (from list_tools). |
Given a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[]. Mirrors a persona landing page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Persona slug, e.g. "students". |
Full tool detail as a JSON+Markdown envelope: identity, pricing, per-feature scores, fit, FAQ, relationships (JSON) + our_take / in-depth review (Markdown). Includes proof: real artifact URLs (input/output screenshots, recordings) from the runs that tested it, each with the /evidence permalink for the finding it proves — you can cite evidence from THIS call. null if unknown. Pass fields to pro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Tool seo_slug, e.g. "affinda" (from list_tools). |
| fields | array | no | Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, name, slug, url, heading, website, domain, categor |
| proof | string | no | How many proof artifacts to inline. "sample" (default) = up to 6 per tool, spread across distinct criteria so you see breadth; "full" = every artifact; "none" = counts only, no URLs. Counts (artifact_ |
Full ranking detail as a JSON+Markdown envelope: ranked tools (rank/badge/scores), criteria, winner, breakdown (JSON) + verdicts / final take (Markdown). Every ranked tool carries proof: real artifact URLs from the exact evidence run this page is bound to, each with the /evidence permalink for the finding it proves — verdict and proof arrive together, no second call needed to cite evidence. `pro
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Ranking slug, e.g. "resume-parsing-api" (from list_rankings). |
| fields | array | no | Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, title, slug, url, abstract, read_time, tested_date |
| proof | string | no | How many proof artifacts to inline. "sample" (default) = up to 6 per tool, spread across distinct criteria so you see breadth; "full" = every artifact; "none" = counts only, no URLs. Counts (artifact_ |
Full use-case detail as a JSON+Markdown envelope: step guide, pros/cons, FAQ, tools used (JSON) + the full narrative guide (Markdown, full_md). null if unknown. Pass fields to project to only the keys you need (token-efficient).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | Use-case slug (from list_use_cases). |
| fields | array | no | Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, title, slug, url, abstract, read_time, category, a |
Query the evidence graph: observation cells (tool × test-scenario × criterion) → verdict, score, the researcher's note, and the REAL artifacts (input/output screenshots) that prove it. The ground truth behind every ranking — filter any combination of tool(s), scenario (slug, group tag, or name), criterion, verdict, or evidence state. evidence_state: "verified" = artifact-backed, "observed" = noted
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool | string | no | Tool slug or name, e.g. "landing-ai". |
| tools | array | no | Several tools at once. |
| ranking | string | no | Ranking page slug — scope cells to the evidence run that published ranking is bound to (exactly what the page renders). |
| scenario | string | no | Scenario slug, cross-run group tag (e.g. "scanned-research-paper"), or name fragment. |
| criterion | string | no | Criterion slug or name, e.g. "table extraction". |
| verdict | string | no | — |
| evidence | string | no | — |
| limit | integer | no | Max cells (default 50). |
Evidence-aligned comparison of two tools, honesty enforced structurally: head_to_head (cells from the SAME test input — provable same-input comparison), related_not_same_input (same dimension, different runs — flagged), and each tool's unique evidence. Built from real observation cells with artifacts, not prose.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tool_a | string | yes | First tool slug, e.g. "llamaparse". |
| tool_b | string | yes | Second tool slug, e.g. "landing-ai". |
| criterion | string | no | Optional: restrict to one criterion. |
- 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 FutureSmart AI Demos or to call it, at any volume.
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. 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 2.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish FutureSmart AI Demos can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.