MCP Risk

Directory / server

com.ambermem/amber

This directory entry reports an automated security scan of com.ambermem/amber, 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 none

B 100/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as com.ambermem/amber. 1 finding
  • Registry entry: com.ambermem/amber ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 42 days ago
  • Stars: 0
  • License: MIT
  • Security policy (SECURITY.md): absent
INFO Published package is consistent and attested §1.3

No published package associated with this server (remote-only or non-npm/PyPI source).
UNVERIFIABLE Tool surface is inspectable and proportionate §2.1–§2.4

Tool surface could not be inspected (no reachable tools/list, no public package source). Per policy, unverifiability caps the overall grade.
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://mcp.ambermem.com
PASS Authentication required §3.2
Server rejects anonymous requests and advertises its auth scheme. 1 finding
  • WWW-Authenticate: Bearer resource_metadata="https://mcp.ambermem.com/.well-known/oauth-protected-resource"
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://mcp.ambermem.com
INFO No known vulnerabilities (OSV.dev) §4.1

No package to query (remote-only server).
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.