M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionKubesharkKubernetes network observability for SREs and AI agentsHevy MCPManage your Hevy workout data from AI assistants via MCP.
FMRS52 / 100 · D77 / 100 · B
Reliability9 / 2012 / 20
Security and permissions8 / 2016 / 20
Maintenance11 / 2016 / 20
Documentation12 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • SRE, DevOps, and network engineering teams using Kubernetes.
  • Incident response and root-cause analysis requiring cluster-wide network, API, and Kubernetes context.
  • Teams that want MCP-compatible AI agents to query live or retained network data.
  • Hevy PRO users who want AI assistants to directly access their workout data
  • People who prefer using MCP clients like Claude, Cursor, Codex for fitness tracking
  • Anyone needing summaries and insights from their training data
Not for
  • Users who do not run Kubernetes or do not need network traffic observability.
  • Client scenarios requiring only generic file, database, or collaboration features.
  • Environments where handling sensitive traffic or decrypting TLS/mTLS is unacceptable.
  • Users without a Hevy PRO subscription (API key required)
  • Users who want to use the server without an API key
  • Those needing delete workflows (Hevy API does not expose delete endpoints)
Required permissions
  • Proxy mode requires a kubeconfig with access to the Kubernetes cluster.
  • Direct URL mode requires access to an existing Kubeshark Hub URL.
  • Start and stop operations require explicitly enabling --allow-destructive.
  • The source does not specify exact Kubernetes RBAC permissions or authentication mechanisms.
  • Requires HEVY_API_KEY environment variable for Hevy API authentication
  • Can create, update, and replace workouts, routines, folders, templates, and body measurements via tools
  • Read operations can fetch workouts, routines, folders, templates, history, and user info
Risks and side effects
  • The server can deploy or remove Kubeshark; start_kubeshark and stop_kubeshark are marked destructive.
  • Observed data may include complete API requests, headers, bodies, and PCAPs.
  • TLS/mTLS traffic can be decrypted into plaintext, potentially exposing sensitive information.
  • The source does not specify access-control, authentication, or data-retention policies.
  • API key can be misused if leaked; do not expose in URLs, logs, or screenshots
  • Create operations may produce duplicates on retry; update operations replace existing records
  • The server sends data to the Hevy API and may send telemetry to external services unless disabled
Supported clientsClaude Code, CursorClaude Desktop, Cursor, Codex, Antigravity
Tools1426