Skills/PyPI/iflow-mcp-azurecosmosdb

iflow-mcp-azurecosmosdb@0.1.0

CAUTION

Publisher claims: "MCP Server for Azure Cosmos DB - enables LLM agents to interact with Azure Cosmos DB for NoSQL" Observed in sandbox: static analysis only — behavior not yet observed.

Registry PyPI (MCP server)Publisher azurecosmosdb-noreply · joined 1 days agoInstalls 10Last detonated 33 h ago

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-02 and scored it 69/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

MEDIUM
Access to sensitive file pathsdocker-compose.yml:12 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
AST05

No other findings across 471 lines in 8 files.

What would make this Verified

11 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim azurecosmosdb-noreply: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. Access to sensitive file paths≈ +2 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim azurecosmosdb-noreply