MCP/Risk

Scan report

ar.com.muovi/mcp-server

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

This page reports an automated security scan of ar.com.muovi/mcp-server (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 low. 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 ar.com.muovi/mcp-server. 1 finding
  • Registry entry: ar.com.muovi/mcp-server ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 31 days ago
  • Stars: 1
  • 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: @muovi/mcp-server@0.4.2 ↗
  • Ecosystem: npm
  • Age: 151 days
  • Weekly downloads: 99
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
8 tool(s) enumerated; no high-risk capability signals. 2 findings
  • Tools exposed: 8
  • Detected capabilities: none
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://mcp.muovi.com.ar/
WARN Authentication required §3.2

Server answers anonymous requests (HTTP 200). Acceptable only for deliberately public, read-only (Low) servers.
PASS OAuth protected-resource metadata published §3.3

Publishes /.well-known/oauth-protected-resource per the June 2025 authorization spec.
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @muovi/mcp-server @0.4.2 (npm).
WARN Server-supplied instructions free of poisoning indicators §5.1–§5.4
4 suspicious indicator(s) found in server-supplied instructions, tool descriptions, or schemas. 4 findings
  • muovi_search_professionals description: oversized: 2307 chars (limit 2048)
  • muovi_create_task_draft description: oversized: 2600 chars (limit 2048)
  • muovi_create_task_draft: cross-tool shadowing: instead of `professional_id`
  • muovi_create_task_draft (schema): cross-tool shadowing: instead of professional_id.

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.