MCP Risk

Directory / server

app.3dstreet/3dstreet

This directory entry reports an automated security scan of app.3dstreet/3dstreet, 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 89/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as app.3dstreet/3dstreet. 1 finding
  • Registry entry: app.3dstreet/3dstreet
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository
  • Last push: 81 days ago
  • Stars: 0
  • License: AGPL-3.0
  • Security policy (SECURITY.md): absent
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: 3dstreet-mcp@0.2.2
  • Ecosystem: npm
  • Age: 85 days
  • Weekly downloads: 83
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: filesystem. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 3 findings
  • filesystem (filesystem write/delete): src/cli.js
  • filesystem (fs module import): src/cli.js
  • Detected capabilities: filesystem
INFO Transport & authentication §3

Local (stdio) server: runs with host-process privileges by design. Transport checks apply to remote servers; scrutiny shifts to §1/§2.

PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for 3dstreet-mcp @0.2.2 (npm).

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

No server-supplied instructions or tool descriptions were obtainable to scan.

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.