Trust Assessment
gold_price_mcp received a trust score of 86/100, placing it in the Mostly Trusted category. This skill has passed most security checks with only minor considerations noted.
SkillShield's automated analysis identified 4 findings: 0 critical, 0 high, 2 medium, and 0 low severity. Key findings include Unpinned Python dependency version, Unpinned Dependency.
The analysis covered 4 layers: Manifest Analysis, Static Code Analysis, Dependency Graph, LLM Behavioral Safety. All layers scored 70 or above, reflecting consistent security practices.
Last analyzed on February 13, 2026 (commit 13146e6a). SkillShield performs automated 4-layer security analysis on AI skills and MCP servers.
Layer Breakdown
Behavioral Risk Signals
Security Findings4
| Severity | Finding | Layer | Location | |
|---|---|---|---|---|
| MEDIUM | Unpinned Python dependency version Requirement 'mcp-server' is not pinned to an exact version. Pin Python dependencies with '==<exact version>'. | Dependencies | skills/jjannet/gold-price-mcp/requirements.txt:1 | |
| MEDIUM | Unpinned Python dependency version Requirement 'httpx' is not pinned to an exact version. Pin Python dependencies with '==<exact version>'. | Dependencies | skills/jjannet/gold-price-mcp/requirements.txt:2 | |
| INFO | Unpinned Dependency The 'requirements.txt' file specifies dependencies without pinning them to a specific version (e.g., 'package==1.2.3'). This can lead to non-reproducible builds, unexpected behavior, or the introduction of vulnerabilities if a new version of a dependency contains breaking changes or security flaws. While not a critical vulnerability in itself, it's a best practice to pin dependencies. Pin dependencies to specific versions (e.g., 'mcp-server==X.Y.Z', 'httpx==A.B.C') to ensure consistent and secure environments. Regularly review and update pinned versions. | LLM | requirements.txt:1 | |
| INFO | Unpinned Dependency The 'requirements.txt' file specifies dependencies without pinning them to a specific version (e.g., 'package==1.2.3'). This can lead to non-reproducible builds, unexpected behavior, or the introduction of vulnerabilities if a new version of a dependency contains breaking changes or security flaws. While not a critical vulnerability in itself, it's a best practice to pin dependencies. Pin dependencies to specific versions (e.g., 'mcp-server==X.Y.Z', 'httpx==A.B.C') to ensure consistent and secure environments. Regularly review and update pinned versions. | LLM | requirements.txt:2 |
Scan History
Embed Code
[](https://skillshield.io/report/aaa9ce813dcc3986)
Powered by SkillShield