2 checks that ran failed — credential hygiene and version behavior — so this release can’t be trusted as-is.
- Publisher
- io.github.kindrat86
- Install
- npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal, npm:@gitdealflow/mcp-signal
- Versions
- 14
- MCP revision
- 2025-06-18 · superseded
- Inspected
- 6 of 6 checks · 100%
- 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.
Injection surface
warn25% of gradeTool descriptions/manifest scanned for instruction-injection patterns (imperatives at the model, hidden text, 'ignore previous', data-exfil URLs).
tool "get_deep_signal" description: off-vendor URL in a description (signals.gitdealflow.com); capability text should not name where data goes. tool "share_result" description: off-vendor URL in a description (x.com); capability text should not name where data goes. tool "share_result" param "approval_token" description: off-vendor URL in a description (signals.gitdealflow.com); capability text should not name where data goes.
Supply chain
pass25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
repository linkage verified
Credential hygiene
fail15% of gradeHow the server takes secrets (env vs plaintext config vs hardcoded); secrets appearing in tool schemas.
tool "share_result" has a secret-shaped input parameter "approval_token" — secrets must never be tool parameters (the model would supply/handle the credential).
Permission scope
pass15% of gradeDeclared 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 gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
vs prior 2.2.1 (patch bump): new hardcoded outbound host/BCC destination(s): gitdealflow.com, github.com.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
manifest/source references analytics 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.
| Version | Published | Grade | Score | Inspected | Change |
|---|---|---|---|---|---|
| v2.2.2 · current | 2026-08-21 | D | 57.5 | 6/6 · 100% | C→D in v2.2.2 |
| v2.2.1 | 2026-08-12 | C | 62.5 | 6/6 · 100% | B→C in v2.2.1 |
| v2.2.0 | 2026-05-30 | B | 100 | 3/6 · 55% | ±0 |
| v2.1.0 | 2026-05-30 | B | 95 | 4/6 · 65% | ±0 |
| v1.5.3 | 2026-05-03 | B | 95 | 4/6 · 65% | — |