Wire.Band MCP server — give your AI agent anomaly detection, drift scoring and compression on any structured data. Free key provisioned on first use.
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":"wire-band-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.
# wire-band-mcp MCP (Model Context Protocol) server for Wire.Band. Give your AI agent anomaly detection, semantic drift scoring and compression on any structured data it touches: logs, API responses, telemetry, event streams. Works in Claude Code, Claude Desktop, or any MCP client. **No signup step.** A free API key (100,000 events/month) is provisioned automatically the first time the server runs, and stored in `~/.config/wire-band/credentials.json`. ## Quick start ### Claude Code ```bash claude mcp add wire-band -- uvx wire-band-mcp ``` Then ask Claude something like *"analyze this log file with wire-band and tell me what looks unusual"*. ### Claude Desktop ```json { "mcpServers": { "wire-band": {"command": "uvx", "args": ["wire-band-mcp"]} } } ``` ### Set up ahead of time (optional) ```bash uvx wire-band-mcp init # gets your free key now and prints setup steps ``` Or get a key in the browser at [wire.band/signup](https://wire.band/signup) and pass it as `WIREBAND_API_KEY`. ## Tools - **`analyze_data(data, topic?, domain?, format?)`**: run a payload through Wire.Band. It takes one record or a JSON array of up to 1000, as JSON, YAML or XML. Returns the detected format, how much the data shrank, how the records classify, any anomalies raised, and the domain's drift report. Every call adds to your account's baseline, so later data gets flagged against earlier data. - **`get_anomaly_status(domain?, limit?)`**: recent anomaly events for your account - **`get_drift_score(domain?)`**: semantic drift score (KL divergence from baseline) - **`get_cache_stats()`**: semantic cache size, hit rate, per-domain breakdown Domains: `iot_telemetry`, `agent_logs`, `fintech`, `healthcare`, `energy`, `default`. Each API key gets its own isolated tenant. Your data, baselines and anomaly log are never shared with another account. ## Environment variables | Variable | Default | Description | |---|---|---| | `WIREBAND_API_KEY` | — | Use this key instead …
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.