io.github.kanylbullen/xupersplit

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

  warn25% of grade

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

  tool "get_split" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "add_expense" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "record_payment" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "update_entry" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "delete_entry" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "add_participant" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "rename_participant" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "remove_participant" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "set_payment_methods" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes. tool "update_split" param "split" description: off-vendor URL in a description (split.xuper.fun); capability text should not name where data goes.

• Supply chain

  warn25% of grade

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

  dependency "@modelcontextprotocol/server" is edit-distance 1 from popular package "semver" (typosquat candidate); dependency "@supabase/ssr" is edit-distance 2 from popular package "ws" (typosquat candidate); dependency "uqr" is edit-distance 2 from popular package "qs" (typosquat candidate); dependency "viem" is edit-distance 2 from top-20 package "vue" (typosquat candidate)

• Credential hygiene

  pass15% of grade

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

  No hardcoded secrets, secret-shaped tool parameters, or leaked keys found. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

• 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

  fail10% of grade

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

  vs prior 1.0.0 (patch bump): new hardcoded outbound host/BCC destination(s): split.xuper.fun, your-project.supabase.co.

• Transport config

  fail10% of grade

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

  remote MCP endpoint declares NO authentication (unauthenticated remote — nginx-ui/CVE-2026-33032 class); manifest/source references analytics behavior — disclosure