MCP server for Keysight CyPerf network testing platform
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":"cyperf-mcp","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.
# CyPerf MCP Server > **Experimental Release** — This package is under active development. Tool names, parameters, and behaviors may change significantly in future versions without backward compatibility. Do not build production automation on the current API surface without expecting to adapt to breaking changes. An [MCP](https://modelcontextprotocol.io/) (Model Context Protocol) server that exposes [Keysight CyPerf](https://www.keysight.com/us/en/products/network-test/protocol-load-test/cyperf.html) network performance and security testing functionality as **100 tools** across 15 categories. AI assistants connected via MCP can orchestrate CyPerf tests, manage agents, analyze results, and perform security testing — all through natural language. ## Quick Start ### Prerequisites - Python 3.10+ - Access to a CyPerf controller ### Installation ```bash python -m venv .venv source .venv/bin/activate pip install cyperf-mcp ``` **From source** (for development): ```bash git clone https://github.com/Keysight/cyperf-mcp.git && cd cyperf-mcp python -m venv .venv source .venv/bin/activate pip install -e . ``` ### Configuration Before running, create a configuration file with your CyPerf controller connection details. **Config file location** (checked in order): 1. Path passed via `CYPERF_CONFIG` environment variable 2. `~/.cyperf/config.json` (default) Run `cyperf-mcp --help` to see this information from the command line. **Multi-profile format** (recommended — manage multiple controllers): ```json { "default_profile": "lab1", "profiles": { "lab1": { "host": "https://10.36.75.100", "refresh_token": "eyJhbGciOi...", "verify_ssl": false }, "cloud": { "host": "https://cyperf-cloud.example.com", "username": "admin", "password": "secret", "verify_ssl": true } } } ``` **Single-profile shorthand** (one controller): ```json { "host": "https://10.36.75.100", "refresh_token": "eyJhbGciOi...", "verify…
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.