Skip to main content
Glama
hyen43

Model Context Protocol Server

by hyen43
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Model Context Protocol Server

No user-submitted related servers found.

    Related Servers

    • My MCP Server

      goodafternoonoo
      F
      license
      Not graded
      quality
      D
      maintenance
      A customizable Model Context Protocol server built with mcp-framework that enables Claude to access external tools and capabilities through a standardized interface.
      67 npm
      -

    • Calculator MCP Server

      QuantGeekDev
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server built with mcp-framework that allows users to create and manage custom tools for processing data, integrating with the Claude Desktop via CLI.
      9 npm
      5
      MIT

    • my-mcp-server

      15972289829
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that allows integration with Claude Desktop by creating and managing custom tools that can be executed through the MCP framework.
      67 npm
      -

    • routine-mcp

      rskmanz
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server built with the mcp-framework for developing and managing custom tools. It provides a structured foundation for building and integrating modular components like data processors and API clients into Claude Desktop.
      5 npm
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    C2.6/5.0

    Scored across 3 tools

    Disambiguation2/5

    The 'weather' and 'weather_api' tools have significant overlap in purpose, as both appear to fetch weather information for a city, making them ambiguous and prone to misselection. The 'example_tool' is distinct but vague, adding to the overall confusion in the tool set.

    Naming Consistency3/5

    The naming is mixed with 'example_tool' and 'weather_api' using snake_case, while 'weather' is a single word, showing some inconsistency. However, the names are still readable and follow a basic pattern, but lack a uniform verb_noun structure or consistent style.

    Tool Count3/5

    With only 3 tools, the count is borderline thin for a general-purpose server like 'Model Context Protocol Server', suggesting it might be under-scoped. While not extreme, it feels insufficient to cover a broad domain effectively, indicating a potential mismatch in scope.

    Completeness2/5

    The tool set is severely incomplete for the server's implied domain, with overlapping weather tools and a vague example tool, leaving obvious gaps in functionality. There is no clear coverage of core operations or a coherent workflow, which will likely cause agent failures due to missing essential capabilities.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources