"namespace:91.174.133.8" matching MCP servers:

Free Industry 4.0 / IIoT tools, no API key or account: lint MQTT Sparkplug B topics, check a Unified Namespace (UNS) for naming and hierarchy problems, and run an industrial AI-readiness diagnostic for manufacturing digital transformation and smart-factory projects. Works in Claude Code, Codex and any MCP client.

Enables driving Omniverse Kit apps (Isaac Sim, Isaac Lab) over MCP, allowing agents to control simulations, run Python, and call namespace-scoped tools via a single bridge.

Enables interactive Python execution with a persistent IPython kernel through MCP, retaining namespace state and providing structured output logs for agent and tool integrations.

Enables AI agents to inspect and operate a Kubernetes cluster safely, with read-only mode and namespace allowlist for mutations.

Provides evidence-first product naming tools for agents and founders, including domain registry checks, namespace searches, and finalist research with sources and timestamps.

An MCP server that proxies multiple MCP servers, allowing you to configure and access multiple MCP servers through a single endpoint with namespace support.

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

Industry 4.0 / IIoT AI agents for manufacturing: explain OEE losses per shift, triage machine alarms, find downtime root causes, prepare predictive-maintenance jobs and write shift reports from Unified Namespace (UNS), MQTT or historian data. Plus an industrial AI-readiness diagnostic and a vendor-neutral digital-transformation advisor. Works in Claude Code, Codex and any MCP client.

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.

Enables coding agents to store, search, update, and delete durable facts, preferences, decisions, and plans in a shared local SQLite database, along with per-namespace profile get/set and stats. Uses offline lexical FTS5 search so multiple agents working on the same project can share one memory store.

Enables LLM and AI-agent clients to operate a Nacos 3.0 control plane through MCP tools, resources, and prompts—covering configuration publishing, rollback, history and drift checks, namespace management, service discovery, instance registration/weighting, and cluster health probing. It supports stdio and SSE transports with Docker deployment, self-healing authentication, and syntax guardrails suited to asymmetric NAT environments.

Exposes ABLESTACK MOLD API through MCP tools with the mold_\* namespace, enabling direct CloudStack API calls, exploration, and debugging. Supports automatic API registration, async polling, parameter expansion, and signature debugging for comprehensive cloud infrastructure management.

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 standalone MCP gateway that multiplexes multiple backend MCP servers behind a single endpoint, supporting both HTTP and stdio transports. It allows users to dynamically manage backends at runtime and organizes tools using a configurable namespace prefix.

Self-hosted MCP proxy and aggregation platform. Register multiple upstream MCP servers and expose them through a single unified endpoint with namespace routing, multi-transport support (HTTP/SSE, stdio, OpenAPI→MCP), per-tool overrides, and a web admin UI.

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.

A read-only MCP server that gives AI assistants Roslyn-powered browsing of any C# solution, letting them list types by folder or namespace, read XML documentation, and retrieve method signatures, locations and bodies. This keeps queries targeted so agents pull only the exact slice of source they need instead of reading whole files into context.