MCP server · trust report

io.github.pendpost/pendpost

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

Publisher
io.github.pendpost
Repository
github.com/pendpost/pendpost
Install
npm:pendpost, npm:pendpost, npm:pendpost, npm:pendpost, npm:pendpost, npm:pendpost, npm:pendpost, npm:pendpost, npm:pendpost
Versions
9
Inspected
5 of 6 checks · 75%
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 checks2 clean3 flagged1 not inspected
  • Injection surface

    unscannable25% of grade

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

    No tool descriptions, server instructions, prompts, or resources were fetched; nothing to scan for injection.

  • Supply chain

    pass25% of grade

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

    repository linkage verified

  • Credential hygiene

    pass15% of grade

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

    Reads secrets from the environment (e.g. lib/api.mjs) — the recommended intake shape. PASS = no static red flag; static analysis cannot prove the code honors env-based secret handling at runtime.

  • Permission scope

    warn15% of grade

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

    has both shell/exec and network egress — capable of download-and-run, though no such path was observed (lib/api.mjs: imports child_process and calls exec/spawn; lib/cloud-client.mjs: outbound HTTP/socket call). has both shell/exec and destructive filesystem writes (lib/api.mjs: imports child_process and calls exec/spawn; lib/accounts.mjs: destructive/writing fs.* call (write/unlink/rm/chmod/rename)). discloses shell/exec capability: 13 files (lib/api.mjs, lib/assets.mjs, scripts/check-encoding.mjs, +10 more) discloses broad/destructive filesystem access: 15 files (lib/accounts.mjs, lib/covers.mjs, scripts/dashboard-build.mjs, +12 more) 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 2.1.0 (minor bump): new capability primitive(s) in source: child_process, fs-write, http-client; new hardcoded outbound host/BCC destination(s): 127.0.0.1, accounts.google.com, api.linkedin.com, api.twitter.com, balanced-giraffe-97.accounts.dev, console.cloud.google.com, developer.x.com, developers.facebook.com, example.invalid, github.com, graph-video.facebook.com, graph.facebook.com, oauth2.googleapis.com, pendpost-cloud-api.fly.dev, pendpost.com, rupload.facebook.com, studio.youtube.com, twitter.com, upload.twitter.com, www.facebook.com, www.googleapis.com, www.instagram.com, www.linkedin.com, www.youtube.com, x.com, youtu.be.

  • Transport config

    warn10% of grade

    Remote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.

    manifest/source references tracking behavior — disclosure

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
v2.2.0 · current2026-08-24 B77.55/6 · 75%±0
v2.1.02026-08-12 B1004/6 · 65%±0
v2.0.12026-07-29 B1003/6 · 55%±0
v2.0.02026-07-26 B87.55/6 · 75%±0
v1.4.02026-07-08 B87.54/6 · 65%±0
v1.2.02026-07-05 B1003/6 · 55%