Allfeatures

io.github.CloudCorpRecords由 GitHub 帳號 CloudCorpRecords 發布v0.1.0更新於 Oct 29, 2026

Protocol feature showcase: echo, math, resources, images, sampling and elicitation demos.

已驗證STDIO僅桌面開發者工具AI 與機器學習

概覽

AI 產生的概覽

一個示範型 MCP 伺服器，用來演練協定各項功能——文字、影像、資源、結構化內容、取樣、roots 與 elicitation，方便測試 MCP 用戶端。

可以做什麼
  • 回顯訊息並計算兩數之和
  • 執行依步驟拆分的長時間作業
  • 回傳 1x1 PNG 影像，以及帶有受眾與優先級的註解訊息
  • 回傳內嵌資源、資源連結與一個最小 ZIP 二進位資源
  • 為指定地點回傳固定的範例結構化內容
  • 演練用戶端功能：取樣用戶端模型、列出其 roots、向使用者提問
適用情境
適合在開發或測試 MCP 用戶端時使用，讓每項協定功能要嘛正常觸發，要嘛以清楚的錯誤失敗。它是功能展示，而非用於實際工作的工具。
執行需求
透過 npx（需 Node.js）或已發佈的 Docker 容器映像，以 stdio 在本機執行。未宣告任何帳號、API 金鑰或環境變數。
安裝前請注意
printEnv 工具會以 JSON 回傳伺服器行程的環境變數，可能暴露其中的機密資訊。取樣、roots 與 elicitation 工具會向所連線的用戶端送出請求並提示其使用者。回傳的天氣資料是固定範例，並非真實資訊。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Allfeatures，將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only，透過 STDIO。 STDIO 服務會啟動本機處理程序，因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

allfeatures

allfeatures is a showroom for the MCP protocol itself. Rather than doing one job well, it exercises the moving parts a client and server need to agree on: plain text results, images, annotations, embedded resources, resource links, structured content, a long-running call, and the three features that only work when the connected client helps out — sampling, roots and elicitation. If you are building a client, point it at allfeatures and watch each feature light up (or fail honestly, with a clear error, when your client does not offer it).

Install

bash
npx @reneturcios/allfeatures echo hello

Or run the container image:

bash
docker run -i ghcr.io/cloudcorprecords/allfeatures

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

Only the two tools that make sense without a client are exposed as commands:

bash
allfeatures echo hello there   # hello thereallfeatures add 2 3            # 5allfeatures add -1.5 0.5       # -1allfeatures --version          # 0.1.0

Exit codes: 0 on success, 1 when the arguments cannot be handled (for example, add given non-numeric input), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

bash
npx -y @reneturcios/allfeatures mcp

MCP client configuration:

json
{  "mcpServers": {    "allfeatures": {      "command": "npx",      "args": ["-y", "@reneturcios/allfeatures", "mcp"]    }  }}

Tools

ToolInputWhat it returns
echomessage (string, required)The message, unchanged, as text.
adda, b (numbers, required)The sum, as text.
longRunningOperationduration (number, optional, seconds, default 10), steps (number, optional, default 5)Waits the duration split across the steps, then a completion note.
printEnv—The server process environment as JSON text.
sampleLLMprompt (string, required), maxTokens (number, optional)A completion sampled from the client's model (see below).
getTinyImage—A 1x1 transparent PNG as image content, plus a short text note.
annotatedMessagemessageType ("error" / "success" / "debug", required), includeImage (boolean, optional)A text message whose annotations (audience and priority) depend on the type; the tiny image is attached when includeImage is true. Errors are priority 1 for user and assistant, successes are priority 0.7 for the user, debug notes are priority 0.3 for the assistant.
getResourceReferenceresourceId (number, required)An embedded text resource with URI demo://resource/<resourceId>.
getResourceLinkscount (number, required, 1–10)That many resource_link items. Counts outside 1–10 are an error.
structuredContentlocation (string, required)Fixed sample weather (72°F, Sunny, 45% humidity) for the location, as structuredContent with matching JSON text alongside.
listRoots—The client's roots, as JSON text (see below).
startElicitation—The outcome of asking the user for a short response (see below).
zip—An embedded blob resource (application/zip) holding a real, minimal ZIP archive with one stored file, hello.txt. The archive is assembled byte by byte — CRC32, local header, central directory — with no archive library.

Client-capability tools

sampleLLM, listRoots and startElicitation cannot be answered by the server alone: they ask the connected client to do something (sample its model, list its roots, prompt its user). allfeatures only sends those requests when the client advertised the matching capability during initialisation. When it did not, the tool returns an error result saying exactly that — the server never invents a plausible-looking answer.

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner over test/*.test.ts, no networknpm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

來源：README.md，提交 7ec649b

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包，因此其工具未知。

版本歷史

1
  1. v0.1.0最新Oct 29, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度，依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價，也不表示伺服器安全或目前可用：可連通性是帶日期的檢查結果，評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手；SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭，或保持端點能夠回應探測，以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list，或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分