mcpampel@0.2.2
VERIFIED· not startedPublisher claims: "MCP security scanner plugin - scan your installed MCP servers with 16 engines" 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
MCPAMPEL_API_KEYMCPTOTAL_API_KEYConfiguration, not credentials: MCPAMPEL_BASE_URL, MCPAMPEL_TRANSPORT, MCPTOTAL_BASE_URL, MCPTOTAL_TRANSPORT- Where it talks to
- mcpampel.com (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 MCPAMPEL_API_KEY, MCPTOTAL_API_KEY and talks to mcpampel.com. 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-10 and scored it 88/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
- npx unscoped-pkg -> https://www.npmjs.com/package/pkg (backend resolves)Fix: Pin versions and sources; vendor anything fetched at install time."""npx -y @org/pkg skips the -y flag and finds the package."""Fix: Pin versions and sources; vendor anything fetched at install time.- npx @org/package -> https://github.com/org/packageFix: Pin versions and sources; vendor anything fetched at install time.entry = {"url": "https://my-mcp-server.example.com/sse"}Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# Handle npx @org/package patternFix: Pin versions and sources; vendor anything fetched at install time."""Unscoped npx packages generate npmjs.com URLs for backend resolution."""Fix: Pin versions and sources; vendor anything fetched at install time.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 mcpampel@0.2.2 as of 4d ago. This is the package itself, not its dependencies.