Test MCP Server
Related Servers
Alternatives to Test MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables 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.-
- FlicenseBqualityCmaintenanceEnables creating users with name, email, address, and phone, and persisting them to a local JSON file.1-
- AlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol (MCP) server that allows LLMs to create and manage user entries in a JSON file system database.1,026 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to read, write, query, and manage JSON data files with automatic ID and timestamp generation.66 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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.-
- FlicenseNot gradedqualityCmaintenanceA 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
Scored across 2 tools
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.
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.
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.
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.