mseep-aws-security-mcp@0.1.1
VERIFIED· not startedPublisher claims: "AWS Security MCP - A comprehensive AWS security inspection and remediation tool" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
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
AWS_ACCESS_KEY_IDAWS_CONTAINER_CREDENTIALS_RELATIVE_URIAWS_SECRET_ACCESS_KEYAWS_SESSION_TOKENConfiguration, not credentials: AWS_DEFAULT_REGION, AWS_EXECUTION_ENV, AWS_PROFILE, AWS_REGION, ECS_CONTAINER_METADATA_URI, ECS_CONTAINER_METADATA_URI_V4, MCP_ATHENA_CATALOG, MCP_ATHENA_OUTPUT_LOCATION, MCP_ATHENA_WORKGROUP, MCP_AUTO_REFRESH_ENABLED, MCP_AUTO_SETUP_SESSIONS, MCP_CLIENT_CACHE_TTL, MCP_CONNECTION_POOL_SIZE, MCP_CROSS_ACCOUNT_ROLE_NAME, MCP_CROSS_ACCOUNT_SESSION_NAME, MCP_DEBUG, MCP_HOST, MCP_LOG_LEVEL, MCP_MAX_CONCURRENT_ASSUMPTIONS, MCP_MAX_CONCURRENT_REQUESTS, MCP_MINIMAL_LOGGING, MCP_PORT, MCP_PROGRESS_UPDATE_INTERVAL, MCP_REFRESH_THRESHOLD_MINUTES, MCP_RETRY_BACKOFF_FACTOR, MCP_RETRY_MAX_ATTEMPTS, MCP_SESSION_DURATION_SECONDS, MCP_STARTUP_QUIET, MCP_TOOL_QUIET- Where it talks to
- no vendor host named in the code
- 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 AWS_ACCESS_KEY_ID, AWS_CONTAINER_CREDENTIALS_RELATIVE_URI, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN and talks to its vendor. 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.
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-12 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 deviationsStatic findings
"AWS credentials source: Auto-resolution (environment variables, ~/.aws/credentials, ECS task role, or instance profile)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# Load environment variables from .env file if presentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."AWS credentials source: Auto-resolution (environment variables, ~/.aws/credentials, ECS task role, or instance profile)"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
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 mseep-aws-security-mcp@0.1.1 as of 2d ago. This is the package itself, not its dependencies.