# io.github.CloudCorpRecords/mcpvet (oci · ghcr.io/cloudcorprecords/mcpvet) Vetting for MCP servers and skills: capabilities, configs, mismatches, typosquats, probe parity. - Trust score: 48/100 (low) - Change this week: +3 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - npm · `@reneturcios/mcpvet`: 72/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-mcpvet/reneturcios-mcpvet.md), [page](https://verifymcp.io/servers/cloudcorprecords-mcpvet/reneturcios-mcpvet) - oci · `ghcr.io/cloudcorprecords/mcpvet`: 48/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-mcpvet/ghcr-io-cloudcorprecords-mcpvet.md), [page](https://verifymcp.io/servers/cloudcorprecords-mcpvet/ghcr-io-cloudcorprecords-mcpvet) ## Channel facts - Registry: `oci` - Package: `ghcr.io/cloudcorprecords/mcpvet` - Version: `0.2.1` - Transport: `stdio` ## Trust breakdown 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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 0/100 - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package. - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - Install-script risk not yet assessed. - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 9 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 80/100 - AI-judged instruction clarity (excellent). - Context-footprint check failed: tool/resource definitions use about 412 tokens (~137/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 47/100 - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation. - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. **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. ## Install ### How do I install the io.github.CloudCorpRecords/mcpvet MCP server? io.github.CloudCorpRecords/mcpvet runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/mcpvet:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add cloudcorprecords-mcpvet -- docker run --rm -i ghcr.io/cloudcorprecords/mcpvet:0.2.1 ``` ### Cursor ```json { "mcpServers": { "cloudcorprecords-mcpvet": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/mcpvet:0.2.1" ] } } } ``` ### VS Code ```json { "servers": { "cloudcorprecords-mcpvet": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/mcpvet:0.2.1" ] } } } ``` ### Codex ```bash codex mcp add cloudcorprecords-mcpvet -- docker run --rm -i ghcr.io/cloudcorprecords/mcpvet:0.2.1 ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "cloudcorprecords-mcpvet": { "type": "local", "command": [ "docker", "run", "--rm", "-i", "ghcr.io/cloudcorprecords/mcpvet:0.2.1" ], "enabled": true } } } ``` ### Hermes ```yaml mcp_servers: cloudcorprecords-mcpvet: command: "docker" args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/mcpvet:0.2.1"] ``` ### Netclaw ```json { "McpServers": { "cloudcorprecords-mcpvet": { "Transport": "stdio", "Command": "docker", "Arguments": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/mcpvet:0.2.1" ] } } } ``` ### Other ```json { "mcpServers": { "cloudcorprecords-mcpvet": { "command": "docker", "args": [ "run", "--rm", "-i", "ghcr.io/cloudcorprecords/mcpvet:0.2.1" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 48, +1) No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-02 (score 47, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-31 (score 46, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-29 (score 45, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-27 (score 44, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-26 (score 43, 0) - [security regression] Stability: 0.10 → unverified - [security regression] Tool safety: pass → unverified - [functional regression] Capabilities: pass → unverified - [functional regression] Tool coverage: 100 → unverified - [functional] First check of Schema quality: unverified - [functional] Package version: 0.2.0 → 0.2.1 ### 2026-10-25 (score 43, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-24 (score 42, 0) - [functional regression] Schema quality: pass → fail - [functional] Package version: 0.1.4 → 0.2.0 ## MCP tools (3) ### `vet_path` (~127 tokens) Vet a local MCP server directory, SKILL.md skill directory, or client config tree before install. Inventories declared and actual tools, flags dangerous capability combinations, audits autostart configs and bundled scripts, checks declared vs actual mismatches, version pinning, and typosquat distance. Static only: scanned code is never executed. Returns a VETTED, REVIEW, or DO-NOT-INSTALL verdict with evidence per finding. Input parameters: - `path` (string, required): Local directory to vet: an MCP server dir, a skill dir with SKILL.md, or a tree containing client MCP configs ### `vet_package` (~106 tokens) Vet an npm package by name before install, using registry metadata only (the tarball is not downloaded and no code runs): typosquat distance against well-known MCP server names, install scripts, description language, and version pinning. Returns a VETTED, REVIEW, or DO-NOT-INSTALL verdict with evidence. Input parameters: - `name` (string, required): npm package name, optionally with @version, e.g. @modelcontextprotocol/server-filesystem@2025.3.28 ### `probe_server` (~179 tokens) Live-probe a stdio MCP server command: spawns it twice, runs initialize plus tools/list both times, and diffs the answers (probe parity), matches the presented tool set and descriptions against exact-hash fingerprints, and derives a server-level risk score from the recorded signals. WARNING: unlike vet_path and vet_package, this EXECUTES the given command on this machine, twice. Live evidence never yields DO-NOT-INSTALL; the harshest live verdict is REVIEW. A probe refused for auth reasons is recorded as a pass; a timeout records no signal. Input parameters: - `args` (array): Arguments for the command, e.g. the server script path - `command` (string, required): Server executable to spawn, e.g. node or npx - `timeoutMs` (integer): Per-probe timeout in milliseconds (default 15000) ## Diagnostics Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-mcpvet/ghcr-io-cloudcorprecords-mcpvet#diagnostics ## Score history - 2026-11-05: 48 - 2026-11-04: 47 - 2026-11-03: 47 - 2026-11-02: 47 - 2026-11-01: 46 - 2026-10-31: 46 - 2026-10-30: 45 - 2026-10-29: 45 - 2026-10-28: 44 - 2026-10-27: 44 - 2026-10-26: 43 - 2026-10-25: 43 - 2026-10-24: 42 - 2026-10-23: 42 - 2026-10-22: 42 ## Common questions ### What is the io.github.CloudCorpRecords/mcpvet MCP server? io.github.CloudCorpRecords/mcpvet is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/mcpvet. Vetting for MCP servers and skills: capabilities, configs, mismatches, typosquats, probe parity. This page covers its container image (ghcr.io/cloudcorprecords/mcpvet). ### Is the io.github.CloudCorpRecords/mcpvet MCP server safe to use? io.github.CloudCorpRecords/mcpvet scores 48 out of 100 on VerifyMCP. 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/mcpvet MCP server expose? io.github.CloudCorpRecords/mcpvet exposes 3 tools: vet_path, vet_package, probe_server. Their descriptions and schemas cost roughly 412 tokens of context every time the server is loaded. ### Is the io.github.CloudCorpRecords/mcpvet MCP server still maintained? io.github.CloudCorpRecords/mcpvet 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/mcpvet MCP server under? io.github.CloudCorpRecords/mcpvet declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - GitHub Container Registry: https://ghcr.io/cloudcorprecords/mcpvet - Repository: https://github.com/CloudCorpRecords/mcpvet - Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-mcpvet/ghcr-io-cloudcorprecords-mcpvet.xml - Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-mcpvet/ghcr-io-cloudcorprecords-mcpvet.json - HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-mcpvet/ghcr-io-cloudcorprecords-mcpvet