Skip to main content
Glama
nickweedon

Skeleton MCP Server

by nickweedon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Skeleton MCP Server

No user-submitted related servers found.

    Related Servers

    • Skeleton MCP Server

      nickweedon
      A
      license
      A
      quality
      D
      maintenance
      A template project for building Model Context Protocol servers with FastMCP framework, providing example CRUD API implementations, Docker support, and development best practices.
      6
      1
      MIT

    • legal-mcp-server

      bsahane
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready template for developing Model Context Protocol (MCP) servers using Python and FastMCP.
      Apache 2.0

    • MCP Server Template

      rwxproject
      F
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive template for building Model Context Protocol servers with FastMCP framework, featuring modular architecture, auto-discovery registry, and support for multiple transport methods. Includes example arithmetic and weather tools to help developers quickly create custom MCP servers.
      -

    • MCP Server Template

      sinan-ozel
      A
      license
      Not graded
      quality
      C
      maintenance
      A production-ready template for building Model Context Protocol (MCP) servers in Python, using Docker Compose for containerized development and CI/CD.
      MIT
    Deploy Server
    RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

    TDQS

    A3.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose with no ambiguity. The five item-related tools (create_item, delete_item, get_item, list_items, update_item) form a complete CRUD set for a single resource type, while health_check serves a completely different operational purpose. The descriptions reinforce these distinct roles, making tool selection straightforward.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case throughout. The item-related tools use standard CRUD verbs (create, delete, get, list, update) followed by the resource name 'item', while health_check maintains the same pattern. There are no deviations in style or convention across the toolset.

    Tool Count5/5

    Six tools is perfectly appropriate for this server's purpose. The five item management tools provide complete CRUD operations with pagination and filtering, while health_check adds necessary operational functionality. This is a well-scoped set where each tool clearly earns its place without being overwhelming or insufficient.

    Completeness5/5

    The tool surface provides complete coverage for the item management domain with full CRUD operations (create, read, update, delete) plus listing with filtering and pagination. The health_check tool adds operational monitoring. There are no obvious gaps - agents can perform all expected lifecycle operations on items without dead ends or workarounds.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources