FutureSmart AI Demos

com.aidemos由 aidemos.com 发布官方发布者v2.0.0更新于 Oct 28, 2026

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

已验证Streamable HTTP可网页运行网页搜索与抓取知识与记忆

概览

AI 生成的概览

只读的远程 MCP 服务器,提供有证据支撑的 AI 工具目录:评测排名、对比、使用场景与工具包。

可以做什么
  • 按关键词或语义搜索已发布目录,返回使用场景、排名、工具、对比和工具包的简要引用
  • 浏览工具、排名、对比、使用场景、工具包、人物画像与分类的列表及数量
  • 读取工具、排名或使用场景的完整详情,包括评分、定价、结论与叙述性评测
  • 查看工具与排名之间的关联,并获取某个画像标签下的全部内容
  • 查询由观测单元构成的证据图谱,并在相同测试输入下对比两个工具
适用场景
适合在需要为某项具体能力挑选 AI 工具时,获取经过测试、带证据的排名结论,而不是营销说辞;也适合查找操作指南和两两对比。
运行要求
远程 streamable HTTP 端点;未声明任何认证、环境变量或请求头。
安装前请注意
内容为第三方编辑观点与测试结果,结论和评分反映提供方自身的测试与条件。排名应作为参考而非中立事实。

安装

在 SourceWeft 中

  1. 打开 控制台中的 FutureSmart AI Demos,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/com.aidemos%2Fcatalogue/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。

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

工具

17

answer

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.

输入参数rankingquestionscenariocriterion

list_use_cases

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

输入参数limitoffset

list_rankings

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

输入参数limitoffset

list_tools

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

输入参数limitoffset

list_compares

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

输入参数limitoffset

list_toolkits

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

输入参数limitoffset

list_personas

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

无需输入参数。

list_categories

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

无需输入参数。

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

输入参数ranking_id必填

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

输入参数tool_id必填

get_persona

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

输入参数slug必填

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

输入参数slug必填prooffields

get_ranking

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

输入参数slug必填prooffields

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). null if unknown. Pass `fields` to project to only the keys you need (token-efficient).

输入参数slug必填fields

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

输入参数toollimittoolsrankingverdictevidencescenariocriterion

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. Built from real observation cells with artifacts, not prose.

输入参数tool_a必填tool_b必填criterion

版本历史

1
  1. v2.0.0最新Sep 16, 2026

评分

已满足适用检查项的 83%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具必需15 分
  • 描述必需15 分
  • 图标10 分
  • 文档15 分

    请声明包含 README 的 GitHub 仓库,或在 OAuth 受保护资源元数据中提供 resource_documentation。

  • 许可证不适用

    托管服务按其提供方的条款使用,因此这里不要求许可证。此检查项不计入百分比。