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.Patrizzos/envspeak

NPM · @PATRIZZOS/ENVSPEAK

MCP server and CLI that resolves config/env-var cascade across .env, docker-compose, and Kubernetes

Available components

−2 this week 77 Trust /100

Last scanned (1 hour ago)

Scores higher than 55% 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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 493 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage84
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 52% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

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.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 6 Nov 26 −3
    • Stability: pass → 0.80 functional
  • 31 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Oct 26 0
    • Stability: pass → 0.97 functional
  • 24 Oct 26 0
    • Stability: 0.97 → pass security
  • 23 Oct 26 0
    • Stability: pass → 0.97 functional
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
  • 16 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

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 8 Nov 2026 · Analysed npm/@patrizzos/envspeak@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 →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~493 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
config_manifest ~76

Compressed, project-wide summary of every config variable found — sources, domains, and risk hotspots (likely secrets in tracked files, variables read in code with no source). Load once per session instead of repeated resolve_variable calls.

NameTypeReqDescription
filesarrayyes–
maxVariablesnumber––
projectRootstring––

No output schema declared.

No examples provided.

diff_environments ~98

Resolves every variable under two different environment/service/workload selectors and reports what differs between them.

NameTypeReqDescription
environmentAobjectyes{ nodeEnv?, service?, workload?, container?, label? }
environmentBobjectyes{ nodeEnv?, service?, workload?, container?, label? }
filesarrayyes–
projectRootstring––
variablesarray–Optional subset; defaults to every variable discovered

No output schema declared.

No examples provided.

impact_preview ~97

Predicts which environments/services/workloads are actually affected if a variable's value in one file is changed (or removed) — including which contexts are shielded by a higher-precedence source.

NameTypeReqDescription
filestringyesThe file that would be edited
filesarrayyes–
newValuestring–Omit to simulate removing the assignment entirely
projectRootstring––
variablestringyes–

No output schema declared.

No examples provided.

resolve_variable ~159

Resolves what a config/env variable actually evaluates to across dotenv, docker-compose, and Kubernetes sources, and which source wins.

NameTypeReqDescription
containerstring–Kubernetes container name within the workload
environmentstring–Target NODE_ENV-style value for dotenv resolution, e.g. "production"
filesarrayyesPaths (relative to projectRoot) to .env*, compose, and k8s manifest files to consider
projectRootstring–Directory the file paths are relative to
servicestring–docker-compose service name to resolve for
variablestringyesThe variable name, e.g. DATABASE_URL
workloadstring–Kubernetes workload (Deployment/Pod/etc.) name to resolve for

No output schema declared.

No examples provided.

trace_variable ~63

Lists every place a variable is defined or read across dotenv, compose, k8s, and code, and what wins in each discovered environment/service/workload context.

NameTypeReqDescription
filesarrayyes–
projectRootstring––
variablestringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.Patrizzos/envspeak MCP server?

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

npm · @patrizzos/envspeak

# add to Claude Code
claude mcp add patrizzos-envspeak -- npx -y @patrizzos/envspeak
Common questions

What is the io.github.Patrizzos/envspeak MCP server?

io.github.Patrizzos/envspeak is an MCP server listed in the public MCP registry as io.github.Patrizzos/envspeak. MCP server and CLI that resolves config/env-var cascade across .env, docker-compose, and Kubernetes. This page covers its npm package (@patrizzos/envspeak).

Is the io.github.Patrizzos/envspeak MCP server safe to use?

io.github.Patrizzos/envspeak scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 8 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.Patrizzos/envspeak MCP server expose?

io.github.Patrizzos/envspeak exposes 5 tools: resolve_variable, trace_variable, impact_preview, config_manifest, diff_environments. Their descriptions and schemas cost roughly 493 tokens of context every time the server is loaded.

Is the io.github.Patrizzos/envspeak MCP server still maintained?

io.github.Patrizzos/envspeak is still listed as active in the MCP registry. We last reached this channel on 8 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.Patrizzos/envspeak MCP server under?

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

What did VerifyMCP test on the io.github.Patrizzos/envspeak MCP server?

VerifyMCP ran 16 checks on io.github.Patrizzos/envspeak, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.