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 分