MCP/Risk

Directory / server

com.attrove/mcp

registry.modelcontextprotocol.io, scanned 2026-09-11, tool surface via package-source

This directory entry reports an automated security scan of com.attrove/mcp, scanned 2026-09-11. Trust grade C rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as com.attrove/mcp. 1 finding
  • Registry entry: com.attrove/mcp
FAIL Source repository is public and maintained §1.2

Claimed source repository does not exist (or is private).

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: @attrove/mcp@0.6.0
  • Ecosystem: npm
  • Age: 231 days
  • Weekly downloads: 137
  • Repo field matches source repo: false
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: filesystem, network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 9 findings
  • filesystem (filesystem write/delete): cjs/lib/global-auth.js
  • filesystem (fs module import): cjs/lib/global-auth.js
  • filesystem (filesystem write/delete): esm/lib/global-auth.js
  • filesystem (fs module import): esm/lib/global-auth.js
  • filesystem (fs module import): cjs/version.js
  • filesystem (fs module import): esm/version.js
  • network-egress (outbound network calls): esm/transport/http.d.ts
  • network-egress (http module import): esm/transport/http.d.ts
  • Detected capabilities: filesystem, network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://api.attrove.com/mcp
UNVERIFIABLE Authentication required §3.2

Endpoint unreachable: The operation was aborted

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://zbrqriqpalplqtiqhkfs.supabase.co/auth/v1
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @attrove/mcp @0.6.0 (npm).

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

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

Score history

DateGradeScore
2026-09-11C72/100
2026-07-28B82/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.