FutureSmart AI Demos MCP Server

by aidemos Your server? Claim it

answering

FutureSmart AI Demos is answering right now. Last checked 6 min ago. It exposes 17 tools.

Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).

Uptime history 91 days of history · worst day 98%

91 days agonow

97.8%

Uptime 24h

89 of 91 checks

Tools

read from the server

409 ms

Response time

average over 24h

open, no key

Access

streamable-http

FutureSmart AI Demos missed 3 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add catalogue --transport http https://mcp.aidemos.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.aidemos.com/mcp

~/.codex/config.toml

[mcp_servers.catalogue]
url = "https://mcp.aidemos.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "catalogue": {
      "url": "https://mcp.aidemos.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "catalogue": {
      "type": "http",
      "url": "https://mcp.aidemos.com/mcp"
    }
  }
}

Available tools 17

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

rankings

list_rankings

List published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.

rankings_for_tool

Given a tool id, return the tool {id,name,slug} and every ranking it appears in [{id,title,slug,url,use_case,rank,badge}].

tools

list_tools

List published AI tool pages: id, name, slug, url, domain, personas[], categories[].

tools_in_ranking

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).

use

get_use_case

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).

list_use_cases

List published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.

answer

answer

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-break reason, and artifact proof URLs. Answers are materialized from the evidence substrate — the same question returns the same answer. Honestly refuses (coverage: not_tested) when we never tested the topic. Start HERE for any 'which tool is best at X' / 'A or B for X' question; use get_evidence for the raw cells behind it.

categories

list_categories

List the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.

compare

compare_tools

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.

compares

list_compares

List published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.

evidence

get_evidence

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 without artifact, "scored-only" = number only.

persona

get_persona

Given a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[]. Mirrors a persona landing page.

personas

list_personas

List personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}. The slugs are valid input for get_persona.

ranking

get_ranking

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. `proof.artifact_count` is the true total and `proof.all_findings` is the get_evidence call that returns all of it. null if unknown. Pass `fields` to project to only the keys you need (token-efficient).

search

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[], persona, category.

tool

get_tool

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 project to only the keys you need (token-efficient).

toolkits

list_toolkits

List published toolkit pages (curated bundles): id, title, slug, url, category.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.aidemos.com/mcp	streamable-http	answering	431 ms	6 min ago

Alternatives to FutureSmart AI Demos

same job, measured the same way

Iranketab Books

by sepehr071

Read-only Iranketab (iranketab.ir) books: search, translations compared, ratings, reviews, prices.

334 installs/wk local only

One AI Guide

by oneaiguide

Read-only approved AI tools, public stacks, guides, and evidence-aware comparisons.

7 tools answering

Saaskly: B2B software reviews and comparisons

by saaskly

Independent UK business software reviews, rankings and real pricing as read-only MCP tools.

9 tools answering

Git.Top

by haocn-ops

Evidence-backed open-source project search, recommendations, alternatives, and comparisons.

5 tools answering

Starbelo

by starbelo

Search real AI money-making use cases, AI tools and prompts from Starbelo. Free, read-only.

3 tools answering

VaultVision Hyperliquid Vault Research

by 0xkayser

Read-only Hyperliquid vault search, risk, drawdown, rankings, TVL, alerts, and comparisons.

9 tools answering

Macaroon Bible Evidence

by macaroonnetwork

Read-only BSB and WEB Scripture evidence with provenance, context, comparison, and search.

11 tools answering

Peptides Academy

by peptidesacademy

Evidence-first peptide research: summaries and comparisons from cited dossiers, linked to courses.

4 tools answering

FutureSmart AI Demos — questions

Answers built from our own checks of this server.

What can FutureSmart AI Demos do?

It exposes 17 tools, read directly from the server on our last check. Among them: answer, compare_tools, get_evidence, get_persona, get_ranking, get_tool and 11 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

What is FutureSmart AI Demos mostly used for?

Its tools cluster around use, rankings and tools. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.

Is FutureSmart AI Demos working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 409 ms. The bar chart above shows every period we have measured.

How do I connect FutureSmart AI Demos?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does FutureSmart AI Demos need an API key?

No. FutureSmart AI Demos completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 17 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is FutureSmart AI Demos?

It answers our handshake in 409 ms on average, which is faster than 32% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.