# AudD Music Recognition (remote · mcp.audd.io)

Music recognition with AudD: identify songs, monitor streams, call the API, plus account tools

- Trust score: 54/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.audd.io`: 54/100 (this document), [markdown](https://verifymcp.io/servers/io-audd-audd/mcp.md), [page](https://verifymcp.io/servers/io-audd-audd/mcp)

## Channel facts

- Endpoint: `https://mcp.audd.io`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.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-05.

- **Endpoint Security**: 100/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 4 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the AudD Music Recognition MCP server?

AudD Music Recognition is a hosted endpoint at https://mcp.audd.io/, 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 io-audd-audd 'https://mcp.audd.io/'
```

### Cursor

```json
{
  "mcpServers": {
    "io-audd-audd": {
      "url": "https://mcp.audd.io/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-audd-audd": {
      "type": "http",
      "url": "https://mcp.audd.io/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-audd-audd]
url = "https://mcp.audd.io/"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add io-audd-audd --url 'https://mcp.audd.io/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-audd-audd:
    url: "https://mcp.audd.io/"
```

### Netclaw

```json
{
  "McpServers": {
    "io-audd-audd": {
      "Transport": "http",
      "Url": "https://mcp.audd.io/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-audd-audd -t streamable-http -u 'https://mcp.audd.io/'
```

### Other

```json
{
  "mcpServers": {
    "io-audd-audd": {
      "type": "http",
      "url": "https://mcp.audd.io/"
    }
  }
}
```

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-05 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-04 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-03 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-02 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-11-01 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-31 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-30 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

### 2026-10-29 (score 54, 0)

- [functional] This server's schema is too large to store in full, so we cannot compare its tools day to day

## MCP tools (0)

No tool schema has been captured from this endpoint yet.

## Diagnostics

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

## Score history

- 2026-11-05: 54
- 2026-11-04: 54
- 2026-11-03: 54
- 2026-11-02: 54
- 2026-11-01: 54
- 2026-10-31: 54
- 2026-10-30: 54
- 2026-10-29: 54
- 2026-10-28: 54
- 2026-10-27: 54
- 2026-10-26: 54
- 2026-10-25: 54
- 2026-10-24: 54
- 2026-10-23: 54
- 2026-10-22: 54
- 2026-10-21: 54
- 2026-10-20: 54
- 2026-10-19: 54

## Common questions

### What is the AudD Music Recognition MCP server?

AudD Music Recognition is an MCP server listed in the public MCP registry as io.audd/audd. Music recognition with AudD: identify songs, monitor streams, call the API, plus account tools. This page covers its hosted endpoint (https://mcp.audd.io).

### Is the AudD Music Recognition MCP server safe to use?

AudD Music Recognition scores 54 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.

### Does the AudD Music Recognition MCP server require authentication?

Yes. AudD Music Recognition asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the AudD Music Recognition MCP server still maintained?

AudD Music Recognition is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.audd.io/
- Website: https://docs.audd.io/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/io-audd-audd/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-audd-audd/mcp.json
- HTML version of this page: https://verifymcp.io/servers/io-audd-audd/mcp