mcpbeat

FutureSmart AI Demos MCP Server

com.aidemos/catalogue
answering

FutureSmart AI Demos is answering right now. Last checked moments ago. It exposes 16 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
92 of 92 checks
16
Tools
read from the server
377 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add catalogue --transport http https://mcp.aidemos.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "catalogue": {
      "url": "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
{
  "mcpServers": {
    "catalogue": {
      "url": "https://mcp.aidemos.com/mcp"
    }
  }
}

Available tools 16

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

URLTransportStateLatencyChecked
https://mcp.aidemos.com/mcp streamable-http answering 366 ms 0 min ago

FutureSmart AI Demos — questions

Answers built from our own checks of this server.

What can FutureSmart AI Demos do?
It exposes 16 tools, read directly from the server on our last check. Among them: compare_tools, get_evidence, get_persona, get_ranking, get_tool, get_use_case and 10 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 92 of 92 checks got a reply (100.0%), average response time 377 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 with the file path 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 16 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 377 ms on average, which is faster than 36% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.