Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.CloudCorpRecords/allfeatures

NPM · @RENETURCIOS/ALLFEATURES · 2 COMPONENTS

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

0 this week 64 Trust /100

Last scanned (4 hours ago)

Scores higher than 31% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 460 tokens (~35/item across 13 items; 13 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Oct 26 49

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/@reneturcios/allfeatures@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 13 exposed · ~460 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add ~39

Add two numbers and return the sum as text.

NameTypeReqDescription
anumberyesFirst number to add.
bnumberyesSecond number to add.

No output schema declared.

No examples provided.

annotatedMessage ~67

Return a text message carrying annotations that vary with the requested message type, optionally with the tiny image attached.

NameTypeReqDescription
includeImageboolean–When true, attach the tiny image to the message.
messageTypestringyesKind of message to return: error, success, or debug.

No output schema declared.

No examples provided.

echo ~28

Return the supplied message unchanged as a text result.

NameTypeReqDescription
messagestringyesMessage to return unchanged.

No output schema declared.

No examples provided.

getResourceLinks ~31

Return the requested number of resource link items.

NameTypeReqDescription
countnumberyesNumber of resource links to return.

No output schema declared.

No examples provided.

getResourceReference ~36

Return an embedded text resource for the given numeric resource identifier.

NameTypeReqDescription
resourceIdnumberyesNumeric identifier of the resource to return.

No output schema declared.

No examples provided.

getTinyImage ~26

Return a tiny 1x1 transparent PNG image together with a short text note.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

listRoots ~18

Ask the connected client to list its filesystem roots.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

longRunningOperation ~57

Run a simulated long operation that waits for a duration split across a number of steps.

NameTypeReqDescription
durationnumber–Total duration of the simulated operation, in seconds.
stepsnumber–Number of steps the duration is split across.

No output schema declared.

No examples provided.

printEnv ~19

Return the server process environment as a JSON text result.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

sampleLLM ~54

Ask the connected client to sample its language model with a prompt.

NameTypeReqDescription
maxTokensnumber–Maximum number of tokens for the sampled response.
promptstringyesPrompt to send to the connected client's language model.

No output schema declared.

No examples provided.

startElicitation ~24

Ask the connected client to elicit a short response from the user.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

structuredContent ~38

Return fixed sample weather data for a location as structured content plus matching text.

NameTypeReqDescription
locationstringyesLocation the sample weather data is returned for.

No output schema declared.

No examples provided.

zip ~23

Return a small ZIP archive containing one text file, as an embedded blob resource.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.CloudCorpRecords/allfeatures MCP server?

io.github.CloudCorpRecords/allfeatures runs locally as an npm package, launched with npx -y @reneturcios/allfeatures. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @reneturcios/allfeatures

# add to Claude Code
claude mcp add cloudcorprecords-allfeatures -- npx -y @reneturcios/allfeatures
Common questions

What is the io.github.CloudCorpRecords/allfeatures MCP server?

io.github.CloudCorpRecords/allfeatures is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/allfeatures. Protocol feature showcase: echo, math, resources, images, sampling and elicitation demos. This page covers its npm package (@reneturcios/allfeatures).

Is the io.github.CloudCorpRecords/allfeatures MCP server safe to use?

io.github.CloudCorpRecords/allfeatures scores 64 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.CloudCorpRecords/allfeatures MCP server expose?

io.github.CloudCorpRecords/allfeatures exposes 13 tools: echo, add, longRunningOperation, printEnv, sampleLLM, and 8 more. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

Is the io.github.CloudCorpRecords/allfeatures MCP server still maintained?

io.github.CloudCorpRecords/allfeatures is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.CloudCorpRecords/allfeatures MCP server under?

io.github.CloudCorpRecords/allfeatures declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.