Skip to content

FutureSmart AI Demos MCP server

com.aidemos/catalogueaidemos.comstreamable-httpv2.0.0Scanned

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

17 tools: 3 change things and 14 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

3 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 FutureSmart AI Demos MCP server can do

The FutureSmart AI Demos MCP server is published by aidemos.com, a domain the MCP Registry verified. It has 17 tools. It can create or change data (3 tools: answer, tools_in_ranking and rankings_for_tool), but cannot delete data. 14 tools only read.

1 tool reads private data (get_evidence); 6 tools bring in text other people can write (list_use_cases, list_rankings, list_tools and 3 more).

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.

Last scanned Nov 12, 2026, version 2.0.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.

17 tools

Changes things 3Claude Code: ask
  • answerANSWER a buyer question in ONE call: which tool is best at a specific capability, with proof.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.
    Description, as the server wrote it
    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.
  • rankings_for_toolGiven a tool id, return the tool {id,name,slug} and every ranking it appears in [{id,title,slug,url,use_case,rank,badge}].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.
    Description, as the server wrote it
    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_in_rankingGiven 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).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.
    Description, as the server wrote it
    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).
Only reads 14Show 14 read-only tools
  • compare_toolsEvidence-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 (sam…No findings

    Why it is in this group

    • The name "compare_tools" says "compare": a word for reading.
    Description, as the server wrote it
    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.
  • get_evidenceQuery the evidence graph: observation cells (tool × test-scenario × criterion) → verdict, score, the researcher's note, and the REAL artifacts (input/output screenshots) that prove…Reads private dataNo findings

    Why it is in this group

    • The name "get_evidence" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "query" and "note": it reads notes.
    Description, as the server wrote it
    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.
  • get_personaGiven a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[].No findings

    Why it is in this group

    • The name "get_persona" says "get": a word for reading.
    Description, as the server wrote it
    Given a persona slug (from list_personas), return everything tagged with it: persona, use_cases[], rankings[], compares[], toolkits[], tools[]. Mirrors a persona landing page.
  • get_rankingFull ranking detail as a JSON+Markdown envelope: ranked tools (rank/badge/scores), criteria, winner, breakdown (JSON) + verdicts / final take (Markdown).No findings

    Why it is in this group

    • The name "get_ranking" says "get": a word for reading.
    Description, as the server wrote it
    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).
  • get_toolFull tool detail as a JSON+Markdown envelope: identity, pricing, per-feature scores, fit, FAQ, relationships (JSON) + our_take / in-depth review (Markdown).Reads text others writeNo findings

    Why it is in this group

    • The name "get_tool" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "review": it reads comments, which other people can write.
    Description, as the server wrote it
    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).
  • get_use_caseFull use-case detail as a JSON+Markdown envelope: step guide, pros/cons, FAQ, tools used (JSON) + the full narrative guide (Markdown, full_md).No findings

    Why it is in this group

    • The name "get_use_case" says "get": a word for reading.
    Description, as the server wrote it
    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_categoriesList the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.No findings

    Why it is in this group

    • The name "list_categories" says "list": a word for reading.
    Description, as the server wrote it
    List the category vocabulary in use with per-type counts and a source flag ("collection"|"derived"), sorted by total.
  • list_comparesList published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.Reads text others writeNo findings

    Why it is in this group

    • The name "list_compares" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List published head-to-head comparison pages: id, title, slug, url, tool_a, tool_b, personas[], shared_use_cases[], updated_at.
  • list_personasList personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}.No findings

    Why it is in this group

    • The name "list_personas" says "list": a word for reading.
    Description, as the server wrote it
    List personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}. The slugs are valid input for get_persona.
  • list_rankingsList published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.Reads text others writeNo findings

    Why it is in this group

    • The name "list_rankings" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List published ranking pages ("best X"): id, title, slug, url, use_case, persona, category, tools_count, winner, tested_as_of, updated_at.
  • list_toolkitsList published toolkit pages (curated bundles): id, title, slug, url, category.Reads text others writeNo findings

    Why it is in this group

    • The name "list_toolkits" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List published toolkit pages (curated bundles): id, title, slug, url, category.
  • list_toolsList published AI tool pages: id, name, slug, url, domain, personas[], categories[].Reads text others writeNo findings

    Why it is in this group

    • The name "list_tools" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List published AI tool pages: id, name, slug, url, domain, personas[], categories[].
  • list_use_casesList published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.Reads text others writeNo findings

    Why it is in this group

    • The name "list_use_cases" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    List published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.

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

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
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:33 UTC, unchanged since Oct 22, 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
3
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 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.aidemos.com/mcp: tools/list returned 17 tools to an anonymous client, including answer (write), tools_in_ranking (write), rankings_for_tool (write)

    What this check looks for

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.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

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

claude mcp add --transport http catalogue https://mcp.aidemos.com/mcp
claude mcp add --transport http catalogue https://mcp.aidemos.com/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__catalogue__list_use_cases",
      "mcp__catalogue__list_rankings",
      "mcp__catalogue__list_tools",
      "mcp__catalogue__list_compares",
      "mcp__catalogue__list_toolkits",
      "mcp__catalogue__list_personas",
      "mcp__catalogue__list_categories",
      "mcp__catalogue__search",
      "mcp__catalogue__get_persona",
      "mcp__catalogue__get_tool",
      "mcp__catalogue__get_ranking",
      "mcp__catalogue__get_use_case",
      "mcp__catalogue__get_evidence",
      "mcp__catalogue__compare_tools"
    ],
    "ask": [
      "mcp__catalogue__answer",
      "mcp__catalogue__tools_in_ranking",
      "mcp__catalogue__rankings_for_tool"
    ],
    "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 catalogue. Review it before you use it.

Capability tags behind 7 rules
  • mcp__catalogue__list_use_cases untrusted-input
  • mcp__catalogue__list_rankings untrusted-input
  • mcp__catalogue__list_tools untrusted-input
  • mcp__catalogue__list_compares untrusted-input
  • mcp__catalogue__list_toolkits untrusted-input
  • mcp__catalogue__get_tool untrusted-input
  • mcp__catalogue__get_evidence private-data

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.aidemos/catalogue/verify?hash=a8e07d1bf6ca6b1233246371778b8e66ff8a426c62b82d05743c7eba24ecba6f" | jq -e '.changed == false'

Pinned hash a8e07d1bf6ca, from Nov 12, 2026, 13:18 UTC.

Watch

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

https://radar.anlyon.com/servers/com.aidemos/catalogue/changes.xml

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

Badge

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

Source: MCP Registry. Synced Oct 21, 2026, 17:48 UTC.

FutureSmart AI Demos MCP server: questions and answers

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

Is the FutureSmart AI Demos MCP server safe?

No scan can promise that. What its definitions show: 17 tools, 3 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 FutureSmart AI Demos MCP server delete data?

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

Can the FutureSmart AI Demos 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 FutureSmart AI Demos MCP server have?

17 tools: 3 write, 14 read. answer, tools_in_ranking, rankings_for_tool, list_use_cases, list_rankings, list_tools, list_compares, list_toolkits and 9 more.

Does the FutureSmart AI Demos MCP server need sign-in or OAuth?

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

Does the FutureSmart AI Demos MCP server send data to outside services?

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

Has the FutureSmart AI Demos MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 12, 2026.