Skip to main content
Glama
thev1ndu

mcpnertes

by thev1ndu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcpnertes

No user-submitted related servers found.

    Related Servers

    • Claude Ops Investigator

      Randhir123
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only Kubernetes incident investigation through MCP tools for listing pods, describing resources, fetching logs, and searching runbooks.
      1
      -

    • Google Ads MCP

      zelentsov-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only inspection of Google Ads accounts through MCP, including account inventory, reporting, metadata, change history, and safe GAQL queries.
      Apache 2.0

    • mcp-kubernetes

      dockndevai
      A
      license
      A
      quality
      A
      maintenance
      Enables MCP clients to inspect and operate Kubernetes clusters across multiple contexts, with read-only/read-write/admin access modes and security flags controlling namespaces, contexts, deletes, applies, and exec.
      10
      68 npm
      2
      MIT

    • corporate-mcp-system-inspector

      313ON
      F
      license
      A
      quality
      C
      maintenance
      Enables observation-only system inspection through MCP, exposing system identity, resources, process summary, and network summary without any mutation or command execution.
      4
      -
    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

    A3.5/5.0

    Scored across 11 tools

    Disambiguation3/5

    There is notable overlap between list_pods, list_deployments, list_services, list_resource, and list_api_resources. list_resource and get_resource are generic dynamic-client tools that can overlap with the specific resource listers, though the specific ones are convenient. get_pod_logs and get_logs also overlap, with get_logs being a broader version of get_pod_logs.

    Naming Consistency4/5

    Most tools follow a consistent list_<resource> or get_<resource> pattern. Minor deviations: list_resource and get_resource are generic rather than resource-specific, and list_api_resources is a discovery operation rather than listing actual resources, but the overall pattern is predictable.

    Tool Count4/5

    11 tools is a reasonable count for a Kubernetes MCP server covering common read-only operations. It is slightly redundant because generic list_resource/get_resource could subsume the specific listers, but the count is not excessive.

    Completeness3/5

    The server is read-only by design, so it covers listing and getting resources, logs, events, and discovery. However, it lacks common read operations like describe/status for resources, and there is no way to get a single deployment or pod by name except through the generic get_resource, which is a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources