toolmenu
Related Servers
Alternatives to toolmenu
- FlicenseNot gradedqualityDmaintenanceA basic MCP server template that provides a foundation for building custom tools, resources, and prompts. Serves as a starting point for developers to create their own MCP server functionality.-
- AlicenseBqualityBmaintenanceFinds problems in your MCP servers before your users do. Scans your Claude config, checks every server's capabilities, actually calls tools to make sure they work, and catches breaking changes between versions.13665 npm121MIT
Related Servers
- AlicenseNot gradedqualityAmaintenanceRuns the MCP initialize handshake and validates tools/list JSON schemas on any public MCP server, and inspects x402 payment endpoints. Ships as a stdio MCP server the agent calls directly, plus a CLI and a GitHub Action. Read-only, no API key needed.657 npmMIT
- AlicenseAqualityCmaintenanceA stdio MCP server that audits other MCP servers over the live protocol. It connects to any MCP target (stdio or HTTP), lints every tool's schema for agent-usability, then actually calls the tools with deliberately broken inputs to see how the server handles them, and returns a 0–100 conformance score with a per-dimension breakdown rendered as Markdown.620 npm6MIT
- AlicenseAqualityDmaintenanceMCP server that validates LLM-generated tool-call arguments, lints tool definitions, and produces retry messages for AI assistants.337 npm1MIT

apidrifterofficial
AlicenseNot gradedqualityBmaintenanceEnables agents to plan and run requests from OpenAPI documents, verify live API responses against specs, diff spec versions for breaking changes, and snapshot or compare MCP servers including tool descriptions.47Apache 2.0- AlicenseAqualityDmaintenanceA stdio MCP server that audits other MCP servers by linting their tool schemas and calling tools with malformed inputs to produce a 0–100 conformance score and Markdown report.620 npmMIT
- AlicenseNot gradedqualityBmaintenancePerforms explainable, deterministic static analysis of MCP tool metadata to detect misleading instructions, concealed capabilities, and schema drift without executing tools.1MIT
TDQS
Scored across 4 tools
Each tool has a distinct role: snapshot_menu captures a menu, diff_menus compares two saved menus, explain_rule documents rules, and check_session monitors menu changes during a live session. The only mild overlap is between snapshot_menu and check_session, since both list a server's tools and report findings, but the one-shot vs. live-session distinction is made clear in the descriptions.
All four names follow the same snake_case verb_noun pattern (snapshot_menu, explain_rule, diff_menus, check_session) with the noun always referring to the menu/rule/session domain. No mixing of conventions or vague verbs.
Four tools is on the lean side but each maps to a genuinely different workflow (capture, compare, explain, monitor) with no filler. A slightly larger surface might be expected for menu management, but nothing here feels redundant.
The core audit lifecycle is covered: snapshot to a file, diff against a baseline, inspect rules, and verify changes during a session. Minor gaps remain, such as listing or deleting previously saved menu files and configuring rules, but agents can work around these.