MCP Risk

Scan report

ai.kawacode/mcp

This page reports an automated security scan of ai.kawacode/mcp (npm), scanned 2026-07-28. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade B and capability risk (what the tools can do) separately at critical. 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

B 84/100 Capability risk: Critical 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 ai.kawacode/mcp. 1 finding
  • Registry entry: ai.kawacode/mcp ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 12 days ago
  • Stars: 0
  • License: NOASSERTION
  • Security policy (SECURITY.md): absent
FAIL Published package is consistent and attested §1.3
Integrity concerns: package repository field does not match the claimed source repo; no npm provenance attestation. 6 findings
  • Package: @kawacode/mcp@6.9.4 ↗
  • Ecosystem: npm
  • Age: 132 days
  • Weekly downloads: 749
  • Repo field matches source repo: false
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: filesystem, 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): build/kawacode-on-pre-edit.js
  • filesystem (fs module import): build/kawacode-on-pre-edit.js
  • process-execution (child process execution): build/kawacode-on-stop.js
  • process-execution (child process module import): build/kawacode-on-stop.js
  • filesystem (fs module import): build/services/muninn-ipc.js
  • process-execution (child process module import): build/tools/resolve-origin.js
  • Detected capabilities: filesystem, process-execution
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 @kawacode/mcp @6.9.4 (npm).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 3 server-supplied text item(s).

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.