mcpField
V
Vongola

Vongola

Local
qompass.aiCloud & Infra0Updated 1w ago
RepositoryVisit website

About Vongola

Vongola is a reverse proxy and web server built on Pingora 0.9.0, with read-only-first instrumentation for TLS gateway operators. It also integrates Prometheus metrics, a live dashboard, and multiple network routing capabilities.

Key features

  1. 01SNI TLS termination and static hosting
  2. 02Health-checked upstream round-robin
  3. 03Post-quantum TLS 1.3
  4. 04NAT traversal and Tor onion services
  5. 05Proxy chains with no direct fallback
  6. 06Prometheus metrics and live dashboard

Use cases

  1. 01Inspect gateway, upstream, and certificate status
  2. 02Check proxy operations through instrumentation
  3. 03Configure NAT traversal or onion routing
  4. 04Route through proxy chains without direct fallback

MCP support

Vongola exposes a read-only-first MCP server, with operator mutations gated by authentication.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository
Packages
mcpbvongola-mcp-0.2.0-linux-x64.mcpb

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

Vongola

License: Apache 2.0

Vongola is Qompass AI's reverse proxy and web server — a clean-room rewrite on Pingora 0.9.0. It hosts qompass.ai, runs on a single small device, and scales across a fleet of small nodes (NVIDIA Jetson-class dev kits, thin/slim clients) sharing one versioned configuration bundle.

  • Hosting: SNI TLS termination, www→apex 308, static hosting with cache rules + gzip, proxied routes with health-checked round-robin upstreams.
  • Post-quantum TLS: TLS 1.3 only with ML-KEM hybrid key exchange — live-negotiated X25519MLKEM768 in smoke. Builds must link system OpenSSL ≥ 3.5 (see the book's TLS chapter for the vendored-OpenSSL trap).
  • Operator surfaces: MCP server (read-only-first, auth-gated mutations), signed A2A Agent Card, populated Prometheus metrics, and a live dashboard (NAT, Tor, chains, upstreams, certs).
  • NAT traversal: PCP / NAT-PMP / UPnP IGD, opt-in per listener, leased and released on shutdown.
  • Tor onion services: publish routes as v3 onion services. Vongola is never a Tor exit node — enforced in config validation, not just documented.
  • Proxy chains: SOCKS5h / HTTP CONNECT / Tor / vongola hops, DNS through the chain, fail closed (a dead hop is a 502, never a direct fallback).

Quickstart

cargo build --release
./target/release/vongola validate-config --config examples/qompass.yaml
./target/release/vongola serve --config examples/lean.yaml
bash scripts/smoke.sh   # full live smoke against loopback fixtures
📄 We advise you read the script BEFORE running it 😉 
#!/usr/bin/env bash
# /qompassai/vongola/scripts/quickstart.sh
# Qompass AI Quick Start Script
# Copyright (C) 2025 Qompass AI, All rights reserved
####################################################

Or, View the quickstart script.

Documentation

The mdBook in docs/src (build with mdbook build) covers architecture, the hosting/lean/fleet profiles, the TLS/PQC posture with negotiation evidence, MCP/A2A, NAT, Tor, chains, the dashboard, a configuration reference, the operations runbook, the Homa and Mojo verdicts, and the feature accounting against the previous tree. SPEC.md is the clean-room contract the implementation was written against.

License

Apache-2.0. Copyright 2026 Qompass AI.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.