MCP server · trust report

io.github.razel369/intentfence

1 check that ran failed — transport config — so this release can’t be trusted as-is.

Publisher
io.github.razel369
Repository
github.com/razel369/intentfence
Install
remote only
Versions
9
Inspected
6 of 6 checks · 100%
Scored
2026-07-20 · 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 checks3 clean3 flagged
  • Injection surface

    pass25% of grade

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

    Scanned 48 text field(s); no instruction-injection patterns found. PASS = no static red flag. A server can serve different tool descriptions at runtime (the rug-pull class), which static scanning cannot see.

  • Supply chain

    warn25% of grade

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

    dependency "@x402/core" is edit-distance 1 from popular package "cors" (typosquat candidate); dependency "@x402/evm" is edit-distance 2 from popular package "ejs" (typosquat candidate); dependency "@x402/next" is edit-distance 2 from popular package "jest" (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

    warn10% of grade

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

    vs prior 0.9.0 (minor bump): new tool "intentfence_preflight" appeared; new tool "intentfence_verified_preflight" appeared; new tool "intentfence_x402_assessment" appeared; new tool "intentfence_x402_readiness" touches a sensitive surface (email/exec/net/fs); new tool "intentfence_wallet_risk" appeared; new tool "intentfence_us_cpi" appeared.

  • 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.11.0 · current2026-07-20 C72.56/6 · 100%B→C in v0.11.0
v0.9.02026-07-19 B87.53/6 · 55%±0
v0.7.12026-07-17 B87.53/6 · 55%