Zaturn
kdqed/zaturnMIT⭐ 73🔧 0 tools
D5.9SpiderScore (registry)
⚠ Hard constraint applied: critical issue caps D
Decision
Allow with Risk
Confidence
90%
Zaturn has risks — usable with isolation (5.87/10, 2 critical, 0 high).
Recommended Actions
- highRun In Container2 critical vulnerabilities require isolation
- highLimit PermissionsRestrict tool access to minimum required scope
Do Not
- ✗running in production without container isolation
Risk Flags (2)
- criticalsql_injection×2SQL injection — .execute() called with f-string (user input may reach query)
- mediumssrfPotential SSRF -- unrestricted network requests with user-controlled URLs
How This Was Decided
- positivew=0.5Overall quality score = 5.87/10 (grade D)
- negativew=0.82 critical security issue(s) detected
- positivew=0.3Tool description clarity score = 5.0/10
Source: SpiderRating automated security scanUpdated: 2026-03-13Protocol: v1.1
Description Quality
Composite: 5.0 / 10
3-Layer Breakdown
Description (38%)
5.0
Security (34%)
6.7
Metadata (28%)
6.1
Description Dimensions
Intent Clarity
5.0
Permission Scope
5.0
Side Effects
5.0
Capability Disclosure
5.0
Operational Boundaries
5.0
Security Analysis
6.7
Score
2
Critical
0
High
1
Medium
0
Low
Findings Redacted
Detailed security findings are hidden during the 90-day responsible disclosure window. Maintainers have been notified.
2 CRITICAL1 MEDIUM
Metadata Health
Provenance (40%)
9.0
Maintenance (35%)
3.0
Popularity (25%)
5.8
Badge
Add this badge to your README:
[](https://spiderrating.com/servers/kdqed/zaturn)🛡️
Protect Your Agents
Get a free API key. Every MCP tool call checked against 15,923 rated servers in real-time.
Get Free API Key →📊
Monitor All Your Servers
Dashboard for your entire MCP portfolio. Score tracking, alerts, and compliance reports.
Start Free Trial →⭐
Scan Locally (Open Source)
Run SpiderShield on your own machine. 46+ security rules, zero data leaves your system.
Star on GitHub →