mcp-everything
Related Servers
Alternatives to mcp-everything
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA test server that exercises all MCP protocol features including prompts, tools, resources, and sampling, intended for MCP client builders.286,763 npm-
- AlicenseNot gradedqualityDmaintenanceA test MCP server that exercises all MCP protocol features, including prompts, tools, resources, and sampling, for client builders.286,763 npm-
- AlicenseNot gradedqualityDmaintenanceA test server implementing all features of the MCP protocol, including prompts, tools, resources, and sampling, designed for testing MCP clients rather than practical applications.MIT
- FlicenseAqualityBmaintenanceSmall diagnostic MCP server for checking what MCP clients actually support, including tools, resources, prompts, and transport behavior.9-
- AlicenseNot gradedqualityDmaintenanceA comprehensive testing server for validating MCP scanner tools and implementations, providing diverse tools, resources, and prompts that exercise various aspects of the Model Context Protocol specification.14 npmMIT
- AlicenseNot gradedqualityDmaintenanceA lightweight MCP test server for verifying client connectivity, providing tools, resources, and prompts for integration.14 npmISC
TDQS
Scored across 13 tools
Most tools target distinct MCP demos, but several overlap: get-resource-links and get-resource-reference both concern resources, get-annotated-message and get-structured-content both return content metadata, and trigger-long-running-operation and simulate-research-query both demonstrate long-running progress. Descriptions help, but boundaries are not always crisp.
All tool names use kebab-case and are almost entirely verb-first or get_-prefixed. Minor variations like echo and gzip-file-as-resource still fit the overall verb-led convention.
At 13 tools, the set is well-scoped for a feature-demonstration server. Each tool appears to demonstrate a specific MCP capability, so the count does not feel bloated or thin.
The implied domain is demonstrating MCP features, but the surface leaves notable gaps such as prompts, sampling, and full resource lifecycle operations. It covers many individual demos without providing complete coverage of the protocol area it claims to represent.