MCP/Risk

Directory / server

com.blackswancausallabs/target-mcp

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

This directory entry reports an automated security scan of com.blackswancausallabs/target-mcp, scanned 2026-09-11. Trust grade B 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.blackswancausallabs/target-mcp. 1 finding
  • Registry entry: com.blackswancausallabs/target-mcp ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 19 days ago
  • Stars: 0
  • License: Apache-2.0
  • 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 PyPI trusted-publishing provenance. 5 findings
  • Package: target-mcp@0.2.0 ↗
  • Ecosystem: PyPI
  • Age: 51 days
  • Repo field matches source repo: false
  • Trusted-publishing provenance: 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
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 target-mcp @0.2.0 (PyPI).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

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

Score history

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