- Explore MCP Servers
- mcp-servers-registry
Mcp Servers Registry
What is Mcp Servers Registry
mcp-servers-registry is a repository that holds the source code for all MCP servers managed by Acuvity, providing a centralized location for development and maintenance.
Use cases
Use cases for mcp-servers-registry include deploying secure MCP servers for data processing, managing agent interactions in a controlled environment, and ensuring compliance with security policies in sensitive applications.
How to use
To use mcp-servers-registry, developers can clone the repository and utilize the provided sources to deploy and manage their MCP servers using the Acuvity Runtime Container (ARC) for enhanced security and simplified operations.
Key features
Key features of mcp-servers-registry include built-in security measures like isolated execution, non-root by default, immutable runtime, version pinning, CVE scanning, and integration with Minibridge for runtime protection and policy compliance.
Where to use
mcp-servers-registry is primarily used in environments that require secure and efficient management of MCP servers, such as in critical agentic systems, enterprise applications, and cloud-based infrastructures.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Overview
What is Mcp Servers Registry
mcp-servers-registry is a repository that holds the source code for all MCP servers managed by Acuvity, providing a centralized location for development and maintenance.
Use cases
Use cases for mcp-servers-registry include deploying secure MCP servers for data processing, managing agent interactions in a controlled environment, and ensuring compliance with security policies in sensitive applications.
How to use
To use mcp-servers-registry, developers can clone the repository and utilize the provided sources to deploy and manage their MCP servers using the Acuvity Runtime Container (ARC) for enhanced security and simplified operations.
Key features
Key features of mcp-servers-registry include built-in security measures like isolated execution, non-root by default, immutable runtime, version pinning, CVE scanning, and integration with Minibridge for runtime protection and policy compliance.
Where to use
mcp-servers-registry is primarily used in environments that require secure and efficient management of MCP servers, such as in critical agentic systems, enterprise applications, and cloud-based infrastructures.
Clients Supporting MCP
The following are the main client software that supports the Model Context Protocol. Click the link to visit the official website for more information.
Content
🚀 Secure and Simplify Your MCP Server with ARC
At Acuvity, security is essential—especially for MCP servers powering critical agentic systems. That’s why we created ARC (Acuvity Runtime Container): a secure, streamlined Docker runtime designed specifically for MCP servers.
ARC provides an isolated, robust environment, adding strong security measures, simplified deployment, and seamless remote access—letting you focus on your MCP server’s capabilities, not operational complexities.
🔧 Why ARC?
ARC securely hosts your MCP servers with built-in runtime protection, secure connectivity, and effortless deployment:
🔐 Built-in Security
- Isolated Execution: Run securely in isolated containers, preventing lateral movement.
- Non-root by Default: Minimize risks by enforcing least-privilege.
- Immutable Runtime: Read-only filesystem ensures tamper-proof operations.
- Version Pinning & CVE Scanning: Consistent and secure deployments with proactive vulnerability detection (via Docker Scout).
- SBOM & Provenance: Traceable builds for complete supply chain transparency.
🛡️ Runtime Protection with Minibridge
Minibridge integrates seamlessly with ARC to secure agent-to-MCP interactions, enforcing runtime integrity and policy compliance:
- Integrity Checks: Ensures authenticity with runtime component hashing.
- Threat Detection & Prevention with built-in Rego Policy:
- Covert‐instruction screening: Blocks any tool description or call arguments that match a wide list of “hidden prompt” phrases (e.g., “do not tell”, “ignore previous instructions”, Unicode steganography).
- Schema-key misuse guard: Rejects tools or call arguments that expose internal-reasoning fields such as note, debug, context, etc., preventing jailbreaks that try to surface private metadata.
- Sensitive-resource exposure check: Denies tools whose descriptions—or call arguments—that reference paths, files, or patterns typically associated with secrets (e.g., .env, /etc/passwd, SSH keys).
- Tool-shadowing detector: Flags wording like “instead of using” that might instruct an assistant to replace or override an existing tool with a different behavior.
- Cross-tool ex-filtration filter: Scans responses and tool descriptions for instructions to invoke external tools not belonging to this server.
- Credential / secret redaction mutator: Automatically replaces recognized tokens format with
[REDACTED]in outbound content.
ARC is the fortress. Minibridge is the guard.
Together, they securely connect and protect your MCP servers.
📦 What ARC Offers
- SBOM Validation: Automatic verification to prevent compromised deployments.
- Rego Policy Enforcement: Fine-grained governance using Open Policy Agent (OPA).
- Simplified Remote Connectivity: Effortlessly bridge your MCP server without custom protocols—Minibridge handles HTTP/SSE, WebSockets, and more.
- Kubernetes Integration: Quickly deploy into Kubernetes with Helm charts and sensible defaults.
Features comparisons
| 🚀 Feature | 🔹 MCP | 🔸 Minibridge | 📦 ARC (Acuvity Containers) | 🌟 ARC + Acuvity Platform |
|---|---|---|---|---|
| 🌐 Remote Access | ⚠️ HTTP/SSE Only | ✅ Built-in | ✅ Built-in | ✅ Built-in |
| 🔒 TLS Support | ❌ | ✅ Built-in | ✅ Built-in | ✅ Built-in |
| 📃 Tool integrity check | ❌ | ✅ Built-in | ✅ Built-in | ✅ Built-in |
| 📊 Visualization and Tracing | ❌ | ✅ Built-in | ✅ Built-in | ✅ Built-in |
| 🛡️ Isolation | ❌ | ⚠️ Basic | ✅ Built-in | ✅ Built-in |
| 🔐 Security Policy Management | ❌ | 👤 Custom Implementation | ⚠️ Basic | ✅ Built-in |
| 🕵️ Secrets Redaction | ❌ | 👤 Custom Implementation | ⚠️ Basic | ✅ Built-in |
| 🔑 Authorization Controls | ❌ | 👤 Custom Implementation | 👤 Custom Implementation | ✅ Built-in |
| 🧑💻 PII Detection and Redaction | ❌ | 👤 Custom Implementation | 👤 Custom Implementation | ✅ Built-in |
| 📌 Version Pinning | ❌ | ❌ | ✅ Built-in | ✅ Built-in |
| 🔍 Deep Multimodal Analysis & Redaction | ❌ | ❌ | ❌ | ✅ Built-in |
✅ Included | ⚠️ Partial/Basic Support | 👤 Custom User Implementation | ❌ Not Supported
✨ Contribute Your MCP Server to ARC!
Join our secure MCP ecosystem by adding your server to ARC:
- Open a GitHub Issue: Use our simple issue template.
- Provide:
- 🌐 Source Link: Your app’s location (GitHub, npm, PyPI, etc.)
- ⚙️ Runtime Config: Environment variables or CLI arguments.
We’ll handle the rest—secure containerization, Minibridge integration, SBOM validation, and remote support.
Why Contribute?
- Enhanced Visibility: Instantly usable in secure, enterprise-grade deployments.
- Built-in Security: Benefit from ARC’s robust protections.
- Community Strength: Boost the secure and plug-and-play MCP ecosystem.
Dev Tools Supporting MCP
The following are the main code editors that support the Model Context Protocol. Click the link to visit the official website for more information.










