@mhdd_24/api-security-mcp
Related Servers
Alternatives to @mhdd_24/api-security-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceScan APIs for security vulnerabilities and get OWASP risk scores. Detects auth bypass, BOLA/IDOR, data exposure, prompt injection, and 12+ security categories.20 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to discover API endpoints from OpenAPI/Swagger specs, send HTTP requests, validate responses, and analyze status codes for automated API testing.1-
- AlicenseAqualityBmaintenanceDiscovers, inspects, and executes requests against OpenAPI or Swagger APIs directly from documentation URLs or specification files. It enables users to trace parameter usage across an API and perform authenticated HTTP requests through a structured toolset.88 npm5MIT
- AlicenseNot gradedqualityCmaintenanceEnables security analysis through MCP-compatible clients, including URL phishing checks, email header verification, JWT decoding, password strength analysis, and leaked secret scanning in code.14 npmMIT
- AlicenseAqualityCmaintenanceEnables local analysis of OpenAPI 3 and Swagger 2 JSON/YAML spec files on disk, with no remote fetching of specs or credentials. It groups endpoints by tag, flags operations that appear to lack security, lists deprecated operations, and produces short markdown cheat sheets for agents.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to inspect OpenAPI specs, fuzz live REST endpoints with boundary and adversarial vectors, replay failing anomalies deterministically without AI tokens, and scaffold OpenAPI specs from source routes.Apache 2.0
TDQS
Scored across 3 tools
The three tools are distinct: status is a health check, scan_spec performs a security scan, and checks returns a checklist. There is minor potential confusion between scan_spec and checks since both relate to security analysis, but their purposes are clearly differentiated.
All tool names use a consistent 'apisec_' prefix followed by a noun or verb_noun pattern (status, scan_spec, checks). The pattern is predictable, though 'apisec_checks' is a noun while 'apisec_scan_spec' is verb_noun, creating a slight inconsistency.
Three tools is on the low end but reasonable for a focused API security MCP server. The scope is narrow, so the count is acceptable, though it feels slightly thin for a security tool that might need more operations.
The server covers health check, scanning, and checklist generation, but lacks obvious operations like retrieving scan results, managing scans, or applying fixes. The surface is functional but has notable gaps for a complete security workflow.