"namespace:91.174.133.8" matching MCP servers:

Enables AI agents to securely read and write SAP ABAP development objects via the ADT REST API, enforcing policy-based guardrails such as package/namespace allow-lists, read-only mode, human approvals, and audit logging.

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.

Enables multi-user, per-namespace storage of AES-256-GCM-encrypted credentials (SSH, web, API, DB) managed through a web console with TOTP 2FA, and lets AI clients save, list, retrieve, or server-side invoke those secrets over a remote Streamable-HTTP endpoint without ever exposing the values in chat.

A security gateway that sits between an MCP client and real MCP servers, routing every tool call through namespace isolation, definition pinning, argument and rate policies, taint tracking, and response injection checks. It blocks tool shadowing, rug pulls, hidden Unicode payloads, path traversal, and exfiltration of private data to outside channels, while logging each decision and requiring out-of-band human approval for sensitive calls.

Enables connecting multiple remote HTTP MCP servers through a single local stdio endpoint, handling OAuth authentication, token refresh, and namespace-scoped tools.

Gives AI agents a shared, encrypted memory store accessible over MCP, with per-agent keys, per-namespace permissions, history and revert, attachments, and semantic search that handles Czech as well as English. Memories, agents, network access, and HTTPS can be managed through a self-hosted admin web on the same port, with backups being simply copies of the encrypted data file.