MCP/Risk

Scan report

ai.vaaya/mcp

npm, scanned 2026-11-07, tool surface via remote-tools-list

This page reports an automated security scan of ai.vaaya/mcp (npm), scanned 2026-11-07. 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.

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as ai.vaaya/mcp. 1 finding
  • Registry entry: ai.vaaya/mcp ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 54 days ago
  • Stars: 44
  • License: MIT
  • Security policy (SECURITY.md): absent
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: @vaaya/mcp@0.7.0 ↗
  • Ecosystem: npm
  • Age: 140 days
  • Weekly downloads: 135
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
14 tool(s) enumerated. Capabilities detected: filesystem. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 3 findings
  • Tools exposed: 14
  • session: filesystem
  • Detected capabilities: filesystem
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://vaaya.ai/mcp
FAIL Authentication required §3.2

Server answers anonymous requests (HTTP 200) while exposing non-trivial or unverifiable capabilities - fail per §3.2.
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://vaaya.ai
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @vaaya/mcp @0.7.0 (npm).
WARN Server-supplied instructions free of poisoning indicators §5.1–§5.4
1 suspicious indicator(s) found in server-supplied instructions, tool descriptions, or schemas. 1 finding
  • buy description: oversized: 4408 chars (limit 2048)

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.