Skip to main content
Glama
jiziyun149-cpu

crc-lnm-medical-agent

Related Servers

Alternatives to crc-lnm-medical-agent

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      A simple cloud-hosted MCP server for verifying upstream MCP connectivity via Streamable HTTP, exposing a single tool that returns a fixed success message.
      -
    • F
      license
      A
      quality
      B
      maintenance
      A minimal MCP server built with the official Python SDK that runs over stdio and exposes a health capability, providing a practical integration-testing target for AI and agent codebases.
      6
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      A minimal Model Context Protocol server built with FastAPI that provides a basic "Hello World" resource and tool. Serves as a starting point for building and validating MCP client integrations with richer resources and tools.
      -
    • 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
    • A
      license
      A
      quality
      D
      maintenance
      A simple Model Context Protocol server that provides a hello world greeting tool, serving as a boilerplate template for quickly creating new MCP servers.
      1
      6 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server built with FastMCP that features dynamic tool loading and modular management via a dedicated tool directory. It supports both stdio and HTTP transport modes, enabling efficient development and deployment of custom MCP tools.
      -

    TDQS

    B3.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: one reports health/status information, the other describes the deployment's behavior. There is no overlap in their purposes.

    Naming Consistency2/5

    Naming styles are inconsistent: 'healthcheck' is a single word noun, while 'describe_deployment' follows the verb_noun snake_case pattern. This lack of a consistent convention makes the set feel uncoordinated.

    Tool Count3/5

    With only two tools, the set is on the thin side, but the explicit mention of a 'deliberately limited behavior' suggests this small count is intentional for a staging environment. Still, it is borderline for a typical server.

    Completeness1/5

    Despite the server name indicating a medical agent, the provided tools only cover operational metadata (healthcheck and deployment description) with zero medical domain functionality. The surface is severely incomplete for any meaningful medical workflow.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues