A
licenseA
qualityC
maintenanceSecurity scanning, prompt injection detection, secret leak detection, and agent permission auditing for AI agent workflows.
8
24 npm
MIT
haiec-ai-agent-security-free-mcp
by subodhkc
Related Servers
Alternatives to haiec-ai-agent-security-free-mcp
No user-submitted related servers found.
Related Servers
Draugrofficial
AlicenseNot gradedqualityAmaintenanceSecurity scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.7Apache 2.0
Rigour MCPofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to self-govern by scanning code for hardcoded secrets, structural violations, and AI drift in real-time, providing fix packets for automatic remediation.27MIT- AlicenseNot gradedqualityCmaintenanceEnables deterministic zero-trust security for AI agents, providing prompt injection protection, PII scrubbing, and policy enforcement before agentic actions reach production systems.2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceProvides pre-deploy AI-assisted security and readiness checks for AI-built apps, including scanning for secrets, auth gaps, and payment safety.5MIT
- AlicenseNot gradedqualityBmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT
TDQS
A4.4/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool is exposed, so there is no possibility of confusing it with another tool. The description also explicitly lists out-of-scope use cases, which helps clarify the intended boundary.
Naming Consistency5/5
The single tool name 'scan_ai_security' follows a clear snake_case verb_noun convention. With only one name, there are no conflicting patterns or inconsistent verb styles to penalize.
Tool Count3/5
One tool is a minimal, thin surface for the stated security-audit workflow. It can handle the core scanning request, but the surface feels sparse given the referenced verify_llm_content, scan_tenant_isolation, and not-yet-implemented check_deploy_security operations.
Completeness3/5
The scan tool covers static analysis and returns structured findings, but the workflow has a clear dead end: BLOCK findings are advisory and deployment enforcement is explicitly not yet implemented. There is also no way to manage or act on findings beyond the initial scan.
Maintenance
ActivityMaintained
ResponsivenessNo issues