Parse a .env file content and return all key-value pairs with metadata.
validate_env
Validate .env content against an expected schema (list of required keys).
generate_env_template
Generate an .env.example template from a list of variable names with placeholder values.
Spec / packaging20%100
✓ depends on an MCP SDK
✓ declares a bin entry (runnable server)
✓ 3 tool(s) detected in source
Security (OWASP MCP)30%90
no high-risk patterns in sampled source
scanned 1 source file
Maintenance / popularity20%83
last published ~3mo ago
5 published versions
Tool hygiene15%95
✓ ships TypeScript types
2 runtime deps
Transparency / provenance15%90
✓ public repository linked
✓ MIT license
12 weekly downloads
Findings
INFO Static analysis of npm package env-forge-mcp@1.0.4 (stdio server — no remote endpoint). Reliability/behavioral signals require running it; not measured.
We re-grade npm:env-forge-mcp on a schedule and alert your Slack/webhook the moment its tools change or its grade drops — rug-pull insurance for the connection.
Share this report card
A 1200×630 card with the grade + audit — drop it in a post, Slack, or your repo.
A live badge — it re-verifies itself and shows current stability. Static scorecards can't. Paste it in your README or site to show users you're independently audited.
Add the wmcp.sh trust oracle as an MCP server and call grade_mcp_server / check_mcp_drift in your agent's pre-connection gate:
https://wmcp.sh/mcp/trust
How this grade is computed. An open, independent rubric — Spec conformance (20%), Security mapped to the OWASP MCP Top 10 (30%), Reliability (20%), Tool hygiene (15%), Transparency (15%) — run by connecting to the server and inspecting its real MCP surface. The grade is free and identical whether or not the operator pays. v1 uses static + spec signals from a single connection; continuous uptime, real latency, and annotation-truthing (declared readOnly vs observed behavior) layer on via the wmcp.sh proxy.