Skills/npm/mcp-server-petkit

mcp-server-petkit@0.4.0

CAUTION

Publisher claims: "MCP server for the PetKit cloud API (Fresh Element Solo feeder)" Observed in sandbox: static analysis only — behavior not yet observed.

Registry npm (MCP server)Publisher dirkjanfaber · joined 0 days agoInstalls 810Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-27 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
MCP server using network transport (SSE/HTTP)dist/index.js:31 · MCP server using network transport (SSE/HTTP) — data sent over networkFix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
AST04

No other findings across 1,446 lines in 18 files.

What would make this Verified

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim dirkjanfaber: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. MCP server using network transport (SSE/HTTP)≈ +2 on the totalNamespace tool names and keep tool descriptions literal; no instructions to the agent inside them.
Publish a new version to npm, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim dirkjanfaber