Skip to main content
Glama
tqmvt
by tqmvt

Related Servers

Alternatives to Test MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI-compatible MCP clients to create, retrieve, update, and delete user records through five MCP tools, plus a guide resource and a prompt that auto-generates and saves random users. User data is validated with Zod and persisted in a JSON file behind a Streamable HTTP endpoint.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      A simple Model Context Protocol (MCP) server that allows LLMs to create and manage user entries in a JSON file system database.
      1,026 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to read, write, query, and manage JSON data files with automatic ID and timestamp generation.
      6
      6 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables users to manage data in a simple JSON file database through MCP tools and REST API. Supports creating, reading, updating, and deleting items organized in collections with auto-generated UUIDs.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      A testing server that provides CRUD operations on a JSON user database via MCP tools, enabling AI assistants to list, search, add, update, and delete users.
      1
      -

    TDQS

    B3.3/5.0

    Scored across 2 tools

    Disambiguation4/5

    The two tools are clearly described: one creates a specified user, the other generates a random one. While both involve creation, the random qualifier distinguishes them, so an agent should not easily confuse them.

    Naming Consistency5/5

    Both tools follow a consistent verb_noun pattern (create-user, create-random-user), with the second incorporating a modifier while maintaining the same structure. The naming is uniform and predictable.

    Tool Count3/5

    With only 2 tools, this is a very thin set, but it could be appropriate for a narrowly scoped server focused solely on user creation. It falls into the borderline range (1-2 tools), neither too many nor too few for the apparent purpose.

    Completeness2/5

    The server only offers creation capabilities, lacking essential operations like retrieving, updating, or deleting users. This leaves obvious gaps in the user lifecycle, which would cause agent failures if the server is intended for full user management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues