Open Traffic Generator - Model Context Protocol
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":"iflow-mcp-h4ndzdatm0ld-otg-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.
# Open Traffic Generator MCP Server [](https://codecov.io/gh/h4ndzdatm0ld/otg-mcp) [](https://github.com/h4ndzdatm0ld/otg-mcp/actions/workflows/ci.yml) MCP (Model Context Protocol) server implementation for Open Traffic Generator (OTG) API. ## Overview The OTG MCP Server is a Python-based Model Context Protocol (MCP) to provide access to Open Traffic Generators (OTG) through a unified API. The server connects to traffic generators using a standardized configuration interface, providing a consistent way to interact with any traffic generator that respects OpenTrafficGenerator Models. ## Features - **Configuration-Based Connection**: Connect to traffic generators via standardized configuration - **OTG API Implementation**: Complete implementation of the Open Traffic Generator API - **Multi-Target Support**: Connect to multiple traffic generators simultaneously - **Type-Safe Models**: Pydantic models for configuration, metrics, and response data ## Documentation Comprehensive documentation is available in the `docs/` directory: - [Ixia-C Deployment Guide](./docs/deployIxiaC_simple_testing.md): Simple testing with Ixia-C Community Edition - [GitHub Flow](./docs/github-flow.md): Guidelines for GitHub workflow ## Configuration The OTG MCP Server uses a JSON configuration file to define traffic generator targets and their ports. Example configuration (`examples/trafficGeneratorConfig.json`): ```json { "schemas": { "schema_path": "/path/to/custom/schemas/directory" }, "targets": { "traffic-gen-1.example.com:8443": { "ports": { "p1": { "location": "localhost:5555", "name": "p1" }, "p2": { "location": "localhost:5556", "name": "p2" } } }, "traffic-gen-2.example.com:8443": { "ports": { …
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.