MCP Risk

Directory / server

app.percher/percher

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

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as app.percher/percher. 1 finding
  • Registry entry: app.percher/percher ↗
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: no npm provenance attestation. 6 findings
  • Package: @percher/mcp@0.6.19 ↗
  • Ecosystem: npm
  • Age: 99 days
  • Weekly downloads: 69
  • Repo field matches source repo: n/a
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: filesystem, network-egress, process-execution. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 7 findings
  • filesystem (filesystem write/delete): dist/src/http/hosted-context.js
  • filesystem (fs module import): dist/src/http/hosted-context.js
  • network-egress (outbound network calls): dist/bin/percher-mcp-http.js
  • process-execution (child process execution): dist/bin/percher-mcp.js
  • process-execution (dynamic code evaluation): dist/bin/percher-mcp.js
  • filesystem (fs module import): dist/bin/percher-mcp.js
  • Detected capabilities: filesystem, network-egress, process-execution
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://mcp.percher.app/mcp
PASS Authentication required §3.2
Server rejects anonymous requests and advertises its auth scheme. 1 finding
  • WWW-Authenticate: Bearer resource_metadata="https://mcp.percher.app/.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.percher.app
PASS No known vulnerabilities (OSV.dev) §4.1

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

No poisoning indicators found across 32 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.