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。

  • 授權條款不適用

    託管服務按其提供方的條款使用,因此這裡不要求授權條款。此檢查項不計入百分比。