EnvMem (samihalawa/envmem-mcp) is an MCP server listed on the M8ven Trust Index. It scores 58 out of 100, grade D. It declares 15 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
D
Caution
58/100

EnvMem

Personal environment variable memory with semantic search and project management. Enables storing, searching, and retrieving environment variables via MCP, supporting project organization and auto-fill of .env files.

→ samihalawa/envmem-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

samihalawa

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 4 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 1 credential: ENVMEM_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes15 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

search_env_variables

Search environment variables using natural language. Example: "browser automation" returns Browserbase, E2B, Playwright variables.

get_env_by_name

Get environment variable details by exact name

list_env_categories

List all available environment variable categories with counts

get_envs_for_services

Get all environment variables needed for multiple services. Use when setting up .env file for a project.

import_env_variables

Import environment variables from .env format text. Parses NAME=value pairs with optional # comments for descriptions. Use this to populate YOUR personal env reference database.

add_env_variable

Add a single environment variable to your reference database

delete_env_variable

Delete an environment variable from your reference database by name

clear_all_env_variables

Delete ALL environment variables from the database. Use with caution!

create_project

Create a project to organize environment variables. Projects can be linked to repos and tagged.

list_projects

List all your projects

link_env_to_project

Link an environment variable to a project. Optionally specify environment (dev/staging/prod) and override value.

link_services_to_project

Bulk link all envs from multiple services to a project. Use when setting up a new project that uses Stripe, Supabase, etc.

get_envs_for_project

Get all environment variables for a project, optionally filtered by environment. Returns ready-to-use .env content.

fill_env_example

Parse a .env.example file and fill it with your stored values. Auto-links matched envs to the project.

delete_project

Delete a project and all its env links (does NOT delete the env variables themselves)

// known CVEs in dependencies4 high

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@modelcontextprotocol/sdk@1.20.0GHSA-345p-7cg4-v4c7

@modelcontextprotocol/sdk has cross-client data leak via shared server/transport instance reuse

high@modelcontextprotocol/sdk@1.20.0GHSA-8r9q-7v3j-jr4g

Anthropic's MCP TypeScript SDK has a ReDoS vulnerability

high@modelcontextprotocol/sdk@1.20.0GHSA-w48q-cv73-mx4w

Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default

highwrangler@3.94.0GHSA-36p8-mvp6-cv38

Wrangler affected by OS Command Injection in `wrangler pages deploy`

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretENVMEM_API_KEY"": "your-secret-api-key"
configENVMEM_URL
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

15/15 tools missing one or more hints — search_env_variables (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_env_by_name (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_env_categories (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tests exist

No test files found

Add tests that exercise each declared tool.

Secrets not logged

1 secret value sent to console.log

Redact or omit secret values from log output.

Production dependencies are patched

0 critical, 3 high severity in production deps — @modelcontextprotocol/sdk@1.20.0 (high), @modelcontextprotocol/sdk@1.20.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Dev dependencies

1 critical/high in dev-only deps (does not ship to users)

Upgrade dev dependencies when convenient.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/samihalawa/envmem-mcp?variant=verified)](https://m8ven.ai/mcp/samihalawa/envmem-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 59483599dc3730651d1530ff7d6c3317e2e8ca5e
code hash: e9ef3fe54a8511d421251d3e1eda477f49c8ea4986dbb9ad117e1cc41cf4654f
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client