MCP server · trust report

com.theaslangroupllc.pulse/pulsenetwork

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

Publisher
com.theaslangroupllc.pulse
Repository
github.com/GTCC777/mcp-pulsenetwork
Install
remote only
Versions
4
MCP revision
2025-11-25 · superseded
Inspected
6 of 6 checks · 100%
Scored
2026-09-01 · 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 checks2 clean4 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 3898 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.

    install hook "prepare" present and not a recognized benign build command; 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 "viem" is edit-distance 2 from top-20 package "vue" (typosquat candidate)

  • Credential hygiene

    fail15% of grade

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

    tool "airdroppulse" has a secret-shaped input parameter "token_id" — secrets must never be tool parameters (the model would supply/handle the credential).

  • 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.3.0 (minor bump): tool "signalpulse" description changed (wording only, no injection pattern); tool "airdroppulse" description changed (wording only, no injection pattern); tool "airdroppulse" gained input property(ies): category; tool "onchainpulse" description changed (wording only, no injection pattern); tool "onchainpulse" gained input property(ies): limit, tx, perspective; tool "discover" description changed (wording only, no injection pattern); new tool "catalog_search" touches a sensitive surface (email/exec/net/fs); new tool "get_openapi_spec" touches a sensitive surface (email/exec/net/fs); new tool "x402_troubleshoot" appeared; new hardcoded outbound host/BCC destination(s): github.com, pulse.theaslangroupllc.com.

  • 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.4.0 · current2026-07-29 D52.56/6 · 100%C→D in v1.4.0
v1.3.02026-07-27 C62.55/6 · 90%±0
v1.2.02026-07-06 C62.55/6 · 90%