"namespace:91.174.133.8" matching MCP servers:

Enables read-only Kubernetes cluster inspection through MCP, with namespace allow/deny and resource block policies enforced before any API call.

Retrieves logs from Datadog for a specified Kubernetes cluster and namespace, enabling analysis by Claude through natural language queries.

A TypeScript MCP server starter kit supporting stdio and HTTP/SSE transports. Includes tools for system metrics, HTTP fetching with URL restrictions, and temporary key-value memory with namespace and TTL support.

Enables AI models to query and analyze Kubernetes cluster logs through Grafana Loki, supporting semantic operations like error aggregation and pod restart detection. It provides tools for regex-based log searching and namespace discovery to facilitate natural language troubleshooting.

Ships only the MCP server, not the recorder. Recording works by wrapping a process on the host — a local proxy, a PATH shim, a shadow git index. None of that survives a container boundary, so orca record inside here would watch an empty namespace. What does travel is the read side: the six MCP tools serve runs that already exist on disk, so a client mounts its .orca directory and r

Fronts many downstream MCP servers through one session, presenting a unified tool namespace with collision resolution, fleet-wide allow/deny/hide policy, per-tool rate limits, centralized audit logging, Prometheus metrics, and bearer-key auth at the edge. Supports both stdio drop-in and Streamable HTTP deployment so agents point at a single endpoint instead of N servers.