FutureSmart AI Demos

by aidemos.com · remote · no sign-in to list tools · v2.0.0 · published by com.aidemos

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

Changes · 3

Compare Registry entry

17 tools: 3 change things and 14 only read.

Scanned Oct 21, 2026

Deletes or cancels0Claude Code: deny
Can't be undone0Claude Code: ask
Changes things3Claude Code: ask: see these tools
Only reads14Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

17 tools

Changes things 3Creates or changes something that can be changed back.Claude 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 14Looks things up and changes nothing.Claude Code: allow

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…No findings
Why it is in this group
- The name "get_evidence" says "get": a word for reading.
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).No findings
Why it is in this group
- The name "get_tool" says "get": a word for reading.
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.No findings
Why it is in this group
- The name "list_compares" says "list": a word for reading.
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.No findings
Why it is in this group
- The name "list_rankings" says "list": a word for reading.
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.No findings
Why it is in this group
- The name "list_toolkits" says "list": a word for reading.
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[].No findings
Why it is in this group
- The name "list_tools" says "list": a word for reading.
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.No findings
Why it is in this group
- The name "list_use_cases" says "list": a word for reading.
Description, as the server wrote it
List published use-case pages (how-to guides): id, title, slug, url, persona, category, updated_at.
searchSearch the published catalogue across use cases, rankings, tools, comparisons, and toolkits.No findings
Why it is in this group
- The name "search" says "search": a word for reading.
Description, as the server wrote it
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.

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.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, 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. It assumes the server is installed as catalogue. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

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

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

Anlyon alternative

3 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Compare with other servers for the same product.

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

For agents: Markdown · JSON · report this listing