VIRP MCP Server — Cryptographic trust primitives for AI agents operating on live network infrastructure.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"virp-mcp-server","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# VIRP MCP Server **Cryptographic trust primitives for any AI agent.** Give your AI agent the ability to prove what it saw on your network. Every observation is HMAC-SHA256 signed at the point of collection, before the AI ever touches it. The AI cannot fabricate what the network never said. VIRP MCP Server exposes the [VIRP protocol](https://github.com/nhowardtli/virp) as standard [MCP](https://modelcontextprotocol.io) tools. Any MCP-compatible client — Claude, GPT, Ollama, OpenClaw, or your own agent — connects and gets signed, verified infrastructure observations out of the box. ## What This Solves Every AI operations platform on the market trusts its own telemetry implicitly. The AI says "I checked your firewall." Did it? Can you prove it? VIRP MCP Server adds a cryptographic trust layer between your AI agent and your infrastructure: ``` Any AI Agent (Claude, GPT, Ollama, h-cli, OpenClaw) │ │ MCP protocol (stdio or SSE) ▼ ┌─────────────────────┐ │ VIRP MCP Server │ ← You are here │ (Python) │ └────────┬────────────┘ │ TCP / Unix socket ▼ ┌─────────────────────┐ │ VIRP O-Node │ Isolated C daemon │ HMAC-SHA256 signing │ chain.db audit trail │ Device SSH access │ Key management └────────┬────────────┘ │ SSH ▼ ┌─────────────────────┐ │ Network Devices │ Cisco, Fortinet, Palo Alto, ... └─────────────────────┘ ``` The MCP server is a translation layer. It takes tool calls from your AI agent, forwards them to the VIRP O-Node, and returns cryptographically signed results. The O-Node does all signing — this server never touches keys. ## Quick Start ### Install ```bash pip install virp-mcp-server ``` Or from source: ```bash git clone https://github.com/nhowardtli/virp.git cd virp/mcp-server pip install -e . ``` ### Configure ```bash # Point to your O-Node (TCP via socat bridge) export VIRP_ONODE_HOST=10.0.0.211 export VIRP_ONODE_PORT=9999 # Or use Unix socket…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.