# io.github.Patrizzos/envspeak (npm · @patrizzos/envspeak)

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

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-22

## Components

- npm · `@patrizzos/envspeak`: 79/100 (this document), [markdown](https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak.md), [page](https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak)

## Channel facts

- Registry: `npm`
- Package: `@patrizzos/envspeak`
- Version: `0.1.0`
- 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-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **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 86 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 493 tokens (~98/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add patrizzos-envspeak -- npx -y @patrizzos/envspeak
```

### Cursor

```json
{
  "mcpServers": {
    "patrizzos-envspeak": {
      "command": "npx",
      "args": [
        "-y",
        "@patrizzos/envspeak"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "patrizzos-envspeak": {
      "command": "npx",
      "args": [
        "-y",
        "@patrizzos/envspeak"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add patrizzos-envspeak -- npx -y @patrizzos/envspeak
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "patrizzos-envspeak": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@patrizzos/envspeak"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add patrizzos-envspeak --command npx --arg -y --arg @patrizzos/envspeak
```

### Hermes

```yaml
mcp_servers:
  patrizzos-envspeak:
    command: "npx"
    args: ["-y", "@patrizzos/envspeak"]
```

### Netclaw

```json
{
  "McpServers": {
    "patrizzos-envspeak": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@patrizzos/envspeak"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add patrizzos-envspeak -t stdio -c npx -a -y @patrizzos/envspeak
```

### Other

```json
{
  "mcpServers": {
    "patrizzos-envspeak": {
      "command": "npx",
      "args": [
        "-y",
        "@patrizzos/envspeak"
      ]
    }
  }
}
```

## 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-12 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-11-11 (score 79, +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.

### 2026-11-10 (score 78, +6)

- [security improvement] Source repository: unverified → pass

### 2026-11-09 (score 72, −5)

- [security regression] Provenance: pass → unverified

### 2026-11-07 (score 77, +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.

### 2026-11-06 (score 76, −3)

- [functional] Stability: pass → 0.80

### 2026-10-31 (score 79, 0)

- [security] Stability: 0.97 → pass

### 2026-10-30 (score 79, 0)

- [functional] Stability: pass → 0.97

## MCP tools (5)

### `resolve_variable` (~159 tokens)

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

Input parameters:

- `container` (string): Kubernetes container name within the workload
- `environment` (string): Target NODE_ENV-style value for dotenv resolution, e.g. "production"
- `files` (array, required): Paths (relative to projectRoot) to .env*, compose, and k8s manifest files to consider
- `projectRoot` (string): Directory the file paths are relative to
- `service` (string): docker-compose service name to resolve for
- `variable` (string, required): The variable name, e.g. DATABASE_URL
- `workload` (string): Kubernetes workload (Deployment/Pod/etc.) name to resolve for

### `trace_variable` (~63 tokens)

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.

Input parameters:

- `files` (array, required)
- `projectRoot` (string)
- `variable` (string, required)

### `impact_preview` (~97 tokens)

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.

Input parameters:

- `file` (string, required): The file that would be edited
- `files` (array, required)
- `newValue` (string): Omit to simulate removing the assignment entirely
- `projectRoot` (string)
- `variable` (string, required)

### `config_manifest` (~76 tokens)

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.

Input parameters:

- `files` (array, required)
- `maxVariables` (number)
- `projectRoot` (string)

### `diff_environments` (~98 tokens)

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

Input parameters:

- `environmentA` (object, required): { nodeEnv?, service?, workload?, container?, label? }
- `environmentB` (object, required): { nodeEnv?, service?, workload?, container?, label? }
- `files` (array, required)
- `projectRoot` (string)
- `variables` (array): Optional subset; defaults to every variable discovered

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak#diagnostics

## Score history

- 2026-11-22: 79
- 2026-11-21: 79
- 2026-11-20: 79
- 2026-11-19: 79
- 2026-11-18: 79
- 2026-11-17: 79
- 2026-11-16: 79
- 2026-11-15: 79
- 2026-11-14: 79
- 2026-11-13: 79
- 2026-11-12: 79
- 2026-11-11: 79
- 2026-11-10: 78
- 2026-11-09: 72
- 2026-11-08: 77
- 2026-11-07: 77
- 2026-11-06: 76
- 2026-11-05: 79
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 79
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 79

## 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 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 22 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.

## Links

- npm package: https://www.npmjs.com/package/@patrizzos/envspeak
- Socket report: https://socket.dev/npm/package/@patrizzos/envspeak
- Repository: https://github.com/patrizzos/envspeak
- Changelog RSS feed: https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak.xml
- Changelog JSON feed: https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak.json
- HTML version of this page: https://verifymcp.io/servers/patrizzos-envspeak/patrizzos-envspeak
