MCP Risk

Scan report

ai.rapay/mcp-server

This page reports an automated security scan of ai.rapay/mcp-server (npm), scanned 2026-07-28. It rates trust (provenance, transport, known vulnerabilities, instruction integrity) as grade C 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

C 68/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 ai.rapay/mcp-server. 1 finding
  • Registry entry: ai.rapay/mcp-server ↗
FAIL Source repository is public and maintained §1.2

Claimed source repository does not exist (or is private).
FAIL Published package is consistent and attested §1.3
Latest version is deprecated by its own maintainer. 6 findings
  • Package: @rapay/mcp-server@1.3.2 ↗
  • Ecosystem: npm
  • Age: 190 days
  • Weekly downloads: 34
  • 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: filesystem, 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. 4 findings
  • filesystem (filesystem write/delete): dist/audit.js
  • filesystem (fs module import): dist/audit.js
  • network-egress (outbound network calls): dist/version-check.js
  • Detected capabilities: filesystem, network-egress
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 @rapay/mcp-server @1.3.2 (npm).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

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