MCP Dev MCP
Related Servers
Alternatives to MCP Dev MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables LLMs to inspect and test other MCP servers by listing and calling their tools, reading resources, and getting prompts. Supports stdio, SSE, and HTTP transports for both local and remote MCP server inspection.75 npm1MIT
- -licenseNot gradedqualityNot gradedmaintenanceProvides programmatic access to MCP server testing, debugging, and validation capabilities by wrapping the official MCP Inspector. Enables users to test tools, validate protocol compliance, discover server capabilities, and debug MCP servers through natural language interactions.-
- AlicenseNot gradedqualityAmaintenanceEnables AI tools to uniformly discover, inspect, and call tools, prompts, and resources from multiple upstream MCP servers through a small set of fixed MCP tools, over stdio or HTTP.2MIT
- AlicenseAqualityCmaintenanceEnables AI agents to programmatically inspect, test, and validate other MCP servers by exposing MCP Workbench capabilities as structured tools. It supports automated test spec generation, execution, and detailed failure analysis to ensure server reliability.45 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible clients to access model registry, prediction logging, drift detection, bias/fairness auditing, compliance and governance queries, explanation generation, LLM/RAG monitoring, content safety, alert management, multi-agent workflow tracking, and performance metrics through 197 tools across 18 domains. Supports stdio and hosted Streamable HTTP transports, plus MCP Apps interactive audit cards.MIT
- FlicenseNot gradedqualityDmaintenanceExposes MCP tools that enable remote LLMs to query local Docker containers, OS processes, and system services in real time.-
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: call_tool executes tools, get_prompt retrieves prompts, list_prompts lists prompts, list_resources lists resources, list_tools lists tools, and read_resource reads resources. The descriptions clearly differentiate their functions, making misselection unlikely.
All tools follow a consistent snake_case pattern with the prefix 'mcpdev_inspector_' followed by a verb_noun structure (e.g., call_tool, get_prompt, list_prompts). This predictability makes the tool set easy to navigate and understand.
With 6 tools, this server is well-scoped for its purpose of inspecting and interacting with MCP servers. Each tool serves a specific role in discovery and execution, with no redundancy, making the count appropriate and efficient.
The tool set provides complete coverage for the MCP server inspection domain, including listing tools, prompts, and resources, reading resources, getting prompts, and calling tools. There are no obvious gaps, enabling agents to perform all essential inspection and interaction tasks.