Allfeatures

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Oct 29, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsAI & ML

Overview

AI-generated overview

A demo MCP server that exercises protocol features — text, images, resources, structured content, sampling, roots and elicitation — for testing MCP clients.

What you can do
  • Echo a message and add two numbers
  • Run a long-running operation split into steps
  • Return a tiny PNG image and annotated messages with audience and priority
  • Return embedded resources, resource links and a minimal ZIP blob
  • Return fixed sample structured content for a location
  • Exercise client-side features: sample the client's model, list its roots, and ask the user a question
When to use it
Useful when building or testing an MCP client and you want each protocol feature to light up or fail with a clear error. It is a showroom rather than a tool for real work.
Requirements
Runs locally over stdio via npx (Node.js) or the published container image with Docker. No accounts, API keys or environment variables are declared.
Before you install
The printEnv tool returns the server process environment as JSON, which may expose secrets present in that environment. The sampling, roots and elicitation tools send requests to the connected client and prompt its user. The weather data returned is fixed sample data, not real information.

Installation

In SourceWeft

  1. Open Allfeatures in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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.

Source: README.md at commit 7ec649b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestOct 29, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts