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
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
{
"mcpServers": {
"wire-band": {"command": "uvx", "args": ["wire-band-mcp"]}
}
}
Set up ahead of time (optional)
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 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 accountget_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 of the stored / auto-provisioned one |
WIREBAND_API_URL |
https://wire.band |
Backend URL. Point it at a self-hosted server if you run one |
WIREBAND_AUTO_SIGNUP |
1 |
Set to 0 to turn off automatic key provisioning |
WIREBAND_CREDENTIALS |
~/.config/wire-band/credentials.json |
Credentials file location |
WIREBAND_MCP_TRANSPORT |
stdio |
stdio | sse | streamable-http |
Installation without uvx
pip install wire-band-mcp
wire-band-mcp # or: python -m wire_band_mcp
Python 3.10+ required.
What this doesn't expose
This is a thin client over Wire.Band's tenant-scoped REST API, not a reimplementation. It returns derived signals only, never Wire.Band's internal encoding or compression internals.
Metadata
Release files for wire-band-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| wire_band_mcp-0.2.0.tar.gz | 7.5 kB | With provenance | Details for wire_band_mcp-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| wire_band_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for wire_band_mcp-0.2.0-py3-none-any.whl |
Total release size: 17.6 kB
Release files / wire_band_mcp-0.2.0.tar.gz
| Download URL | wire_band_mcp-0.2.0.tar.gz |
|---|---|
| Size | 7.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfda6c57f11d0f067cdbd0d3d048dbdd3953d38ef36301509ed92de907f3c5a0
|
|
BLAKE2b-256 checksum How to use checksums |
785b50dc50c61350ad8fe5d5c06b05189d3d9e7e1f693d2a0b5270028bdfd2cc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logRelease files / wire_band_mcp-0.2.0-py3-none-any.whl
| Download URL | wire_band_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 10.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
71713bb24fff5055aef0cbca41de992890821390a30314fe2a4ae92b55182e14
|
|
BLAKE2b-256 checksum How to use checksums |
3f6d365b3210fc76fbd682e89d7465b06cddfc974480478352c9a9bb88b3d1f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logSecurity for wire-band-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for wire_band_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 23, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.