MCP Risk

Directory / server

ai.meetsquad/squad

This directory entry reports an automated security scan of ai.meetsquad/squad, scanned 2026-07-28. Trust grade B rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

B 82/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as ai.meetsquad/squad. 1 finding
  • Registry entry: ai.meetsquad/squad
WARN Source repository is public and maintained §1.2
Repository health issues: no license. 5 findings
  • Repository
  • Last push: 1 days ago
  • Stars: 2
  • License: none detected
  • Security policy (SECURITY.md): absent
FAIL Published package is consistent and attested §1.3
Integrity concerns: package repository field does not match the claimed source repo; no npm provenance attestation. 6 findings
  • Package: @squadai/tools@2.3.0
  • Ecosystem: npm
  • Age: 455 days
  • Weekly downloads: 24
  • Repo field matches source repo: false
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned; no high-risk capability signals. 1 finding
  • Detected capabilities: none
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://mcp.meetsquad.ai/mcp
PASS Authentication required §3.2
Server rejects anonymous requests and advertises its auth scheme. 1 finding
  • WWW-Authenticate: Bearer error="unauthorized", error_description="Authorization needed", resource_metadata="https://mcp.meetsquad.ai/.well-known/oauth-protected-resource"
PASS OAuth protected-resource metadata published §3.3
Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec. 1 finding
  • Authorization server: https://auth.meetsquad.ai/oauth/2.1
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @squadai/tools @2.3.0 (npm).

PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 4 server-supplied text item(s).

Score history

DateGradeScore
2026-07-28B82/100
2026-07-26C73/100
2026-07-25C72/100
2026-07-13C71/100
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.