"Ingress" matching MCP servers:

Provides AI ingress governance by masking prompts, classifying risk, and enforcing tool policies before agent calls reach model providers or sandboxes.

Bridge between IITC and MCP agents, enabling AI assistants to interact with Ingress Intel: view map, count portals, track players, and communicate via COMM without manual input.

An MCP server that gives AI assistants direct access to Kubernetes clusters for pod management and network debugging (DNS, NetworkPolicy, ingress, service mesh) and correlates Dynatrace observability with OpenTelemetry self-monitoring, which automatically ships traces, metrics, and logs to Dynatrace.

Enables a single MCP connector to route requests to independent local Chat and Codex runtimes, supporting workspace operations, process control, reviews, browser-backed tasks, and Codex workflows through one public ingress.

Enables AI agents to operate a LiveKit deployment, managing rooms, tokens, participants, data messages, egress/ingress, and hackathon workshops with one-call room setup, status, broadcast, and teardown tools.