Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_SECRETS_GUARD_ROOTNoAbsolute path to the project root that the server is confined to. Defaults to the current directory.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_env_for_secretsA

Check a local env file (default: .env) for exposed secrets such as API keys, tokens, private keys and passwords. Returns only a sanitized report (line numbers, secret types, variable names). Secret values are NEVER returned, so it is safe to call. Do not try to read the env file directly.

scan_project_for_secretsA

Recursively scan the project (skipping node_modules, .git, build output and binaries) for hard-coded secrets and env files that may be committed. Returns only file paths, line numbers and secret types. Secret values are NEVER returned.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 2 tools

Disambiguation4/5

The two tools are differentiated by scope: check_env_for_secrets targets a single env file while scan_project_for_secrets recursively scans the whole project. However, the recursive scan likely also covers env files, creating partial overlap that an agent must reason about from the descriptions rather than from distinct purposes.

Naming Consistency5/5

Both tools follow a clear, consistent verb_noun_for_secrets pattern (check_env_for_secrets, scan_project_for_secrets) with matching suffix semantics. The verb difference (check vs scan) also maps sensibly to single-file vs recursive scope.

Tool Count3/5

Two tools is thin for a scanner/guard server; it sits at the borderline where the surface feels minimal. The split is defensible (file-level vs project-level), but there is little room for configuration, baselines, or reporting tools.

Completeness3/5

Detection coverage is reasonable for the domain, but the lifecycle is incomplete: there is no way to configure ignore rules/custom patterns, manage an allowlist or baseline, export reports, or receive remediation guidance. These are notable gaps for a 'guard' toolset, though agents can still perform the core detection workflow.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues