MCP server · trust report
ai.meetsquad/squad
Passes 3 checks with a soft flag on supply chain and transport config — worth a look, not a dealbreaker.
- Publisher
- ai.meetsquad
- Repository
- github.com/the-basilisk-ai/squad-mcp
- Install
- remote only
- Versions
- 10
- Inspected
- 5 of 6 checks · 75%
- Scored
- 2026-09-03 · 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
unscannable25% of gradeTool 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
warn25% of gradePackage provenance: namespace verification, repo linkage, maintainer count, account age, postinstall scripts, typosquat distance.
dependency "@graphql-typed-document-node/core" is edit-distance 1 from popular package "cors" (typosquat candidate); dependency "@posthog/mcp" is edit-distance 2 from popular package "yup" (typosquat candidate); dependency "@propelauth/node" is edit-distance 2 from popular package "@babel/core" (typosquat candidate)
Credential hygiene
pass15% of gradeHow 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 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
pass10% of gradeDiff of tool definitions between versions; new permissions or changed descriptions in a patch release (the postmark-mcp class).
tool surface, capabilities, install scripts, and publisher unchanged vs prior version 4.1.3 (patch bump); no rug-pull drift.
Transport config
warn10% of gradeRemote servers: TLS and auth mode (none/token/OAuth). Local servers: whether the manifest indicates it phones home.
sends telemetry to third-party SDK (posthog) — disclosure, verify opt-in
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 |
|---|---|---|---|---|---|
| v4.1.4 · current | 2026-09-02 | B | 82.5 | 5/6 · 75% | ±0 |
| v4.1.3 | 2026-09-01 | B | 87.5 | 5/6 · 75% | ±0 |
| v4.1.1 | 2026-08-17 | B | 82.5 | 5/6 · 75% | ±0 |
| v4.1.0 | 2026-08-07 | B | 82.5 | 4/6 · 65% | ±0 |
| v4.0.2 | 2026-08-04 | B | 82.5 | 5/6 · 75% | ±0 |
| v4.0.0 | 2026-07-14 | B | 82.5 | 4/6 · 65% | — |