Skills/PyPI/mcpshield

mcpshield@0.3.3

VERIFIED· not started

Publisher claims: "MCPShield - Secure infrastructure access for AI agents (databases, APIs, cloud) with deterministic policy enforcement and AI-powered policy generation" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher mcpshield-support · publishing for 277 daysInstalls 25Last detonated 3d ago
$claude mcp add mcpshield -- uvx mcpshield
WatchReport an issue

Coverage

Not started: dependency install failed; the server itself was not observed.
Tested
the dependency install step · every file read, file written and host contacted by what ran
Not tested
server startup · the tool list · tool behavior

What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.

Before you give it your token

It will ask for
DATABASE_URLDSNMCPSHIELD_API_KEYPG_DSNConfiguration, not credentials: API_BASE_URL, BACKEND, BATCH_SIZE, BATCH_TIMEOUT, INFRASTRUCTURE_TYPES, LOG_DECISIONS, MCPSHIELD_BACKEND, POLICY_CACHE_DIR, POLICY_FILE, POLICY_REFRESH_SECONDS, POLICY_SOURCE, PROJECT_ID, SPOOL_DIR
Where it talks to
mcpshield.xyz (its own)
What the honeypot saw
no credential files read · no network
What we could not test
server startup · the tool list · tool behavior

Connect it with a scoped credential, under the guard. It asks for DATABASE_URL, DSN, MCPSHIELD_API_KEY, PG_DSN and talks to mcpshield.xyz. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.

$vet-skills run --secrets DATABASE_URL=mcpshield.xyz,DSN=mcpshield.xyz,MCPSHIELD_API_KEY=mcpshield.xyz,PG_DSN=mcpshield.xyz -- uvx mcpshield

Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-11 and scored it 86/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.1sprocessdependency install exit 1 ·
0.1sclaimednot started: dependency install failed (exit 1); the server itself was not observed
0.1sprocessscript backend runs setup only
0.1sprocessno install scripts to re-run

Static findings

HIGH
Access to sensitive file pathssrc/mcpshield_gateway/config.py:144 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file: Optional path to .env file to load firstFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/config.py:282 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_file: Optional path to .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/config.py:164 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Load .env file if providedFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspyproject.toml:69 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files".env*",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathspyproject.toml:70 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files"*.env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/cli.py:185 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesbackup_path = env_path.parent / f".env.backup.{int(Path.home().stat().st_mtime)}"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/cli.py:343 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesprint(" 4. Manual setup (just create .env file)")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/cli.py:346 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system files# Create .env fileFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/cli.py:169 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_path = Path.home() / ".mcpshield" / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/cli.py:347 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesenv_path = Path.home() / ".mcpshield" / ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/config.py:304 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesraise FileNotFoundError(f".env file not found: {env_path}")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05
HIGH
Access to sensitive file pathssrc/mcpshield_gateway/config.py:297 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesLoad environment variables from .env file.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

Cost to the agent

Instructions loaded
≈72 tok
1 file · 30 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.

Known vulnerabilities

No advisories in OSV for mcpshield@0.3.3 as of 3d ago. This is the package itself, not its dependencies.

mcpshield@0.3.3 safety verdict: Verified (not started) — KillerSkills