MCP Risk

Directory / server

com.b20check/b20check

This directory entry reports an automated security scan of com.b20check/b20check, 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 remote-tools-list

C 79/100 permalink

Automated checks

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

No public source repository could be identified for this server.
WARN Published package is consistent and attested §1.3
Minor integrity gaps: package is only 15 days old; no npm provenance attestation. 6 findings
  • Package: b20check-mcp@0.1.1 ↗
  • Ecosystem: npm
  • Age: 15 days
  • Weekly downloads: 50
  • Repo field matches source repo: n/a
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
2 tool(s) enumerated; no high-risk capability signals. 2 findings
  • Tools exposed: 2
  • Detected capabilities: none
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://b20check.com/mcp
WARN Authentication required §3.2

Server answers anonymous requests (HTTP 200). Acceptable only for deliberately public, read-only (Low) servers.
WARN OAuth protected-resource metadata published §3.3
No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding
  • Checked: https://b20check.com/.well-known/oauth-protected-resource
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for b20check-mcp @0.1.1 (npm).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 4 server-supplied text item(s).
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.