Skills/npm/good-eggs-mcp-server

good-eggs-mcp-server@0.1.11

VERIFIED· startup only

Publisher claims: "MCP server for Good Eggs grocery shopping automation using Playwright." Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry npm (MCP server) · listed in the official MCP RegistryPublisher pulsemcp · publishing for 506 daysInstalls 0Last detonated 19 h ago
$claude mcp add good-eggs-mcp-server -- npx -y good-eggs-mcp-server
WatchReport an issue

Coverage

Startup only; authenticated tool behavior not tested.
Tested
server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
Not tested
the tool list (the server exited before answering) · what the tools do when called with real credentials
Needs
GOOD_EGGS_PASSWORD — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.

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
GOOD_EGGS_PASSWORDConfiguration, not credentials: GOOD_EGGS_USERNAME, HEADLESS, TIMEOUT
Where it talks to
goodeggs.com (its own)
What the honeypot saw
no credential files read · no network
What we could not test
the tool list (the server exited before answering) · what the tools do when called with real credentials

Connect it with a scoped credential, under the guard. It asks for GOOD_EGGS_PASSWORD and talks to goodeggs.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.

$vet-skills run --secrets GOOD_EGGS_PASSWORD=goodeggs.com -- npx -y good-eggs-mcp-server

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; startup only; authenticated tool behavior not tested) on 2026-11-13 and scored it 95/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 (it asks for GOOD_EGGS_PASSWORD); 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 · 50 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
9.3sprocessdependency install exit 0
29sprocessrelaunched with a decoy GOOD_EGGS_PASSWORD (tagged; nothing real)
49sclaimedstartup only: exited before answering, asking for GOOD_EGGS_PASSWORD (a decoy value was refused)
49sprocessscript backend runs setup only
49sprocessno install scripts to re-run

Static findings

No findings across 2,752 lines in 15 files.

Cost to the agent

Instructions loaded
≈57 tok
1 file · 15 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 good-eggs-mcp-server@0.1.11 as of 18 h ago. This is the package itself, not its dependencies.