MCP server · trust report

com.alphaassay/mcp

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

Publisher
com.alphaassay
Repository
Install
remote only
Versions
6
MCP revision
2025-11-25 · superseded
Inspected
5 of 6 checks · 85%
Scored
2026-09-02 · 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 clean4 flagged1 not inspected
  • 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 "assay_signal" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_signal" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_reproduce" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_reproduce" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_tradelog" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_tradelog" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_forensics" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_forensics" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_backtest" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_backtest" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_gauntlet" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_gauntlet" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_falsify" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_falsify" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_pbo" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_pbo" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_var_es" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_var_es" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_conformal" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_conformal" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_survivors" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_survivors" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_cpcv" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_cpcv" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_batch" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_batch" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_register" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_register" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_verdict" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. tool "assay_verdict" param "api_key" description: off-vendor URL in a description (api.alphaassay.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (alphaassay.com); capability text should not name where data goes. server instructions: off-vendor URL in a description (api.alphaassay.com); 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.

    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 "assay_signal" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_reproduce" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_tradelog" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_forensics" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_backtest" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_gauntlet" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_falsify" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_pbo" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_var_es" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_conformal" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_survivors" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_cpcv" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_batch" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_register" has a secret-shaped input parameter "api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "assay_verdict" has a secret-shaped input parameter "api_key" — 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

    pass10% of grade

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

    tool surface, capabilities, install scripts, and publisher unchanged vs prior version 0.6.0 (patch bump); no rug-pull drift.

  • 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
v0.6.1 · current2026-07-22 D505/6 · 85%±0
v0.6.02026-07-09 D504/6 · 75%