Skip to main content
Glama
esinecan

MCP Inspector as MCP Server

by esinecan

Related Servers

Alternatives to MCP Inspector as MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables LLM agents to programmatically inspect, debug, and test other MCP servers by wrapping the MCP Inspector CLI. Supports listing and calling tools, reading resources, and testing prompts on both local and remote MCP servers.
      6
      5 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server is a zero-config CLI tool that lets developers tap into any stdio-based MCP server from their terminal, enabling them to list tools/resources/prompts, call tools with JSON arguments, and health-check servers without requiring a full AI client or browser setup.
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A dual-transport MCP server that exposes your API as tools to LLM clients, supporting both stdio transport for local clients like Claude Desktop and HTTP/SSE transport for remote clients like OpenAI's Responses API.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that publishes CLI tools on your machine for discoverability by LLMs
      10 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      A mock MCP server for testing MCP client implementations and development workflows. Supports tools, prompts, and resources across multiple transport protocols (stdio, HTTP, SSE).
      1
      MIT

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting different MCP server components: prompts (get/list), resources (list/read/templates), and tools (list/call). There is no overlap or ambiguity in functionality, making it easy for an agent to select the correct tool.

    Naming Consistency5/5

    All tools follow a consistent 'insp_[component]_[action]' pattern with snake_case, using clear verbs like get, list, read, call, and templates. This predictability enhances usability and reduces confusion.

    Tool Count5/5

    With 7 tools, the server is well-scoped for inspecting MCP servers, covering prompts, resources, and tools comprehensively. Each tool earns its place without being excessive or insufficient for the domain.

    Completeness5/5

    The tool set provides complete coverage for inspecting MCP servers, including listing and accessing prompts, resources (with templates), and tools (with calling capability). There are no obvious gaps, ensuring agents can perform all necessary inspection tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues