FutureSmart AI Demos
REMOTE · MCP.AIDEMOS.COM · SCANNED SEP 27
Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only).
Available components
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 → Why this is hard to 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 17 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 enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement. 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 2315 tokens (~136/item across 17 items; 17 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the FutureSmart AI Demos MCP server?
FutureSmart AI Demos is a hosted endpoint at https://mcp.aidemos.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.aidemos.com
claude mcp add --transport http com-aidemos-catalogue 'https://mcp.aidemos.com/mcp'
{
"mcpServers": {
"com-aidemos-catalogue": {
"url": "https://mcp.aidemos.com/mcp"
}
}
} {
"servers": {
"com-aidemos-catalogue": {
"type": "http",
"url": "https://mcp.aidemos.com/mcp"
}
}
} [mcp_servers.com-aidemos-catalogue] url = "https://mcp.aidemos.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-aidemos-catalogue": {
"type": "remote",
"url": "https://mcp.aidemos.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-aidemos-catalogue --url 'https://mcp.aidemos.com/mcp' --transport streamable-http
mcp_servers:
com-aidemos-catalogue:
url: "https://mcp.aidemos.com/mcp" {
"McpServers": {
"com-aidemos-catalogue": {
"Transport": "http",
"Url": "https://mcp.aidemos.com/mcp"
}
}
} assistant mcp add com-aidemos-catalogue -t streamable-http -u 'https://mcp.aidemos.com/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 −1
- Stability: pass → 0.97 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 19 Aug 26 0
- HSTS header: unverified → fail ▼ security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 17 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
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.80 ▲ functional
- 18 Aug 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.73 → unverified ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 27 Sept 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 |
Background: What to check on a remote MCP endpoint →
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
answer ~245
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.
| Name | Type | Req | Description |
|---|---|---|---|
| criterion | string | – | Criterion slug or exact name (with `ranking`). |
| question | string | – | The buyer question in natural language, e.g. 'Which document extraction tool best preserves table structure from scanned PDFs?'. Alternative: pass ranking + criterion explicitly. |
| ranking | string | – | Ranking slug (skips routing). |
| scenario | string | – | Optional scenario/condition of interest. |
No output schema declared.
No examples provided.
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.
| 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.
| 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.
| 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).
| 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).
| 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).
| 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 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.
| 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 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.
| 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.
| 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[].
| 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.
| 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}].
| 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.
| 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).
| Name | Type | Req | Description |
|---|---|---|---|
| ranking_id | string|integer | yes | Ranking id (from list_rankings). |
No output schema declared.
No examples provided.
What is the FutureSmart AI Demos MCP server?
FutureSmart AI Demos is an MCP server listed in the public MCP registry as com.aidemos/catalogue. Search evidence-backed AI-tool reviews, rankings, use cases, comparisons & toolkits (read-only). This page covers its hosted endpoint (https://mcp.aidemos.com/mcp).
Is the FutureSmart AI Demos MCP server safe to use?
FutureSmart AI Demos scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the FutureSmart AI Demos MCP server expose?
FutureSmart AI Demos exposes 17 tools: answer, list_use_cases, list_rankings, list_tools, list_compares, and 12 more. Their descriptions and schemas cost roughly 2,145 tokens of context every time the server is loaded.
Does the FutureSmart AI Demos MCP server require authentication?
No. We connected to FutureSmart AI Demos without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the FutureSmart AI Demos MCP server still maintained?
FutureSmart AI Demos is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.