jarvis-registry
Health Gecti
- License — License: Apache-2.0
- Description — Repository has a description
- Active repo — Last push 0 days ago
- Community trust — 238 GitHub stars
Code Basarisiz
- rm -rf — Recursive force deletion command in agents/a2a/deploy_live.sh
- rm -rf — Recursive force deletion command in agents/a2a/deploy_local.sh
Permissions Gecti
- Permissions — No dangerous permissions requested
This tool is an enterprise-grade gateway and orchestration platform that connects AI copilots and autonomous agents to internal company tools. It provides a secure, centralized hub for identity management, access control, and workflow observability.
Security Assessment
This gateway is designed to handle highly sensitive data by managing authentication (OAuth 2.0/OIDC) and routing external AI requests to internal enterprise systems, inherently carrying a high-impact risk profile. The automated scan identified two failures regarding `rm -rf` commands within deployment scripts (`agents/a2a/deploy_live.sh` and `agents/a2a/deploy_local.sh`). While potentially standard cleanup operations for a local or live environment, these forceful deletion commands warrant a manual review to ensure they do not unexpectedly target critical directories. No hardcoded secrets or dangerous application permissions were detected. Overall risk: Medium.
Quality Assessment
The project demonstrates strong health and active maintenance, evidenced by repository updates as recent as today. It utilizes the well-respected Apache-2.0 license, making it highly suitable for enterprise integration. With nearly 240 GitHub stars, it exhibits a solid and growing level of community trust for an early-stage infrastructure tool.
Verdict
Use with caution — the core platform offers excellent security features and active maintenance, but developers should manually review the deployment scripts before executing them due to the flagged shell commands.
Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure MCP/Agent gateway with built-in identity, access control, and full observability.
Connect any AI copilot or autonomous agent to your enterprise tools — through a single, secure MCP gateway with built-in identity, access control, and full observability.
What is Jarvis Registry?
Jarvis Registry is an open-source, enterprise-grade MCP (Model Context Protocol) and A2A Agent Gateway and Workflow Orchestration platform built by ASCENDING Inc.
It solves one of the hardest problems in enterprise AI: giving AI copilots and autonomous agents secure, governed access to internal tools and data — without fragmented integrations or security blind spots.
| Capability | Description |
|---|---|
| MCP Gateway & Reverse Proxy | Single authenticated entry point for all AI clients and agents using MCP over SSE or Streamable HTTP |
| AI Copilot Integration | Connect Cursor, Claude Desktop, GitHub Copilot, VS Code, and any MCP-compatible copilot to enterprise tools |
| A2A Agent Orchestration | Register and manage autonomous agents; orchestrator agents coordinate worker agents through the same secure gateway |
| Identity & Access Management | OAuth 2.0/OIDC with Keycloak, Amazon Cognito, and Microsoft Entra ID — no custom auth code needed |
| Fine-Grained Access Control | ACL engine enforces scope-based, role-based permissions down to the individual tool level |
| Skill & Context-Based Discovery | Semantic search over skills, descriptions, and tags so agents and copilots find the right MCP server or A2A agent at runtime |
| Audit & Observability | Full request logging, OpenTelemetry tracing, and Prometheus metrics |
▶ Watch the demo — click to open on YouTube
Quick Start
# Clone the repository
git clone https://github.com/ascending-llc/jarvis-registry.git
cd jarvis-registry
# Copy and configure environment
cp .env.example .env
# Edit .env with your identity provider credentials
# Setup Python Virtual Environment
uv sync --all-packages
source .venv/bin/activate
# Start all services
docker compose --profile full up -d
# Open the registry UI
open http://localhost:80
See the full Get Started guide for detailed instructions.
Documentation
Full documentation is available at ascending-llc.github.io/jarvis-registry:
| Section | Description |
|---|---|
| Why Use Jarvis Registry | Benefits, use cases, and competitive advantages |
| Get Started | Installation, configuration, and first run |
| Authentication | IdP setup for Keycloak, Cognito, and Entra ID |
| Core Design | Architecture, RBAC, ACL, federation, and A2A |
| API Reference | REST API and MCP endpoint documentation |
Deployment
Cloud-native deployment guides are available for:
- AWS — EKS
- Azure — AKS
- GCP — GKE
- Docker Compose — Full local stack in under 5 minutes
Contributing
We welcome contributions! Please read our Contributing Guide and Code of Conduct before submitting pull requests.
For security vulnerabilities, contact [email protected] — do not open a public issue.
Acknowledgments
Jarvis Registry builds upon the excellent foundational work of the agentic-community/mcp-gateway-registry project. We are grateful to those contributors for establishing the core MCP gateway patterns that made this enterprise evolution possible.
License
Licensed under the Apache 2.0 License — see the LICENSE file for details.
⭐ Star this repository if it helps your organization!
Get Started | Documentation | Website | YouTube | LinkedIn
Yorumlar (0)
Yorum birakmak icin giris yap.
Yorum birakSonuc bulunamadi