FutureSmart AI Demos

REMOTE · MCP.AIDEMOS.COM · SCANNED AUG 3

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

Available components

0 this week 60 60 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security46

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability73

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2000 tokens (~125/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage98

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
95% of tool parameters carry a description.Partial

Capabilities60

Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.aidemos.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

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

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-aidemos-catalogue": {
      "type": "remote",
      "url": "https://mcp.aidemos.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-aidemos-catalogue --url https://mcp.aidemos.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-aidemos-catalogue:
    url: "https://mcp.aidemos.com/mcp"

// mcp.json

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog Show cosmetic changes

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

3 Aug 26 +1
- Tool “get_tool” rewrote its description, which is the text the model reads security
- Tool “get_ranking” rewrote its description, which is the text the model reads security
- Schema quality: 107 → 125 ▼ functional
- Schema quality: good → excellent functional
- “get_tool” added an optional parameter “proof” cosmetic
- “get_ranking” added an optional parameter “proof” cosmetic
- “get_tool” reworded the description of “fields” cosmetic
2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 −4
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +10
- HSTS header: unverified → fail ▼ security
- HTTPS: pass → unverified ▼ security
- TLS certificate: unverified → pass ▲ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 16 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
29 Jul 26 −8
- TLS certificate: pass → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- HTTPS: unverified → pass ▲ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 59

First indexed and scored.

Show 4 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.aidemos.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mcp.aidemos.com	CN=Amazon RSA 2048 M01,O=Amazon,C=US	13 Jun 2026	27 Dec 2026	RSA 2048	SHA256-RSA	38c81505f6662c5fff90df9a13d6c0e
SANs: mcp.aidemos.com
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA)	CN=Amazon Root CA 1,O=Amazon,C=US	23 Aug 2022	23 Aug 2030	RSA 2048	SHA256-RSA	77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA)	CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US	25 May 2015	31 Dec 2037	RSA 2048	SHA256-RSA	67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

DNSSEC insecure

Validation of mcp.aidemos.com. — Not signed

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
aidemos.com.	absent			Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.aidemos.com/mcp	Verified	200
http (plaintext)	http://mcp.aidemos.com/mcp	Inconclusive	404

MCP tools — 16 exposed · ~1,900 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

compare_tools ~120

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.

Input Output Examples

Name	Type	Req	Description
criterion	string	—	Optional: restrict to one criterion.
tool_a	string	yes	First tool slug, e.g. "llamaparse".
tool_b	string	yes	Second tool slug, e.g. "landing-ai".

No output schema declared.

No examples provided.

get_evidence ~240

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.

Input Output Examples

Name	Type	Req	Description
criterion	string	—	Criterion slug or name, e.g. "table extraction".
evidence	string	—	—
limit	integer	—	Max cells (default 50).
ranking	string	—	Ranking page slug — scope cells to the evidence run that published ranking is bound to (exactly what the page renders).
scenario	string	—	Scenario slug, cross-run group tag (e.g. "scanned-research-paper"), or name fragment.
tool	string	—	Tool slug or name, e.g. "landing-ai".
tools	array	—	Several tools at once.
verdict	string	—	—

No output schema declared.

No examples provided.

get_persona ~60

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

Input Output Examples

Name	Type	Req	Description
slug	string	yes	Persona slug, e.g. "students".

No output schema declared.

No examples provided.

get_ranking ~319

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

Input Output Examples

Name	Type	Req	Description
fields	array	—	Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, title, slug, url, abstract, read_time, tested_dat…
proof	string	—	How many proof artifacts to inline. "sample" (default) = up to 6 per tool, spread across distinct criteria so you see breadth; "full" = every artifact; "none" = counts only, no URLs. Counts (artifact…
slug	string	yes	Ranking slug, e.g. "resume-parsing-api" (from list_rankings).

No output schema declared.

No examples provided.

get_tool ~308

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

Input Output Examples

Name	Type	Req	Description
fields	array	—	Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, name, slug, url, heading, website, domain, catego…
proof	string	—	How many proof artifacts to inline. "sample" (default) = up to 6 per tool, spread across distinct criteria so you see breadth; "full" = every artifact; "none" = counts only, no URLs. Counts (artifact…
slug	string	yes	Tool seo_slug, e.g. "affinda" (from list_tools).

No output schema declared.

No examples provided.

get_use_case ~151

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

Input Output Examples

Name	Type	Req	Description
fields	array	—	Optional projection: return ONLY these top-level fields (identity id/name/title/slug/url is always included) to control response size. Available: id, title, slug, url, abstract, read_time, category,…
slug	string	yes	Use-case slug (from list_use_cases).

No output schema declared.

No examples provided.

list_categories ~32

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_compares ~68

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max items to return. Omit for all.
offset	integer	—	Items to skip (paging).

No output schema declared.

No examples provided.

list_personas ~41

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

Input Output Examples

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_rankings ~72

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max items to return. Omit for all.
offset	integer	—	Items to skip (paging).

No output schema declared.

No examples provided.

list_toolkits ~56

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max items to return. Omit for all.
offset	integer	—	Items to skip (paging).

No output schema declared.

No examples provided.

list_tools ~57

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max items to return. Omit for all.
offset	integer	—	Items to skip (paging).

No output schema declared.

No examples provided.

list_use_cases ~62

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

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max items to return. Omit for all.
offset	integer	—	Items to skip (paging).

No output schema declared.

No examples provided.

rankings_for_tool ~59

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

Input Output Examples

Name	Type	Req	Description
tool_id	string\|integer	yes	Tool id (from list_tools).

No output schema declared.

No examples provided.

search ~183

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.

Input Output Examples

Name	Type	Req	Description
category	string	—	Restrict to this category (case-insensitive).
limit	integer	—	Max results (default 20).
mode	string	—	Search mode.
persona	string	—	Restrict to items tagged with this persona slug.
query	string	yes	Free-text search query.
type	array	—	Restrict to these kinds (default: all).

No output schema declared.

No examples provided.

tools_in_ranking ~72

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

Input Output Examples

Name	Type	Req	Description
ranking_id	string\|integer	yes	Ranking id (from list_rankings).

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	59
27 Jul	60
28 Jul	60
29 Jul	52
30 Jul	62
31 Jul	58
1 Aug	58
2 Aug	59
3 Aug	60