incident-response
chunhualiao/incident-response⭐ 0🔧 0 tools
C6.5SpiderScore (registry)
Decision
Recommended
Confidence
90%
incident-response is safe to use — high score (6.54/10), no critical issues.
Risk Flags (1)
- highsandbox.not_configured[TS-C009] No sandbox
How This Was Decided
- positivew=0.5Overall quality score = 6.54/10 (grade C)
- negativew=0.51 high-severity issue(s) detected
- positivew=0.3Tool description clarity score = 6.65/10
Source: SpiderRating automated security scanUpdated: 2026-03-22Protocol: v1.1
Description Quality
Composite: 6.7 / 10
3-Layer Breakdown
Description (38%)
6.7
Security (34%)
8.0
Metadata (28%)
4.6
Description Dimensions
Intent Clarity
6.0
Permission Scope
4.0
Side Effects
8.0
Capability Disclosure
7.5
Operational Boundaries
9.0
Category Ranking: Developer Tools
#11 of 214 · Top 5%Overall#116.5 (avg 5.8)
Security8.0 (avg 7.6)
Description#336.7 (avg 5.6)
Metadata#424.6 (avg 4.1)
Why #11 in Developer Tools?
Top 5% of 214 toolsSecurity8.0avg 7.6
Description#336.7avg 5.6
Metadata#424.6avg 4.1
How to reach #10? Need +0.0 overall to pass Git Repo To Book (6.6).
Top action: Register MCP tools with name, description, and input schema (+2.3)
Security Analysis
8.0
Score
0
Critical
1
High
0
Medium
0
Low
HIGH
Metadata Health
Provenance (40%)
7.5
Maintenance (35%)
2.0
Popularity (25%)
3.6
Badge
Add this badge to your README:
[](https://spiderrating.com/servers/chunhualiao/incident-response)🛡️
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 →