MCP server · trust report

com.reqbeat/hiring-signals

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

Publisher
com.reqbeat
Repository
github.com/reqbeat/mcp-server
Install
remote only
Versions
5
MCP revision
2025-11-25 · superseded
Inspected
5 of 6 checks · 85%
Scored
2026-09-11 · 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 "find_company" description: off-vendor URL in a description (www.stripe.com); 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 "is_hiring" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_open_reqs" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "hiring_pulse" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "who_is_hiring_for" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "search_jobs" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_role" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "pre_action_brief" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "get_changes" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "find_company" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "register_webhook" has a secret-shaped input parameter "secret" — secrets must never be tool parameters (the model would supply/handle the credential). tool "register_webhook" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "watch_company" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "list_watches" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "cancel_watch" has a secret-shaped input parameter "plane_api_key" — secrets must never be tool parameters (the model would supply/handle the credential). tool "write_outcome" has a secret-shaped input parameter "plane_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

    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.1 (minor bump): tool "hiring_pulse" description changed (wording only, no injection pattern); tool "search_jobs" description changed (wording only, no injection pattern); tool "get_role" description changed (wording only, no injection pattern); tool "pre_action_brief" description changed (wording only, no injection pattern); tool "get_changes" description changed (wording only, no injection pattern); new tool "find_company" whose description contains embedded outbound URL; new tool "list_watches" touches a sensitive surface (email/exec/net/fs); new tool "cancel_watch" touches a sensitive surface (email/exec/net/fs).

  • 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.1.2 · current2026-09-10 D52.55/6 · 85%C→D in v1.1.2
v1.0.12026-09-10 C705/6 · 85%B→C in v1.0.1
v1.0.02026-07-28 B754/6 · 75%—