Skip to main content
Glama
Mhdd-24

@mhdd_24/api-auth-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @mhdd_24/api-auth-mcp

No user-submitted related servers found.

    Related Servers

    • api-testing-agent

      SHREELASYABEZAWADA
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -

    • TalkAPI

      prakhar7824
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables conversational API testing via MCP, allowing users to make HTTP requests, decode JWT tokens, and validate JSON schemas through natural language.
      -

    • Conversational API Test MCP

      Mr-Lucasz
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive API testing from YAML definitions, executing and chaining requests without hand-written curl, while keeping credentials out of the conversation and responses token-cheap, plus a VANDER-based QA review of endpoints.
      MIT

    • DryHack-MCP

      HarshXor
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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

    • MCP OpenAPI Discovery

      Rekl0w
      A
      license
      A
      quality
      B
      maintenance
      Discovers, 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.
      8
      16 npm
      5
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.5/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    Three tools is well-scoped for the narrow purpose of API auth testing. Each tool covers a meaningful and distinct aspect without unnecessary redundancy.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources