Skip to main content
Glama

Related Servers

Alternatives to sett-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Opinionated template for building read-only MCP servers with I/O timeouts, offline tests, compact text outputs, and least-privilege security guidance.
      2
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A minimal MCP server template demonstrating basic tools, resources, and prompts functionality built with Smithery SDK.
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready Python template for building MCP servers with enterprise features including registry integration, configuration management, structured logging, and extensible patterns for tools, resources, and prompts.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A minimal demonstration MCP server showcasing basic tools, resources, and prompts functionality. Built as a template for learning and starting new MCP server projects with Smithery SDK.
      8 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A minimal template MCP server demonstrating basic tools, resources, and prompts functionality, built with Smithery SDK for quick prototyping and deployment.
      9 npm
      ISC
    • A
      license
      A
      quality
      D
      maintenance
      A Python MCP server template with environment-driven configuration, key authentication with rotation, JSON logging, and a golden-set eval harness for building production-ready MCP servers.
      2
      MIT

    TDQS

    A4.2/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are cleanly separated: search by fuzzy field match versus get by exact id. Descriptions explicitly tell the agent which to use and reference each other, leaving no realistic chance of misselection.

    Naming Consistency4/5

    Both names follow the same `acme_verb_noun` convention, which is predictable. The only nit is `search_contacts` (plural) versus `get_contact` (singular), a minor deviation that does not hinder readability.

    Tool Count3/5

    Two tools is thin for a contact-management surface, though it is plausible for a deliberately read-only gateway. It sits at the borderline where the surface feels minimal rather than well-scoped.

    Completeness2/5

    The surface covers only read access: search and retrieve by id. There is no way to create, update, delete, or enumerate contacts, so any write workflow or bulk listing is a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues