@mhdd_24/api-auth-mcp
Related Servers
Alternatives to @mhdd_24/api-auth-mcp
No user-submitted related servers found.
Related Servers
- 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-
- FlicenseNot gradedqualityDmaintenanceEnables conversational API testing via MCP, allowing users to make HTTP requests, decode JWT tokens, and validate JSON schemas through natural language.-
- AlicenseNot gradedqualityBmaintenanceEnables an AI agent to perform authorized penetration testing through raw HTTP interaction, Python scripting, and shell commands, while providing an authorization wrapper to keep actions within an approved engagement context.MIT
- 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.818 npm5MIT
- FlicenseNot gradedqualityCmaintenanceA full-stack API automation testing server that parses OpenAPI/Swagger/Postman/HAR specs, generates comprehensive test scenarios and executable code, and provides AI-powered review and auto-fix.-
- AlicenseAqualityCmaintenanceEnables AI agents to call real API endpoints and verify responses against OpenAPI specs, supporting contract testing, auth presets, spec diffing, and health checks.849 npmMIT
TDQS
Scored across 3 tools
Each tool has a distinct role: status shows the current auth configuration, probe actually executes a request, and matrix suggests test scenarios. There is minor potential confusion between status and matrix, but the descriptions separate present-state reporting from future/test-plan generation well enough.
All tool names follow a consistent apiauth_ prefix and lowercase snake_case style. Although the names are not strictly verb_noun, the pattern is uniform and predictable across the entire set.
Three tools is well-scoped for the narrow purpose of API auth testing. Each tool covers a meaningful and distinct aspect without unnecessary redundancy.
The set covers inspecting configuration, executing probes, and generating a test matrix, which forms a coherent workflow. A minor gap is the lack of a tool for updating or persisting auth configuration, but the current surface is sufficient for advisory and testing tasks.