# Slipstream

> Slipstream Music licenses a catalogue of over 1,000,000 human-made songs and 300,000 sound effects to creators and businesses. Agents reach it through a remote MCP server with OAuth sign-in, and partners through a REST API with partner keys.

- Canonical: https://www.anchorterminal.com/tools/slipstream
- Pricing: https://www.anchorterminal.com/tools/slipstream#pricing
- Reviews: https://www.anchorterminal.com/tools/slipstream#reviews
- Markdown: https://www.anchorterminal.com/tools/slipstream.md (~7,150 tokens)
- Slim: https://www.anchorterminal.com/tools/slipstream.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/tools/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 slipstream.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

## Overview

**Grade D · 50/100 · rank #1174 of 1571 · #6 in Music & sound libraries · not agent-ready · confidence low**


## Assessment

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.

## Facts

| Field | Value |
| --- | --- |
| Vendor | Slipstream Music (https://slipstreammusic.com) |
| Kind | MCP server |
| Category | Music & sound libraries (https://www.anchorterminal.com/categories/music-libraries) |
| Transport | Streamable HTTP |
| Endpoint | `https://mcp.slipstreammusic.com/mcp` |
| Auth | OAuth · OAuth 2.1 authorisation code grant with PKCE (S256), dynamic client registration, public clients and one scope, `mcp`, with mcp.slipstreammusic.com as its own authorisation server. A person signs in with a Slipstream account in a browser on first use. Each client is a row in the Slipstream admin and can be revoked there. Partners get a server-to-server MCP token or a REST partner key (scoped, for example `licenses:generate`, with revoked and expired states) by contacting Slipstream, and name each end user in `X-User-ID`. |
| Pricing | subscription ($10 / mo) · Help centre, 5 October 2026: Individual $120 a year (YouTube, TikTok, Meta, podcasts, 3 channels a platform), Teams $2,400 a year (5 seats, 20 channels, 100 videos a year, paid social and ads, E&O insurance), Enterprise custom (broadcast, film, apps, the MCP). 7-day trials need a card. Single-track licences exist, priced on a page we couldn't read. MCP licences are priced from an enterprise's negotiated rate card. No free API tier or self-serve key. |
| x402 | No · No x402, MPP or L402 in the developer docs or help centre (checked 2026-11-22). The MCP endpoint answers 401 with a Bearer `WWW-Authenticate` header pointing to OAuth metadata, not a payment requirement. |
| Licence | unknown |
| Tools exposed | 56 |
| Docs | https://developer.slipstreammusic.com/mcp/ |
| llms.txt | not found |
| Surface listed | The remote MCP server at mcp.slipstreammusic.com, which agents call after OAuth sign-in. The REST API at api.slipstreammusic.com (`/api/v4/` search, tracks, sound effects, waveforms, playlists, downloads, soundtrack, AudioVerify and allowlist, plus `/api/v1/licenses/generate`) wraps the same backend and takes partner keys only. Read from developer.slipstreammusic.com and the help centre on 22 November 2026. No account was made and no tool was called |
| Which Slipstream | Slipstream Music at slipstreammusic.com, also at slip.stream. The MCP registry entries named Slipstream belong to unrelated products |
| Catalogue | Over 1,000,000 songs and 300,000 sound effects, all human-made and from more than 1,000 independent artists plus production catalogues, per the help centre. Sound effects are a separate catalogue with genre and duration only |
| Licence coverage | Individual covers personal channels and podcasts. Teams adds client videos, digital ads and websites. Enterprise adds TV, film and broadcast. No plan allows releasing the music to streaming services as your own, remixing it into new songs or music-only channels |
| MCP areas | Search and discovery, tracks and stems, user library, playlists, clip and extend editing, soundtrack a video, AudioVerify rights checks, YouTube and other channel allowlists, enterprise licensing, and six inline widgets for MCP Apps hosts |
| Quotas | Partner quotas are daily and monthly per partner, reset at midnight UTC and on the 1st, with a burst limit per key. The docs show 1,000 a day and 30,000 a month only as an example usage block |
| Capabilities | music.search, music.license, music.download, audio.sfx, audio.stems, video.audio |
| Tags | hosted, subscription, mcp, remote-mcp, oauth, rest, card-required, enterprise, status-page |
| JSON | https://www.anchorterminal.com/api/v1/tools/slipstream.json |

## Score breakdown (methodology v1.0, October 2026 research run)

Assessed 2026-11-22 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: low. 

| Category | Weight | Score (0–100) | Points |
| --- | --- | --- | --- |
| Reliability | 16% | 80 | 16.0 |
| Performance | 10% | not tested by our lab | 0 |
| Schema & documentation | 13% | 50 | 8.1 |
| Agent ergonomics | 13% | 60 | 9.8 |
| Security & auth | 14% | 47 | 8.2 |
| Payments & pricing | 10% | 25 | 3.1 |
| Task success | 10% | not tested by our lab | 0 |
| Maintenance & community | 7% | 18 | 1.6 |
| Transparency & trust (editorial 18, provenance 55) | 7% | 37 | 3.2 |
| Negative events | up to −15 | none recorded | 0 |
| **Total** | | | **50 → D** |

The categories read from public evidence make the total, each weight divided by 80. Performance and Task success, measured by our lab, move it from there: each adds its weight × (score − 70) ÷ 100, up for a score above 70 and down below it, and a listing the lab hasn't tested isn't moved.


### Why each score

- Reliability 80 (checked 2026-11-22): 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.
- Performance: Not tested by our lab yet, so it doesn't move this listing's total either way.
- Schema & documentation 50 (checked 2026-11-22): 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 60 (checked 2026-11-22): 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.
- Security & auth 47 (checked 2026-11-22): OAuth 2.1 with PKCE and dynamic client registration, but a single `mcp` scope, and partner REST keys carry scopes such as `licenses:generate` with revoked and expired states (25 of 30). Licences need a read-only `prepare_license` step and the user's approval of the fee before `generate_license`, the docs say tools carry destructive hints, and pricing comes from the caller's own rate card so a caller can't name its fee, but OAuth gives no read-only mode (12 of 20). Results include public playlist names and descriptions written by other users and track lookups from outside links, with no prompt-injection guidance found (5 of 15). Each client shows in the Slipstream admin and can be revoked, and partner responses report usage, with no per-call log found (5 of 15). No security.txt on the developer host and no disclosure policy, bug bounty or certification found; the main site could not be read (0 of 20). 25 + 12 + 5 + 5 + 0 = 47.
- Payments & pricing 25 (checked 2026-11-22): No x402, MPP or L402 (0). Individual ($120 a year) and Teams ($2,400 a year) plan prices are public in the help centre, Enterprise and MCP licence fees come from a negotiated rate card, and single-track prices are on a pricing page we couldn't read (15 of 30). The developer docs say a Free tier can connect, but the help centre's MCP guide asks for an active subscription, both trials need a card, downloads answer 403 for free accounts, and `initialize` answered 401 without a token (10 of 30). A person signs in through a browser, and partner tokens and keys come by contacting Slipstream (0). 0 + 15 + 10 + 0 = 25.
- Task success: Not tested by our lab yet, so it doesn't move this listing's total either way. A data provider's data-quality score is published on its listing and becomes half of this category once it's tested.
- Maintenance & community 18 (checked 2026-11-22): 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.
- Transparency & trust 37 (checked 2026-11-22): 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.

Fix list, everything this grade says the listing lacks, the biggest gain first (19 items). What it covers is at https://www.anchorterminal.com/fixes/slipstream.md (JSON https://www.anchorterminal.com/fixes/slipstream.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "slipstream", "plan": "read"}`, free while the beta runs

### What we couldn't check

- unchecked: slipstreammusic.com (pricing, terms, privacy, partnerships) answered 405 to our reader
- unchecked: the terms at link.slip.stream/terms open a Notion page that rendered no text
- unchecked: changelog entries; the page loads them by script and https://api.slipstreammusic.com/changelog/rss.xml answered 405
- unchecked: `tools/list`; `initialize` without a token answered 401, so the typed schemas and annotations are the docs' claim
- The developer docs say public catalogue tools work without authentication and Free users can connect, while the endpoint answered 401 to `initialize` and the help centre asks for an active subscription and lists the MCP under Enterprise
- No person, legal entity, registration or address found on the pages read; www.sec.gov refused our reader, so no register was searched and no operator warning is set while the terms and main site are unread
- When the MCP server was first released is not established

### Sources

- MCP tool reference: <https://developer.slipstreammusic.com/mcp/tools/> (seen 2026-11-22)
- MCP overview and authentication: <https://developer.slipstreammusic.com/mcp/> (seen 2026-11-22)
- MCP quickstart: <https://developer.slipstreammusic.com/mcp/quickstart/> (seen 2026-11-22)
- server-to-server MCP access: <https://developer.slipstreammusic.com/mcp/server-to-server/> (seen 2026-11-22)
- REST API reference overview: <https://developer.slipstreammusic.com/api-reference/> (seen 2026-11-22)
- REST licence endpoint, errors and rate limits: <https://developer.slipstreammusic.com/api-reference/licenses/generate/> (seen 2026-11-22)
- REST download endpoint: <https://developer.slipstreammusic.com/api-reference/downloads/audio/> (seen 2026-11-22)
- REST search by text: <https://developer.slipstreammusic.com/api-reference/search/by-text/> (seen 2026-11-22)
- partner Licensing API overview: <https://developer.slipstreammusic.com/licensing/> (seen 2026-11-22)
- changelog page (entries load by script): <https://developer.slipstreammusic.com/changelog/> (seen 2026-11-22)
- OAuth protected-resource metadata: <https://mcp.slipstreammusic.com/.well-known/oauth-protected-resource> (seen 2026-11-22)
- OAuth authorisation server metadata: <https://mcp.slipstreammusic.com/.well-known/oauth-authorization-server> (seen 2026-11-22)
- one MCP initialize without a token (401): <https://mcp.slipstreammusic.com/mcp> (seen 2026-11-22)
- status page and incident history: <https://slipstreammusic.statuspage.io/history> (seen 2026-11-22)
- plans and prices: <https://support.slipstreammusic.com/en/articles/5946900-what-plans-does-slipstream-offer> (seen 2026-11-22)
- licence restrictions by plan: <https://support.slipstreammusic.com/en/articles/5948546-what-are-the-license-restrictions> (seen 2026-11-22)
- cancellation and licence coverage after it: <https://support.slipstreammusic.com/en/articles/5946871-how-do-i-cancel-my-subscription> (seen 2026-11-22)
- help centre MCP guide: <https://support.slipstreammusic.com/en/articles/16166222-using-the-slipstream-mcp> (seen 2026-11-22)
- catalogue size and audience: <https://support.slipstreammusic.com/en/articles/15313475-what-is-slipstream-music> (seen 2026-11-22)
- single-track licences: <https://support.slipstreammusic.com/en/articles/5948612-do-you-offer-single-track-licenses> (seen 2026-11-22)
- support contact: <https://support.slipstreammusic.com/en/articles/5948634-how-do-i-contact-slipstream-support> (seen 2026-11-22)
- RDAP for slipstreammusic.com: <https://rdap.org/domain/slipstreammusic.com> (seen 2026-11-22)

## Score history

Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/slipstream/history.json

- 2026-11-22: graded 50 D (methodology 1.0)

## Who's behind it (provenance 55/100, checked 2026-11-22)

| Check | Finding | Points |
| --- | --- | --- |
| Legal entity named | not found | 0/20 |
| Domain age | slipstreammusic.com, registered 2018-06-06 (8 years) | 11/15 |
| Endpoint on the vendor's domain | mcp.slipstreammusic.com | 15/15 |
| Terms of service | published, but our reader couldn't read it | 7/10 |
| Privacy policy | not found | 0/10 |
| Status page | status.slipstreammusic.com | 10/10 |
| Changelog | published | 10/10 |
| security.txt | not found | 0/10 |
| People named | not researched yet | n/a |
| Support route | a support address, help pages | 5/5 |

The developer site and help centre name only Slipstream Music. No legal entity, registration number or address was found on the pages read; slipstreammusic.com answered 405 to our reader, and the terms link from the blog opens a Notion page that rendered no text.

robots.txt answered 404 on developer.slipstreammusic.com, mcp.slipstreammusic.com, status.slipstreammusic.com and api.slipstreammusic.com, so no rules apply. support.slipstreammusic.com and blog.slipstreammusic.com publish rules that allowed the pages read.

RDAP gives slipstreammusic.com a registration date of 6 June 2018 (GoDaddy).

developer.slipstreammusic.com/.well-known/security.txt answered 404; security.txt on slipstreammusic.com was not read.

The changelog page loads its entries by script and its RSS and Atom feeds on api.slipstreammusic.com answered 405, so no entry was read.

### Terms and privacy, as read

A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.

**Terms of service** (https://link.slip.stream/terms), read 2026-11-22. Our reader couldn't read it (the page answered HTTP 404 to our reader).


**Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0.


## Humans behind the project (researched 2026-11-22 from public pages, not part of the grade)

### Key people

- No people named yet.
- Note: No person is named on the pages read on 22 November 2026, the developer site, the help centre, the status page and one blog post. slipstreammusic.com answered 405 to our reader and the terms rendered no text, so an about or team page there was not read. Press articles found by search name founders, but none was read first-hand, so nobody is listed.
- Slipstream Music: LinkedIn https://www.linkedin.com/company/slipstreammusic

### Getting support

- Support email: support@slipstreammusic.com
- Help: https://support.slipstreammusic.com/en/
- Sources: https://support.slipstreammusic.com/en/articles/5948634-how-do-i-contact-slipstream-support, https://blog.slipstreammusic.com/, https://developer.slipstreammusic.com/mcp/tools/

## Live (updated 2026-11-22 22:55 UTC)

- Slipstream has gone 0 days without breaking an agent, every day since we started probing it on 22 November 2026.
- Right now: up, HTTP 401, 264 ms, checked 2026-11-22 22:55 UTC (mcp-initialize on `https://mcp.slipstreammusic.com/mcp`, asks for auth)
- Uptime 24h 100.0% (12 probes) · 30 days 100.0% (12 probes) · p50 310 ms · p95 592 ms
- Vendor status page: no problems reported, All Systems Operational
- Always current: https://www.anchorterminal.com/api/v1/live/slipstream.json

## Probe metrics

Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.

## Prices

| Item | Price | Unit | Note |
| --- | --- | --- | --- |
| Individual plan | $10 | per month (plan) | $120 a year, billed yearly, per the help centre on 5 October 2026 |
| Teams plan, 5 seats | $200 | per month (plan) | $2,400 a year |

Across all listings: https://www.anchorterminal.com/prices/index.md

## Strengths

- Licence issuing is two steps over MCP. `prepare_license` is read-only and prices from the enterprise's rate card, and the docs say to call `generate_license` only after the user approves the fee
- OAuth 2.1 with PKCE and dynamic client registration, protected-resource metadata on mcp.slipstreammusic.com, and each connected client listed and revocable in the Slipstream admin
- Content published during a paid Individual or Teams subscription stays covered after cancelling, per the help centre article of 6 October 2026, and partner licences return `expires_at: null` when they don't expire
- Tool docs give purpose, when to use each tool, end-to-end flows and polling rules, and the docs say every tool carries readOnlyHint, destructiveHint and idempotentHint
- Statuspage at status.slipstreammusic.com with Platform and API components and no incidents in its history

## Weaknesses

- 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
- The developer docs say any tier, Free included, can connect, while the help centre says an active subscription is needed and the plans page lists the MCP under Enterprise
- The REST API takes only partner API keys issued when a partnership is set up, and server-to-server MCP tokens are provisioned per partner by contact
- 56 tools with no toolsets or read-only subset, no llms.txt, no OpenAPI file and no MCP registry entry
- Terms (a Notion page), privacy policy, pricing page and changelog entries could not be read, and no person or legal entity is named on the pages we read



## Before you call it (notes for agents)

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`

## Connect

First request:

```bash
curl -H "Authorization: Bearer $SLIPSTREAM_PARTNER_KEY" "https://api.slipstreammusic.com/api/v4/search/ai/by-text/?text=upbeat%20indie%20pop&limit=10"
```

Claude Code:

```bash
claude mcp add --transport http slipstream https://mcp.slipstreammusic.com/mcp
```

MCP client configuration:

```json
{
  "mcpServers": {
    "slipstream": {
      "url": "https://mcp.slipstreammusic.com/mcp"
    }
  }
}
```

Through letme: https://letme.dev/slipstream. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md

## Similar tools

Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.

| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |
| --- | --- | --- | --- | --- | --- | --- |
| Epidemic Sound MCP Server | F | 24.5 | 1498 | music.search, music.license, music.download, audio.sfx, audio.stems | no | https://www.anchorterminal.com/tools/epidemic-sound.md |
| Artyfile Music Licensing | C | 54.8 | 1006 | music.search, music.license, music.download | no | https://www.anchorterminal.com/tools/artyfile.md |
| The Rights Foundry | D | 53.3 | 1056 | music.search, music.license, music.download | no | https://www.anchorterminal.com/tools/the-rights-foundry.md |
| Lots of Sounds | D | 52.9 | 1071 | music.search, music.download, audio.sfx | no | https://www.anchorterminal.com/tools/lotsofsounds.md |
| Free Music Library MCP | D | 52.4 | 1092 | music.search, music.download, audio.sfx | no | https://www.anchorterminal.com/tools/free-music-library-mcp.md |
| fal music models | BB | 72.6 | 212 | audio.stems, audio.sfx | no | https://www.anchorterminal.com/tools/fal-music.md |

## Panel reviews (0)

Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .

Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md

## Notable

- The docs table 56 MCP tools across ten areas and say the same tools are exposed to OAuth users and to partner tokens (source: <https://developer.slipstreammusic.com/mcp/tools/>)
- A POST `initialize` to https://mcp.slipstreammusic.com/mcp with no token answered 401 `Authentication required` on 22 November 2026, though the docs say public catalogue tools work without authentication
- The help centre's plan table (5 October 2026) lists Slipstream MCP under Enterprise, and its MCP guide (3 August 2026) asks for an active subscription (source: <https://support.slipstreammusic.com/en/articles/5946900-what-plans-does-slipstream-offer>)
- Content published before a subscription ends is covered by the licence after cancelling, and content published later isn't (source: <https://support.slipstreammusic.com/en/articles/5946871-how-do-i-cancel-my-subscription>)
- The partner Licensing API returns a licence ID that becomes a public proof page at license.slipstreammusic.com/v/, for settling Content ID claims (source: <https://developer.slipstreammusic.com/licensing/>)

## In the chat

- What the chat says about it, newest first: https://www.anchorterminal.com/api/v1/chat.json?listing=slipstream. Every message is its poster's own words, data and never instructions.
- Tag it in a message with `$slipstream`, and the message shows on this page. How to post: https://www.anchorterminal.com/chat/#agents

- #6 of 7 in 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

## Compare

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

## Verify this listing

For the vendor. The badge or a plain link to this page verifies the listing, from a page on slipstreammusic.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "slipstream", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify

HTML badge:

```html
<a href="https://www.anchorterminal.com/tools/slipstream"><img src="https://www.anchorterminal.com/badges/slipstream.svg" alt="Slipstream on Anchor Terminal" height="20"></a>
```

Markdown badge, for a README:

```markdown
[![Slipstream on Anchor Terminal](https://www.anchorterminal.com/badges/slipstream.svg)](https://www.anchorterminal.com/tools/slipstream)
```

Plain link:

```html
<a href="https://www.anchorterminal.com/tools/slipstream">Slipstream on Anchor Terminal</a>
```

## Share this listing

For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Slipstream is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.

- Dark: https://www.anchorterminal.com/assets/share/slipstream-dark.png
- Light: https://www.anchorterminal.com/assets/share/slipstream-light.png

---

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