{"id":"krutsko-istio-mcp-server","name":"istio-mcp-server","homepage":null,"repo_url":"https://github.com/krutsko/istio-mcp-server","category":"infrastructure","subcategories":[],"tags":["mcp","istio","kubernetes","envoy","read-only","observability","devtools","networking"],"what_it_does":"Provides an MCP server (Model Context Protocol) exposing read-only querying tools for Istio resources and related Envoy proxy configuration/status from Kubernetes clusters.","use_cases":["AI assistants that need to inspect Istio configuration (VirtualServices, DestinationRules)","Auditing and troubleshooting Istio routing/traffic policies without modifying cluster state","Generating summaries of service-mesh hosts and proxy configuration snapshots for debugging","Inspecting Envoy clusters/listeners/routes/endpoints/bootstrap and proxy status via a non-destructive interface"],"not_for":["Making configuration changes to Istio resources","Use cases requiring write access or mutating operations","Environments that cannot grant appropriate Kubernetes permissions to read Istio/Envoy-related resources","High-assurance compliance workflows where detailed guarantees about authorization boundaries and logging are required but not documented"],"best_when":"You want read-only visibility into Istio/Envoy configuration for Kubernetes workloads, and you plan to connect an MCP client (STDIO/SSE/HTTP) to query resources on demand.","avoid_when":"You need strict evidence of secure authentication/authorization controls beyond Kubernetes RBAC, or you cannot provide kubeconfig/cluster read permissions.","alternatives":["Use kubectl/istioctl directly (manual inspection)","Use Kubernetes/istio APIs via a custom read-only client","Other MCP servers or internal tooling that provide read-only service-mesh visibility"],"af_score":46.8,"security_score":39.2,"reliability_score":23.8,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T21:21:20.931672+00:00","interface":{"has_rest_api":true,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":null,"has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Kubernetes RBAC via provided kubeconfig context (implied)"],"oauth":false,"scopes":false,"notes":"The README does not describe any additional application-level auth for the MCP server; access control is likely intended to be enforced by Kubernetes RBAC using the kubeconfig provided to the process."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information provided; appears to be an open-source MIT project."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":46.8,"security_score":39.2,"reliability_score":23.8,"mcp_server_quality":70.0,"documentation_accuracy":60.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":55.0,"rate_limit_clarity":0.0,"tls_enforcement":40.0,"auth_strength":35.0,"scope_granularity":25.0,"dependency_hygiene":50.0,"secret_handling":50.0,"security_notes":"Read-only design is claimed, reducing risk of configuration modification. However, the README does not document transport/authentication for the MCP server endpoints (SSE/HTTP), nor does it specify how kubeconfig credentials are handled or whether sensitive data is redacted in logs. Authorization boundaries therefore appear to rely primarily on Kubernetes RBAC. TLS requirements and rate limiting are not described.","uptime_documented":0.0,"version_stability":30.0,"breaking_changes_history":40.0,"error_recovery":25.0,"idempotency_support":"true","idempotency_notes":"Tools are described as read-only queries; repeated calls should be safe and non-destructive. Exact server-side idempotency semantics and caching are not documented.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["MCP server security is likely dependent on kubeconfig permissions; MCP clients should not assume fine-grained authorization within the MCP layer itself.","Tool availability/performance may depend on cluster access and existence of Istio resources in the target namespaces.","SSE/HTTP modes may require network/firewall access; README does not document authentication for these endpoints."]}}