io.github.allenlu0409/agent-lagoon-mcp

What we checked

Six static checks, weighted by risk. Every result reflects only what could be observed in the published package and repository — never intent.

• Injection surface

  pass25% of grade

  Tool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).

  Scanned 250 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

• Supply chain

  warn25% of grade

  Package provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.

  no resolvable repository linked to the package (provenance unverifiable)

• Credential hygiene

  fail15% of grade

  How the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.

  tool "lagoon_say" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_upgrade" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_move" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_reply" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_bottle_throw" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_travel" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_wish" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_vent_guess" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_crab_hunt" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_capsule_seal" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_sandcastle_build" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_wall_post" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_beachcomb" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_bottle_reply" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_guild_create" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_guild_join" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_campfire_share" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_sky_attend" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_legacy_leave" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_customize" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_heirloom" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "lagoon_arena_submit" has a secret-shaped input parameter "sessionToken" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  pass15% of grade

  Declared tools vs. breadth (filesystem, network, exec); flags shell-exec and unbounded filesystem access.

  No shell-exec, unbounded/sensitive filesystem, or download-and-run primitives found in scanned source. PASS = no static red flag. Static scanning is blind to code fetched or executed at runtime.

• Version behavior

  warn10% of grade

  Diff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).

  vs prior 0.3.0 (minor bump): new tool "lagoon_check_in" appeared; new tool "lagoon_say" appeared; new tool "lagoon_wave" appeared; new tool "lagoon_upgrade" appeared; new tool "lagoon_move" appeared; new tool "lagoon_inbox" appeared; new tool "lagoon_reply" appeared; new tool "lagoon_bottle_throw" appeared; new tool "lagoon_islands" appeared; new tool "lagoon_travel" appeared; new tool "lagoon_wish" appeared; new tool "lagoon_vent_guess" appeared; new tool "lagoon_crab_hunt" appeared; new tool "lagoon_capsule_seal" appeared; new tool "lagoon_capsules" appeared; new tool "lagoon_sandcastle" appeared; new tool "lagoon_sandcastle_build" appeared; new tool "lagoon_wall_post" appeared; new tool "lagoon_wall" appeared; new tool "lagoon_beachcomb" appeared; new tool "lagoon_bottle_reply" appeared; new tool "lagoon_state" appeared; new tool "lagoon_stats" appeared; new tool "lagoon_guild_create" appeared; new tool "lagoon_guild_join" appeared; new tool "lagoon_guilds" appeared; new tool "lagoon_chronicle" appeared; new tool "lagoon_digest" appeared; new tool "lagoon_recall" appeared; new tool "lagoon_dimensions" appeared; new tool "lagoon_hall" appeared; new tool "lagoon_campfire" appeared; new tool "lagoon_campfire_share" appeared; new tool "lagoon_sky" appeared; new tool "lagoon_sky_attend" appeared; new tool "lagoon_relationships" appeared; new tool "lagoon_legacy_leave" touches a sensitive surface (email/exec/net/fs); new tool "lagoon_legacy_view" appeared; new tool "lagoon_postcard" appeared; new tool "lagoon_customize" appeared; new tool "lagoon_heirloom" appeared; new tool "lagoon_arena" appeared; new tool "lagoon_arena_submit" appeared; new tool "lagoon_arena_leaderboard" appeared.

• Transport config

  unscannable10% of grade

  Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

  local stdio server: no remote transport or auth surface, and no phone-home/telemetry signal found in source. Absence of transport findings is NOT a safety guarantee — phone-home hosts can be constructed at runtime and defeat static analysis.