T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unaudited Mutable Remote MCP Service
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 39-48
Vulnerability Type:T08: Insecure Dependencies
Risk Level: Mediummarkdown ## Quick Start ```json { "openclaw-timestamp": { "type": "streamable-http", "url": "https://timestamp-converter-mcp.yagami8095.workers.dev/mcp" } }Add to Claude Desktop, Cursor, Windsurf, VS Code, or any MCP-compatible client. Zero install. Works immediately.
text ### Technical Analysis The skill directs users to configure a remotely hosted MCP server on a mutable Cloudflare Workers subdomain. The package contains no server implementation, pinned source revision, artifact digest, signature, or other integrity mechanism that would allow users to verify the behavior of the service. Consequently, the server operator can alter the effective tool implementation after this skill has been reviewed or installed. All values submitted to the advertised tools, including timestamps, meeting times, source and destination time zones, and date calculations, are transmitted to infrastructure controlled by a third party. The privacy claims in `SKILL.md`, including assertions that inputs are not logged or stored, cannot be independently verified from this documentation-only package. This finding does not establish that the current endpoint is malicious. It identifies a supply-chain and trust-boundary weakness caused by relying on an externally controlled, mutable component without verifiable provenance or integrity controls. ### Attack Path 1. A user follows the Quick Start instructions and registers the supplied remote MCP endpoint in an MCP-compatible client. 2. The endpoint operator changes the server implementation after the skill has been reviewed, or the hosting account is compromised. 3. The user invokes one of the advertised tools and sends timestamp, scheduling, or time-zone information to the remote service. 4. The modified service records the s ...[truncated 881 chars]- Remediation
View remediation
Remediation Suggestions
- Publish the complete MCP server source code so users can audit the implementation and deploy it locally.
- Pin the recommended service to a verifiable release and publish signed build artifacts, checksums, or reproducible-build instructions.
- Clearly disclose that tool inputs leave the user's environment and identify every field transmitted to the remote server.
- Document service ownership, data retention, logging, deletion, incident response, and privacy policies in verifiable terms.
- Provide a local-only implementation for timestamp and time-zone calculations, which do not inherently require remote processing.
- If remote operation remains necessary, use authenticated releases, strict transport security, request minimization, and independent monitoring for unexpected endpoint changes.
- Advise users not to submit confidential schedules or contextual information unless they have independently assessed and accepted the service operator's trust and privacy model.
