io.github.getgapup/mcp-knowledge

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

  fail25% of grade

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

  tool "webhooks_manage" description: names an outbound copy/exfil destination (BCC/exfil verb). tool "usdc_x402_payments_intel" param "endpoint_url" description: off-vendor URL in a description (mcp.gapup.io); capability text should not name where data goes. tool "transcribe_chapterize_media" param "url" description: off-vendor URL in a description (www.youtube.com); capability text should not name where data goes. tool "seo_cro_audit" param "url" description: off-vendor URL in a description (stripe.com); capability text should not name where data goes. tool "competitor_pricing_scrape" param "url" description: off-vendor URL in a description (notion.so); capability text should not name where data goes. tool "competitor_pricing_scrape" param "url" description: off-vendor URL in a description (www.example.com); capability text should not name where data goes.

• Supply chain

  pass25% of grade

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

  repository linkage verified

• Credential hygiene

  fail15% of grade

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

  tool "mttr_breakdown_analyzer" has a secret-shaped input parameter "githubToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "mttr_breakdown_analyzer" has a secret-shaped input parameter "snykToken" — secrets must never be tool parameters (the model would supply/handle the credential). tool "crm_connector" has a secret-shaped input parameter "credentials" — secrets must never be tool parameters (the model would supply/handle the credential). tool "webhooks_manage" has a secret-shaped input parameter "secret" — secrets must never be tool parameters (the model would supply/handle the credential).

• Permission scope

  unscannable15% of grade

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

  No source files, package.json, or pyproject were fetched; cannot infer capability scope.

• Version behavior

  unscannable10% of grade

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

  no prior version to diff (first sight of io.github.getgapup/[email protected]); version-drift / rug-pull cannot be evaluated. Cold-start risk is covered by point-in-time checks (injection_surface, supply_chain, credential_hygiene), not here.

• 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)