Skip to main content
Glama
kepungnzai

mcp_cimd_server

by kepungnzai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp_cimd_server

No user-submitted related servers found.

    Related Servers

    • simple-mcp

      pcparts001
      F
      license
      Not graded
      quality
      B
      maintenance
      A simple HTTP-based MCP server that provides demo tools (get_test_string, echo, check_maintenance), greeting prompts, and test resources, with optional OAuth 2.1 support.
      -

    • mcp_auth_server

      dawa
      F
      license
      Not graded
      quality
      D
      maintenance
      A proof-of-concept MCP server implementing OAuth 2.1 authorization with CIMD client registration and PKCE, demonstrating protected resource access and step-up authentication.
      -

    • OAuth MCP Framework

      0xagentlabs
      F
      license
      Not graded
      quality
      B
      maintenance
      A minimal MCP server framework for single-owner production deployments using OAuth authorization code flow with PKCE, providing endpoints for MCP, authorization, token, and metadata.
      -

    • Hello World MCP FastAPI

      bankszach
      F
      license
      Not graded
      quality
      D
      maintenance
      A minimal Model Context Protocol server built with FastAPI that provides a basic "Hello World" resource and tool. Serves as a starting point for building and validating MCP client integrations with richer resources and tools.
      -
    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

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: say_hello is a basic greeting, cimd_resolve performs the actual CIMD resolution with caching, cimd_cache_info inspects the cache, and cimd_clear_cache resets it. There is no functional overlap between them.

    Naming Consistency4/5

    The cimd_* tools share a clear prefix and describe their actions (resolve, cache_info, clear_cache). However, cimd_cache_info is more noun-like than verb-first, and say_hello breaks the prefix pattern. Overall, the naming is consistent enough to be predictable.

    Tool Count4/5

    With 4 tools, the server is compact and focuses on the core CIMD resolution domain plus cache management. The unrelated say_hello tool adds a bit of noise but does not make the set feel over- or under-scoped.

    Completeness4/5

    The server covers the essential flow: resolving a client_id with caching, viewing cache contents, and clearing the cache. A minor gap is the lack of a tool to invalidate a specific cache entry without clearing all, but for a small CIMD server this is workable.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources