Skip to main content
Glama
vikrantkalyan23

MCP-Server

by vikrantkalyan23
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MCP-Server

No user-submitted related servers found.

    Related Servers

    • node-mcp

      styles102
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that offers arithmetic operations (addition and division) and current weather data from OpenWeatherMap. It serves as a learning project for building MCP servers with Node.js and TypeScript, supporting both stdio and Streamable HTTP transports.
      2 npm
      ISC

    • MCP Server TypeScript Template

      HarshitRatan
      F
      license
      Not graded
      quality
      D
      maintenance
      A demonstration MCP server built in TypeScript that shows how to implement stdio-based communication for integration with MCP clients. Serves as a template for building custom MCP servers with strong typing and maintainability.
      -

    • my-mcp-server

      MarvelNwachukwu
      A
      license
      Not graded
      quality
      D
      maintenance
      A minimal starter template for building Model Context Protocol (MCP) servers using TypeScript and FastMCP, including an example weather tool for demonstration.
      8 npm
      1
      ISC

    • trainee-mcp-server

      whmi1
      F
      license
      Not graded
      quality
      C
      maintenance
      A training MCP server built with TypeScript that provides basic tools (add, get_weather) and a resource (favorite-cities) for use with Claude Desktop. Weather data is fetched from Open-Meteo without requiring an API key.
      -
    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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools serve completely distinct purposes (age vs. weather), so there is no ambiguity or overlap. An agent can easily tell them apart.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern ('get_age', 'get_weather'), making the naming predictable and clear.

    Tool Count2/5

    Only two tools exist, covering two unrelated domains. This feels insufficient for any meaningful workflow, as each domain likely requires more operations (e.g., for weather: location support, forecast; for age: input variations).

    Completeness1/5

    Each tool is a single isolated operation with no supporting tools (e.g., no set_age, no get_forecast). The surface is severely incomplete for any realistic use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources