# ai.echoteka/mastering (remote · echoteka.ai)

Audio mastering for AI agents: LUFS analysis, Suno artifact cleanup, free daily master.

- Trust score: 78/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `echoteka.ai`: 78/100 (this document), [markdown](https://verifymcp.io/servers/ai-echoteka-mastering/echoteka.md), [page](https://verifymcp.io/servers/ai-echoteka-mastering/echoteka)

## Channel facts

- Endpoint: `https://echoteka.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.5.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1588 tokens (~122/item across 13 items; 9 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 89% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the ai.echoteka/mastering MCP server?

ai.echoteka/mastering is a hosted endpoint at https://echoteka.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-echoteka-mastering 'https://echoteka.ai/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-echoteka-mastering": {
      "url": "https://echoteka.ai/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-echoteka-mastering": {
      "type": "http",
      "url": "https://echoteka.ai/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-echoteka-mastering]
url = "https://echoteka.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-echoteka-mastering": {
      "type": "remote",
      "url": "https://echoteka.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-echoteka-mastering --url 'https://echoteka.ai/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-echoteka-mastering:
    url: "https://echoteka.ai/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-echoteka-mastering": {
      "Transport": "http",
      "Url": "https://echoteka.ai/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-echoteka-mastering -t streamable-http -u 'https://echoteka.ai/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-echoteka-mastering": {
      "type": "http",
      "url": "https://echoteka.ai/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 75, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 74)

First indexed and scored.

## MCP tools (9)

### `get_service_info` (~39 tokens)

Service info

What Echoteka does, what is free, what a credit buys, and where the rules live. Call once at the start of a session.

### `list_presets` (~79 tokens)

List mastering presets

All mastering presets with their target loudness in LUFS. Call this to get the exact preset keys that master_track and batch_master accept. Use preview_styles instead when you want to HEAR 2-6 of them on the actual track before choosing, and get_service_info when you need the wider service manifest rather than the preset list. Free.

Output parameters:

- `count` (integer)
- `presets` (array)

### `check_limits` (~41 tokens)

Check quota and balance

What this caller may do right now: free master left today and when it resets, credit balance, upload cap, whether advanced modules are available. Call before mastering.

Output parameters:

- `can_master_now` (boolean)
- `free` (object)
- `max_batch_total_mb_via_mcp` (integer)
- `max_upload_mb` (integer)
- `max_upload_mb_via_mcp` (integer): effective per-file ceiling for THIS channel
- `result_retention_days` (integer)
- `tokens_balance` (integer)

### `analyze_track` (~121 tokens)

Analyze a track

Measure integrated LUFS, sample peak, duration, sample rate and stereo correlation without processing. Free, a couple of seconds. Run this before choosing a preset. Note: true peak and loudness range are NOT part of this fast pass — they are measured on the result and come back from get_job.

Input parameters:

- `audio_url` (string, required): Public https URL of the audio file (wav/mp3/flac/m4a). A share link to the page works too — Suno/Udio song pages, Google Drive and Dropbox links are resolved to the file automatically.

Output parameters:

- `channels` (integer|null)
- `duration_sec` (number|null)
- `genre_suggestion`
- `lufs` (number|null)
- `peak_dbfs` (number|null)
- `sample_rate` (integer|null)
- `stereo_correlation` (number|null)
- `true_peak_db` (number|null): null in the fast pass; see get_job for the measured value

### `clean_ai_trace` (~158 tokens)

Clean AI generator artifacts

Remove the marks an AI generator leaves in the audio (narrow tones above 15 kHz, level jumps at block seams, fixed spectral peaks); loudness and tone stay as they are. It does not hide that a track is AI-made - disclose AI use wherever a platform asks. Free, never spends a credit. Returns a job id - poll get_job.

Input parameters:

- `audio_url` (string, required): Public https URL of the audio file (wav/mp3/flac/m4a). A share link to the page works too — Suno/Udio song pages, Google Drive and Dropbox links are resolved to the file automatically.
- `out_format` (string)
- `sensitivity` (number): 0-1, default server-side.

Output parameters:

- `job_id` (string)

### `preview_styles` (~139 tokens)

Compare presets on 24 seconds

Master the middle 24 s of the track in 2-6 presets at once and get each one's loudness plus a listen link. FREE (6 per day). Use this instead of guessing a preset, and instead of spending a credit to 'try' one.

Input parameters:

- `audio_url` (string, required): Public https URL of the audio file (wav/mp3/flac/m4a). A share link to the page works too — Suno/Udio song pages, Google Drive and Dropbox links are resolved to the file automatically.
- `styles` (array): Preset keys from list_presets. Default: edm, pop, rnb, standard.

Output parameters:

- `job_id` (string)
- `poll_with` (string)
- `preview_url_template` (string)
- `styles` (array)

### `master_track` (~448 tokens)

Master a track

Master one track. Uses 1 CREDIT when the account has a balance; otherwise it runs on the free quota (1 free master per day (UTC), without advanced modules). Returns a job id immediately - poll get_job (typical 20-60 s, up to 10 min with restoration). The source is fetched by this server, so the ceiling here is 100 MB per file. Pass dry_run=true first if you want to see what would be used and the effective settings before anything is spent.

Input parameters:

- `audio_url` (string, required): Public https URL of the audio file (wav/mp3/flac/m4a). A share link to the page works too — Suno/Udio song pages, Google Drive and Dropbox links are resolved to the file automatically.
- `bitrate` (integer): MP3: 128/192/256/320; OPUS: 128/192.
- `denoise_strength` (number): Noise reduction, 0-1. 0 disables.
- `dither_type` (string): Dither for 16-bit WAV output: tpdf (default), ns_e or ns_itu (noise-shaped).
- `dry_run` (boolean): Do not master: report what this call would use and what settings would apply. Nothing is charged, the file is not even downloaded.
- `intensity` (number): Multiplier on the preset's multiband compression: 1.0 as designed, 0.5 gentler, 1.5 denser. Values outside 0.5-1.5 are clamped.
- `out_format` (string)
- `remove_watermark` (boolean): Also run AI artifact cleanup first. Free.
- `restore_dynamics` (boolean): Open up a brickwalled source before mastering (pairs with style unlimiter).
- `style` (string): Preset key from list_presets, e.g. edm, hiphop, podcast, unlimiter. Default standard.
- `target_lufs` (number): Override the preset target, e.g. -14 for Spotify.
- `webhook_url` (string): Public https URL to POST the result to instead of polling.

Output parameters:

- `dry_run` (boolean)
- `job_id` (string)
- `nothing_was_charged` (boolean)
- `poll_with` (string)
- `tokens_balance` (integer)
- `would_charge` (string)

### `batch_master` (~301 tokens)

Master an album or a batch

Master up to 10 tracks in one call with the same settings. Needs N CREDITS for N tracks, or N free runs - not one. album_mode (default true) levels the tracks RELATIVE to each other: the loudest hits the target exactly, the others keep their offsets, so a quiet interlude is not inflated to single level. Limits: 10 tracks, 100 MB per file and 300 MB per call (this server's own caps, for memory). A big album takes minutes - send fewer, longer tracks per call rather than all at once. Returns one job id per track - poll each with get_job. Pass dry_run=true to see what would be used and the settings before anything is spent.

Input parameters:

- `album_mode` (boolean): Keep relative loudness between tracks. Default true. Set false for unrelated singles.
- `audio_urls` (array, required): Public https URLs, in album order.
- `bitrate` (integer): MP3: 128/192/256/320; OPUS: 128/192.
- `dry_run` (boolean): Report what would be used and the settings without mastering and without downloading anything.
- `out_format` (string)
- `remove_watermark` (boolean): Also run AI artifact cleanup first. Free.
- `style` (string): Preset key from list_presets.
- `target_lufs` (number): Target for the LOUDEST track in album mode.

Output parameters:

- `album_mode_requested` (boolean)
- `album_offsets_applied` (boolean)
- `dry_run` (boolean)
- `enough_capacity` (boolean)
- `job_ids` (array)
- `jobs` (array)
- `nothing_was_charged` (boolean)
- `poll_with` (string)
- `tracks` (array): job_id, filename, source_url, target_lufs and album_lufs_offset as APPLIED by the server
- `would_charge` (string)

### `get_job` (~132 tokens)

Get job status

Status, progress and result metrics (after_lufs, true_peak_db, lra, platform_ready) for a mastering, cleanup or preview job. For previews it returns each style with its loudness and a listen link. When a master is done it also returns download_url - a signed link that works without credentials for about an hour. Free.

Input parameters:

- `job_id` (string, required): Job id returned by master_track, clean_ai_trace or preview_styles; batch_master returns one per track in job_ids. Not a URL or a filename: 1-64 chars of A-Z a-z 0-9 _ -

Output parameters:

- `after_lufs` (number|null)
- `download_url` (string): signed, ~1 h, works without credentials
- `download_url_expires_in` (integer)
- `error` (string|null)
- `lra` (number|null)
- `platform_ready`
- `progress` (integer|null)
- `result_url` (string)
- `status` (string)
- `true_peak_db` (number|null)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-echoteka-mastering/echoteka#diagnostics

## Score history

- 2026-11-21: 78
- 2026-11-20: 77
- 2026-11-19: 77
- 2026-11-18: 77
- 2026-11-17: 76
- 2026-11-16: 76
- 2026-11-15: 75
- 2026-11-14: 75
- 2026-11-13: 74

## Common questions

### What is the ai.echoteka/mastering MCP server?

ai.echoteka/mastering is an MCP server listed in the public MCP registry as ai.echoteka/mastering. Audio mastering for AI agents: LUFS analysis, Suno artifact cleanup, free daily master. This page covers its hosted endpoint (https://echoteka.ai/mcp).

### Is the ai.echoteka/mastering MCP server safe to use?

ai.echoteka/mastering scores 78 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the ai.echoteka/mastering MCP server expose?

ai.echoteka/mastering exposes 9 tools: get_service_info, list_presets, check_limits, analyze_track, clean_ai_trace, and 4 more. Their descriptions and schemas cost roughly 1,458 tokens of context every time the server is loaded.

### Does the ai.echoteka/mastering MCP server require authentication?

No. We connected to ai.echoteka/mastering without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the ai.echoteka/mastering MCP server still maintained?

ai.echoteka/mastering is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the ai.echoteka/mastering MCP server?

VerifyMCP ran 14 checks on ai.echoteka/mastering, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://echoteka.ai/mcp
- Website: https://echoteka.ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/ai-echoteka-mastering/echoteka.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-echoteka-mastering/echoteka/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ai-echoteka-mastering/echoteka.json
- HTML version of this page: https://verifymcp.io/servers/ai-echoteka-mastering/echoteka
