Skip to main content
Glama

Related Servers

Alternatives to skills-example

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to call a simple greeting tool that takes a name and returns personalized text and structured messages via stdio.
      1
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables a simple greeting tool over MCP, demonstrating schema validation and transport communication.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Serves skill-defined JSON-in/JSON-out scripts as callable tools over MCP stdio, driven by a portable skill-runtime.json manifest that supplies each tool's title, description, and input schema. Exposes commands to validate, list, and run skills, so hosts can discover and invoke agent skills without custom per-skill glue code.
      9 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Turns any folder of agent skills into a live MCP server, exposing skills_list, skills_get, and skills_search tools with zero-dependency stdio support.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A simple MCP server that exposes a 'greet' tool which returns a friendly greeting for a given name.
      6 npm
      ISC
    • F
      license
      A
      quality
      C
      maintenance
      Provides a minimal Model Context Protocol server that demonstrates a basic tool, a static resource, and a prompt template, enabling clients to discover and exercise core MCP capabilities over stdio.
      1
      -

    TDQS

    B3.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion or overlap. The tool's purpose is singular and clear.

    Naming Consistency5/5

    The single tool name 'greet' follows a simple verb pattern, consistent with itself. No inconsistencies can exist with only one tool.

    Tool Count3/5

    One tool is at the lower boundary of acceptability. While it feels thin for a typical server, it is reasonable for a small example or demo server.

    Completeness5/5

    The domain is limited to greeting, and the single tool fully covers that purpose. There are no obvious gaps within the stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues