MCP Risk

Scan report

co.whooshly/whooshly-mcp

This page reports an automated security scan of co.whooshly/whooshly-mcp (npm), scanned 2026-07-28. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade A and capability risk (what the tools can do) separately at high. It does not certify the server is safe to connect; it reports what could be checked from outside.

npm, scanned 2026-07-28, tool surface via package-source

A 93/100 Capability risk: High permalink

The grade rates trust: provenance, transport, known vulnerabilities and instruction integrity. Capability risk rates what the tools can do and is reported, not penalised – a server built to run shell commands is doing its job (Policy §2.4).

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as co.whooshly/whooshly-mcp. 1 finding
  • Registry entry: co.whooshly/whooshly-mcp ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 9 days ago
  • Stars: 0
  • License: MIT
  • Security policy (SECURITY.md): absent
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: whooshly-mcp@1.1.0 ↗
  • Ecosystem: npm
  • Age: 15 days
  • Weekly downloads: 287
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 2 findings
  • network-egress (outbound network calls): bin/whooshly-mcp.mjs
  • Detected capabilities: network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://app.whooshly.co/api/mcp
PASS Authentication required §3.2
Server rejects anonymous requests and advertises its auth scheme. 1 finding
  • WWW-Authenticate: Bearer realm="OAuth", resource_metadata="https://app.whooshly.co/.well-known/oauth-protected-resource/api/mcp", error="invalid_token", error_description="Missing or invalid access token"
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://app.whooshly.co
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for whooshly-mcp @1.1.0 (npm).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

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

Verify manually - the scoring model can’t judge these for you

  • §2.3 - Is the tool surface no broader than the server’s stated purpose requires?
  • §3.4 - For stdio servers: which environment credentials does it read, and are they scoped rather than org-wide tokens?
  • §6.1 - Cross this server’s capabilities with your already-connected servers: any read-capability × send-capability pairs need explicit sign-off.
  • §6.2 - Run the connecting agent with sandboxing and egress controls sized to the combined tool surface, not just this server’s.

Methodology: MCP Server Security Policy. Checks and scoring weights are open source. Unfamiliar term? See the glossary.