Security audit

Api Odontosoft

Security checks across malware telemetry and agentic risk

Overview

This skill is a straightforward Odontosoft dental scheduling integration, but installers should treat it as handling sensitive patient data.

Install only for authorized clinic staff or systems. Use a least-privileged Odontosoft token, keep the base URL on the intended HTTPS Odontosoft service, confirm patient and appointment details before booking, and avoid logging document numbers or appointment details.

SkillSpector

Vulnerability Patterns

Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
MCP Least PrivilegeUnderdeclared Capability, Wildcard Permission, Missing Permission Declaration
Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code

Findings (5)

Lp3

Medium

Category: MCP Least Privilege
Confidence: 92% confidence
Finding: The skill clearly performs network-backed operations against an external Odontosoft API, yet the skill metadata shown in the file does not declare that capability as a permission. This creates a transparency and policy-enforcement gap: users and host systems may not understand that the skill can transmit data externally, including patient identifiers and scheduling details.

Missing User Warnings

Medium

Confidence: 90% confidence
Finding: The README explicitly documents searching patients by document number and scheduling dental appointments, which implies handling personally identifiable information and health-related data. Omitting any warning about sensitive-data handling, access control expectations, logging minimization, or privacy obligations can lead integrators to expose, transmit, or retain regulated patient data unsafely.

Missing User Warnings

Medium

Confidence: 95% confidence
Finding: The description says the skill manages dental appointments and requires ODONTOSOFT_BASE_URL and ODONTOSOFT_TOKEN, but it does not warn that it accesses patient data and sends requests to an external dental system. In a healthcare context, omission of this privacy/security disclosure is more dangerous because the workflow includes patient lookup by document number and appointment creation, involving sensitive personal and medical-adjacent data.

Missing User Warnings

Medium

Confidence: 92% confidence
Finding: The manifest exposes capabilities to look up patients by document number and book appointments, which involves handling sensitive health-related and identifying personal data. Without any user-facing disclosure or consent warning, users may not understand that the skill can retrieve and transmit protected patient information to an external clinical system, increasing privacy and compliance risk.

Missing User Warnings

Medium

Confidence: 90% confidence
Finding: The manifest requires a bearer token and network access to an external API but does not warn users that their requests and supplied data will be transmitted off-platform under authenticated access. This lack of transparency can lead to unintended disclosure of personal or operational data and makes misuse of privileged backend access less visible to users.

VirusTotal

64/64 vendors flagged this skill as clean.

View on VirusTotal

Static analysis

No suspicious patterns detected.