Skip to main content
Glama
Mhdd-24

@mhdd_24/api-mocking-mcp

by Mhdd-24
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @mhdd_24/api-mocking-mcp

No user-submitted related servers found.

    Related Servers

    • Bruno MCP Server

      brianconway
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables API development directly from MCP clients by creating and editing collections, running requests through the real CLI, generating documentation, and starting mock servers.
      52 npm
      MIT

    • studyofus-agent

      aminamos
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables local agent interactions with a mock Study of Us API through tools for health checks, catalogs, current user info, reports, and voting.
      MIT

    • SpyNet

      aj-bartocci
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to configure and manage session-based REST and WebSocket mock servers for application development and testing. It allows for dynamic endpoint setup, request history inspection, and real-time WebSocket communication through natural language commands.
      8
      -

    • mcp-mock

      vibeglitch
      A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight mock MCP server for local testing and resilience experiments, providing predictable tool responses with simulated latency and errors.
      1
      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

    Disambiguation5/5

    The three tools are clearly distinct: status is a health check, mock generates a single endpoint response, and collection generates a full mock collection. There is no ambiguity in their purposes.

    Naming Consistency5/5

    All tool names share the consistent apimock_ prefix and follow a simple noun pattern (status, mock, collection). This makes the toolset predictable and easy to navigate.

    Tool Count5/5

    Three tools is well-scoped for a simple API mocking utility. Each tool serves a single clear purpose without unnecessary bloat.

    Completeness4/5

    The core capabilities of checking service health, generating a single mock, and generating a collection are covered. A minor gap is the lack of configuration options (e.g., status codes or headers), but the surface is otherwise sufficient for basic mocking.

    Resources