API Tools

aidemos.com

Provides structured data about AI tools, including use cases, rankings, comparisons, and toolkits.

2 endpoints33 known toolsFirst detected July 25, 2026Last detected August 29, 2026

ENDPOINT 1

https://mcp.aidemos.com/mcp

No auth detected

MCP server metadata

Name: aidemos-mcp
Version: 2.0.0

Capabilities

tools

Server instructions

Evidence-backed answers about AI tools, from hands-on testing (published data only). START WITH `answer` for any 'which tool is best at X' question — it returns the resolved verdict in one call: winner for the asked criterion, ranked scores, the conditions each result holds under, dissent preserved, openable proof; it refuses honestly when we never tested the topic. Then: list_* to enumerate use cases, rankings, tools, comparisons, toolkits, personas, and categories; tools_in_ranking / rankings_for_tool to traverse; get_persona for everything tagged to a persona; get_tool / get_ranking / get_use_case for the full page as a JSON-structure + Markdown-content envelope; get_evidence for the raw observation cells behind any answer. Every entity has id, slug, and a full url.

Known tools 17

answer

ANSWER a buyer question in ONE call: which tool is best at a specific capability, with proof.

Inferred read-only

list_use_cases

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

Inferred read-only

list_rankings

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

Inferred read-only

list_tools

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

Inferred read-only

list_compares

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

Inferred read-only

list_toolkits

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

Inferred read-only

list_personas

List personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}.

Inferred read-only

list_categories

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

Inferred read-only

search

Search the published catalogue across use cases, rankings, tools, comparisons, and toolkits.

Inferred read-only

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

Inferred read-only

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

Inferred read-only

get_persona

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

Inferred read-only

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

Inferred read-only

get_ranking

Full ranking detail as a JSON+Markdown envelope: ranked tools (rank/badge/scores), criteria, winner, breakdown (JSON) + verdicts / final take (Markdown).

Inferred read-only

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

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aidemos-mcp]
url = "https://mcp.aidemos.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "aidemos-mcp": {
      "type": "http",
      "url": "https://mcp.aidemos.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: aidemos-mcp
Remote MCP URL: https://mcp.aidemos.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "aidemos-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.aidemos.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://mcp.aidemos.com/api/mcp

No auth detected

MCP server metadata

Name: aidemos-mcp
Version: 2.0.0

Capabilities

tools

Server instructions

Discovery + detail API for the FutureSmart AI Demos catalogue (published data only). Use list_* to enumerate use cases, rankings, tools, comparisons, toolkits, personas, and categories; tools_in_ranking / rankings_for_tool to traverse; get_persona for everything tagged to a persona; and get_tool / get_ranking / get_use_case for the full page as a JSON-structure + Markdown-content envelope. Every entity has id, slug, and a full url.

Known tools 16

list_use_cases

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

Inferred read-only

list_rankings

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

Inferred read-only

list_tools

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

Inferred read-only

list_compares

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

Inferred read-only

list_toolkits

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

Inferred read-only

list_personas

List personas with published-page counts per type {use_cases, rankings, tools, compares, toolkits}.

Inferred read-only

list_categories

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

Inferred read-only

search

Search the published catalogue across use cases, rankings, tools, comparisons, and toolkits.

Inferred read-only

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

Inferred read-only

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

Inferred read-only

get_persona

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

Inferred read-only

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

Inferred read-only

get_ranking

Full ranking detail as a JSON+Markdown envelope: ranked tools (rank/badge/scores), criteria, winner, breakdown (JSON) + verdicts / final take (Markdown).

Inferred read-only

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

Inferred read-only

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.

Inferred read-only

compare_tools

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.aidemos-mcp]
url = "https://mcp.aidemos.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "aidemos-mcp": {
      "type": "http",
      "url": "https://mcp.aidemos.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: aidemos-mcp
Remote MCP URL: https://mcp.aidemos.com/api/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "aidemos-mcp",
  "transport": "streamable-http",
  "url": "https://mcp.aidemos.com/api/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for aidemos.com was fetched 2026-08-26T00:04:33.611Z.

Trust status RestrictedContent

aidemos.com is assessed as RestrictedContent: Domain runs gambling-related technology.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.