MCP Risk

Directory / server

ai.autoblocks/contextlayer-mcp

This directory entry reports an automated security scan of ai.autoblocks/contextlayer-mcp, scanned 2026-07-28. Trust grade C 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

C 68/100 permalink

Automated checks

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

Claimed source repository does not exist (or is private).
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: @contextlayer/mcp@0.0.3 ↗
  • Ecosystem: npm
  • Age: 197 days
  • Weekly downloads: 45
  • Repo field matches source repo: true
  • 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
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 @contextlayer/mcp @0.0.3 (npm).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

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

Score history

DateGradeScore
2026-07-28C68/100
2026-07-27C68/100
2026-07-27C68/100
2026-07-27C68/100
2026-07-26C68/100
2026-07-26C68/100
2026-07-26C68/100
2026-07-26C77/100
2026-07-25C75/100
2026-07-25C77/100
2026-07-25A91/100
2026-07-25A91/100
2026-07-24A91/100
2026-07-24A91/100
2026-07-24A91/100
2026-07-12C77/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.