MCP server · trust report

ai.verticalmarketplace/vertical-marketplace

3 checks that ran failed — credential hygiene, version behavior and transport config — so this release can’t be trusted as-is.

Publisher
ai.verticalmarketplace
Repository
github.com/ilya7-eng/replit-vertical-market-place-website
Install
npm:vertical-marketplace-mcp
Versions
2
MCP revision
2025-06-18 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-04 · rubric 1.0.0

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.

6 checks1 clean5 flagged
  • 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 "about_marketplace" description: off-vendor URL in a description (verticalmarketplace.ai); 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 "become_seller" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "sell_data" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "buy_data" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_purchase" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "rate_listing" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "update_listing" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "deactivate_listing" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "seller_dashboard" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_health_data" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "set_delivery_endpoint" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_wallet_balance" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "fund_wallet" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "setup_payment_method" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "configure_auto_recharge" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "bulk_purchase" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "wallet_transactions" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). Reads secrets from the environment (e.g. bin/cli.js) — the recommended intake shape.

  • Permission scope

    warn15% of grade

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

    discloses shell/exec capability: bin/cli.js: imports child_process and calls exec/spawn Capability DISCLOSURE, not a verdict: static analysis sees the primitive is present and reachable, not whether its use is attacker-controlled.

  • 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): tool "become_seller" description changed (wording only, no injection pattern); tool "sell_data" description changed (wording only, no injection pattern); tool "browse_marketplace" description changed (wording only, no injection pattern); tool "buy_data" description changed (wording only, no injection pattern); new capability primitive(s) in source: child_process; new hardcoded outbound host/BCC destination(s): ..., verticalmarketplace.ai.

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

Version history

Each release plotted by grade against the safe line at B. A version that sinks below the line has lost its trusted standing — the shape of a rug-pull.

VersionPublishedGradeScoreInspectedChange
v1.0.1 · current2026-08-11 D456/6 · 100%C→D in v1.0.1
v1.0.02026-08-10 C62.54/6 · 75%