# Lots of Sounds vs Slipstream

> Lots of Sounds scores 52.9 (D) to Slipstream's 50 (D) for music search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream
- Markdown: https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream.md (~4,300 tokens)
- Slim: https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream.min.md (~980 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-22

Lots of Sounds scores 52.9 (D) on agent readiness against Slipstream's 50 (D), and leads in 4 of 7 scored categories. Slipstream leads on reliability. Both do music search.

- Lots of Sounds: grade D, 52.9/100, rank #1071 of 1571. Markdown https://www.anchorterminal.com/tools/lotsofsounds.md · JSON https://www.anchorterminal.com/api/v1/tools/lotsofsounds.json
- Slipstream: grade D, 50/100, rank #1174 of 1571. Markdown https://www.anchorterminal.com/tools/slipstream.md · JSON https://www.anchorterminal.com/api/v1/tools/slipstream.json
- Best music and sound libraries for AI agents: https://www.anchorterminal.com/best/music-libraries/index.md
- All 21 music libraries comparisons: https://www.anchorterminal.com/compare/music-libraries/index.md

## Which one, for what

### Lots of Sounds (D)

Good for: An agent that needs short CC0 sound effects, ambience or loops with trim points and loudness for video, apps or games.

Ahead on:
- Schema & documentation, 79 against 50
- Agent ergonomics, 88 against 60
- Maintenance & community, 66 against 18
- Transparency & trust, 43 against 37

Watch for: No page says where the CC0 sounds come from or who recorded them, and the licence page leaves checking suitability to the user

### Slipstream (D)

Good for: An agent helping a Slipstream subscriber find, clip and clear music for video, or an enterprise issuing rate-card licences with approval.

Ahead on:
- Reliability, 80 against 40

Also in its favour:
- No incidents deducted, where Lots of Sounds loses 3 points for them

Watch for: An `initialize` with no token answered 401 on 22 November 2026, so the catalogue tools the docs call public were not reachable without signing in


## Why the edge

### Maintenance & community: Lots of Sounds +48

- Lots of Sounds (66): Closed service. The npm CLI 0.1.0 was published on 29 October 2026, 24 days ago (30). In the last 90 days the examples repository changed on 26 August and 21 September, the registry entry and TypeScript client appeared on 21 September, the privacy policy took effect on 19 October and the CLI shipped on 29 October, but none of these is a dated changelog entry (10 of 20). The blog's only changelog is March 2026, the roadmap lists a shipped MCP server as in progress, and support is team@lotsofsounds.com with a reply within one business day stated on the pricing page and a UserJot feedback board (6 of 15, closed-service reading). Listed in the official MCP registry as com.lotsofsounds/mcp, a reverse-DNS namespace on its own domain (15). The CLI has no install scripts and the TypeScript client has CI, but the CLI's source repository named on npm isn't public (5 of 10). 30 + 10 + 6 + 15 + 5 = 66.
- Slipstream (18): Closed-service reading. No dated API or MCP change could be read because the changelog loads by script and its feeds answered 405. The newest dated page about the MCP is the help centre guide of 3 August 2026, within 180 days (10 of 30). Dated changelog entries in the last 90 days unchecked (0 of 20). A changelog page that promises advance notice of breaking changes, support by chat and support@slipstreammusic.com with a stated 24 to 48 hour reply (8 of 15). No entry in the official MCP registry, and no official SDK (0 of 15). No package to judge (0 of 10). 10 + 0 + 8 + 0 + 0 = 18.

### Reliability: Slipstream +40

- Lots of Sounds (40): Graded on the hosted MCP server and the REST API beneath it. No status page found, only the words 'API status: operational' on the home page with no link (0). No readable incident history (5). Daily limits published with numbers, 2,500 for Pro and 50,000 for Enterprise, resetting at midnight UTC (15). The API reference documents 429 with `X-RateLimit-Reset` and asks for bounded exponential backoff on 429 and 5xx, and every call is a read (15). The home page claims a 99.9% uptime SLA, but the terms of 1 April 2026 say the service is as-is and availability isn't guaranteed, and no SLA document was found (0). Nothing is labelled beta and the registry entry is version 1.0.0, but the public roadmap still lists the MCP server as in progress (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.
- Slipstream (80): Atlassian Statuspage at status.slipstreammusic.com with Platform and API components and no MCP component (20). The history page and its RSS feed list no incidents, and the last 15 days each read no incidents reported (30). Partner quotas are daily and monthly with a burst limit per key, but the only numbers (1,000 a day, 30,000 a month) are an example usage block, and no limits are given for OAuth users (5 of 15). The licence endpoint returns 429 `throttled` with Retry-After and is safe to repeat for the same user, track and project, and async MCP tools are polled with identical arguments (15). No SLA found on the pages read; the main site could not be read (0). The MCP server and API carry no beta label (10). 20 + 30 + 5 + 15 + 0 + 10 = 80.

### Schema & documentation: Lots of Sounds +29

- Lots of Sounds (79): Public OpenAPI 3.1 spec with 7 operations, and typed JSON Schema inputs on all 5 MCP tools, read with one `tools/list` (25). llms.txt and llms-full.txt, plus a Copy Markdown option on each docs page (10). Tool descriptions say how search matches, when to call `download_sound` and that `get_profile` is only for identifying the account, with fewer when-not-to-use lines in the spec (14 of 20). Enums for category, sort and order, minimum and maximum on limit and page, required ids, and `additionalProperties: false` on every tool. Duration filters have no bounds (13 of 15). Examples in curl, JavaScript and Python and an error table with actions, but the spec's error schema is a single `error` string and the coded errors (`plan_required`, `rate_limited`) are documented for the CLI only (12 of 15). Paths are versioned `/api/v1` and the spec is 1.0.0, but the one dated changelog post is from March 2026 (5 of 15). The spec says 12,000+ sounds where llms.txt says 16,874, and tags use OR on the sample endpoint and AND on search. 25 + 10 + 14 + 13 + 12 + 5 = 79.
- Slipstream (50): The docs say tool inputs and outputs are typed, but `tools/list` could not be read because `initialize` answered 401, and the REST API has no OpenAPI file or other contract linked (10 of 25). No llms.txt (404) or Markdown docs for agents (0). The tools page states each tool's purpose and when to use it, for example `soundtrack_a_video` only when no video is attached and `get_track_download_url` as a download, not a licence (15 of 20). Filter values come from `get_search_filters`, `audio_type` takes three values and stems take separate id lists, but no schema was read (8 of 15). End-to-end flows for soundtracks, AudioVerify, allowlists and licences, and REST error tables with stable codes (12 of 15). REST paths are versioned (`/api/v4/`, `/api/v1/`) and a changelog page exists, but its entries load by script and its feeds answered 405 (5 of 15). 10 + 0 + 15 + 8 + 12 + 5 = 50.

### Agent ergonomics: Lots of Sounds +28

- Lots of Sounds (88): Five compact tools, about 5,000 characters of definitions (25). Search takes page and limit (up to 100), category, tags, duration bounds and sort, and returns total and totalPages (20). Errors are documented with a status, a meaning and an action, and 429 carries a reset time, though MCP error shapes were not seen because no tool was called (15 of 20). Every tool carries readOnlyHint, destructiveHint and idempotentHint, the reads are idempotent, and `download_sound` is marked non-destructive (20). Defaults on every optional parameter and one required field at most. The npm CLI and examples in JavaScript and Python exist, but the TypeScript client was not found on npm, so there is one published package (8 of 15). 25 + 20 + 15 + 20 + 8 = 88.
- Slipstream (60): MCP reading. 56 tools with no toolsets, dynamic loading or read-only subset (5 of 25). Search takes genre, mood, vocals, BPM and duration filters, REST search takes `limit` and `offset` with next and previous links, and an over-tight filter stack is relaxed and reported in `relaxed_filters` (15 of 20). REST errors return `success: false` with a stable `code` and a message, and the MCP docs say a capped call returns a clear message, with already-added channels and videos returning success (15 of 20). The docs say every tool carries readOnlyHint, destructiveHint, idempotentHint and openWorldHint, licences are idempotent for the same user, track and project, and renders are polled with identical arguments, not verified in `tools/list` (18 of 20). Few required parameters, and six registered prompts, but no official SDK (7 of 15). 5 + 15 + 15 + 18 + 7 = 60.

### Transparency & trust: Lots of Sounds +6

- Lots of Sounds (43): Closed service with terms of 1 April 2026 and a licence page that put every sound under CC0 1.0. No page read says where the sounds come from, who recorded them or how their CC0 status was checked. Sound ids carry an `fs-` prefix, sound pages show added dates from 2017, and the roadmap plans generated sounds, so the licence's basis can't be traced (10 of 30). The privacy policy of 19 October 2026 lists what is collected, including search terms, and says data is kept 'as long as reasonably necessary', with no periods, DPA or deletion route beyond an email (10 of 30). No deprecation policy or dated notices (0 of 20). Processors are named by type only (hosting, authentication, payments), with no list or locations (3 of 20). 10 + 10 + 0 + 3 = 23.
- Slipstream (37): Closed service. The licence coverage by plan, the banned uses and the rule that content published during a subscription stays covered after cancelling are set out in dated help centre articles, but the terms (a Notion page that rendered no text) could not be read (10 of 30). No privacy policy, DPA or retention statement was read (0 of 30). The changelog says breaking changes are announced ahead with migration steps, with no notice period and no dated notice read (8 of 20). No subprocessors or data locations found, beyond the docs' mention of S3 for downloads (0 of 20). 10 + 0 + 8 + 0 = 18.

## Score by category

| Category | Weight | Lots of Sounds | Slipstream | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% | 40 | 80 | Slipstream +40 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 79 | 50 | Lots of Sounds +29 |
| Agent ergonomics | 13% | 88 | 60 | Lots of Sounds +28 |
| Security & auth | 14% | 46 | 47 | Slipstream +1 |
| Payments & pricing | 10% | 25 | 25 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 66 | 18 | Lots of Sounds +48 |
| Transparency & trust | 7% | 43 | 37 | Lots of Sounds +6 |
| Negative events | ≤15 | -3 | 0 | |
| **Total** | | **52.9 · D** | **50 · D** | |

## Facts side by side

| Fact | Lots of Sounds | Slipstream |
| --- | --- | --- |
| Kind | MCP server | MCP server |
| Vendor | Lots of Sounds (Elliott Labs) | Slipstream Music |
| Hosted endpoint | `https://api.lotsofsounds.com/mcp` | `https://mcp.slipstreammusic.com/mcp` |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Freemium | subscription |
| x402 | no | no |
| Tools exposed | 5 | 56 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | no |
| MCP registry | `com.lotsofsounds/mcp` | not listed |
| Last release | 2026-10-29 | none |
| Terms last updated | 2026-04-01 | couldn't be read |
| Privacy policy last updated | 2026-10-19 | no document linked |
| Customer content may train models | not found in the text | couldn't be read |
| Terms restrict automated access | not found in the text | couldn't be read |
| Terms restrict benchmarking | not found in the text | couldn't be read |
| Terms or service can change without notice | not found in the text | couldn't be read |
| Arbitration or class-action waiver | not found in the text | couldn't be read |

## Verdicts

**Lots of Sounds.** A small, read-only MCP server and REST API with typed inputs, tool annotations, numbered daily limits and timing and loudness data on each sound. API access needs a person to sign up and subscribe, no page says where the CC0 sounds come from, and the home page's brand logos and uptime SLA have nothing behind them.

**Slipstream.** The MCP server documents 56 tools for search, downloads, stems, video soundtracks, rights checks and enterprise licences, and its licence flow waits for the user to approve the fee. Every call we could make needed a signed-in subscriber or a partner token, the REST API takes partner keys only, and the terms and privacy policy could not be read.

## Before you call either

### Lots of Sounds

1. Send short keywords in `q`, because every word must match a name, description or tag and search isn't semantic
2. Call `download_sound` only when the user is ready, because the signed URL expires after one hour
3. If the server returns 429, wait for `X-RateLimit-Reset`, which falls at midnight UTC for the daily limit
4. Pass one or two `tags` on `search_sounds`, since tags match with AND logic there and with OR logic on the sample endpoint
5. Tell the user the source of each sound isn't stated before they use it in a product where provenance matters

### Slipstream

1. Expect a 401 and a browser OAuth sign-in on the first call, even for search, and ask the user to sign in with an active Slipstream subscription
2. Call `prepare_license` until it returns `ready: true`, show the user the one-line `confirm`, and call `generate_license` once with the same values after they agree, since it mints a contract number
3. Treat `get_track_download_url` as a download only, not a licence, and remember the link spends the partner's download quota when opened
4. Poll `create_track_clip`, `extend_track` and `render_soundtrack` with identical arguments until `ready: true`, and keep calling `get_compliance_result` while AudioVerify returns `timeout`
5. Take filter values from `get_search_filters` or `get_sfx_filters`, because unknown values are dropped and an empty match retries without filters, reported in `relaxed_filters`

## Questions

### Which is better for AI agents, Lots of Sounds or Slipstream?

Lots of Sounds scores 52.9 (D) on agent readiness against Slipstream's 50 (D), and leads in 4 of 7 scored categories. Slipstream leads on reliability.

### Do Lots of Sounds and Slipstream need an API key?

Lots of Sounds takes an API key or an OAuth sign-in. Slipstream uses an OAuth sign-in.

### Can an agent call Lots of Sounds and Slipstream without installing anything?

Yes. Lots of Sounds has a hosted endpoint at https://api.lotsofsounds.com/mcp and Slipstream at https://mcp.slipstreammusic.com/mcp.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream.json, and with the fewest tokens: https://www.anchorterminal.com/compare/lotsofsounds-vs-slipstream.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "lotsofsounds", "b": "slipstream"}`. From a terminal: `anchor compare lotsofsounds slipstream`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/lotsofsounds.json and https://www.anchorterminal.com/api/v1/tools/slipstream.json

## Other comparisons with Lots of Sounds or Slipstream

- [Artyfile Music Licensing vs Lots of Sounds](https://www.anchorterminal.com/compare/artyfile-vs-lotsofsounds.md)
- [Artyfile Music Licensing vs Slipstream](https://www.anchorterminal.com/compare/artyfile-vs-slipstream.md)
- [Epidemic Sound MCP Server vs Lots of Sounds](https://www.anchorterminal.com/compare/epidemic-sound-vs-lotsofsounds.md)
- [Epidemic Sound MCP Server vs Slipstream](https://www.anchorterminal.com/compare/epidemic-sound-vs-slipstream.md)
- [Free Music Library MCP vs Lots of Sounds](https://www.anchorterminal.com/compare/free-music-library-mcp-vs-lotsofsounds.md)
- [Free Music Library MCP vs Slipstream](https://www.anchorterminal.com/compare/free-music-library-mcp-vs-slipstream.md)
- [Lots of Sounds vs The Rights Foundry](https://www.anchorterminal.com/compare/lotsofsounds-vs-the-rights-foundry.md)
- [Slipstream vs The Rights Foundry](https://www.anchorterminal.com/compare/slipstream-vs-the-rights-foundry.md)
- [LGDA Autonomic Pacing Node vs Slipstream](https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-slipstream.md)
- [LGDA Autonomic Pacing Node vs Lots of Sounds](https://www.anchorterminal.com/compare/lgda-autonomic-node-vs-lotsofsounds.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
