Head to head · Music search · October 2026 research run
Epidemic Sound MCP Server vs The Rights Foundry
The Rights Foundry scores 53.3 (D) on agent readiness against Epidemic Sound MCP Server's 24.5 (F), and leads in 6 of 7 scored categories. Epidemic Sound MCP Server leads on maintenance & community. Both do music search.
Best music and sound libraries for AI agents · All 21 music libraries comparisons
Which one, for what
Best for An agent soundtracking video for a person who already pays for Epidemic Sound.
Ahead on
- Maintenance & community, 40 against 27
Watch for
Labelled beta, with rate limits stated as unpublished and no status page or changelog found
Best for An app or agent that places human-made music in video made inside a product and records a licence per sync.
Ahead on
- Reliability, 30 against 5
- Schema & documentation, 80 against 29
- Agent ergonomics, 74 against 35
- Security & auth, 55 against 28
- Payments & pricing, 35 against 15
- Transparency & trust, 68 against 32
Watch for
Terms and licensing page describe the service as BETA, with access by invitation code and prices that may change
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation The Rights Foundry +51
Epidemic Sound MCP Server 29
The tool definitions couldn't be read, because robots.txt disallows /a/* and the endpoint sits at /a/mcp-service/mcp. The docs say tools/list returns each tool's description and parameters, but we didn't see them (0). www.epidemicsound.com/llms.txt is a site index that links the MCP page, with no Markdown copy of the MCP docs (5). The docs group the 16 tools by area, give three multi-step workflows and a known-limitations table that says when a tool fails (8). Parameters named in the docs include externalID, targetDurationMs up to 300,000, requiredRegionsAtOffsets, maxResults, skipStems and a language code from a voice's list, with no full input schema (5). curl examples for initialize and tools/list, client configs for four clients and a documented 401, with no other error responses (8). Registry versions 1.0.0 and 1.0.1, no public changelog (3). 0 + 5 + 8 + 5 + 8 + 3 = 29.
The Rights Foundry 80
A public OpenAPI 3.1 file, version 1.0, covers all seven operations (25). No llms.txt (404 on the docs host) and no Markdown docs. The reference is one HTML page (0). Descriptions say when to use each search mode and when to use another, with a table choosing between them (20). Typed inputs with enums for vocals, sort and booleans, length and range limits, required fields, and a sync body that rejects unknown keys (15). Request and response examples for every operation, and every error status documented with its body (15). Versioned /v1/ paths and a dated retirement of /v1/tracks/creative-brief on 24 September 2026 in the reference, but no public changelog (5). The MCP tool definitions were not readable. 25 + 0 + 20 + 15 + 15 + 5 = 80.
Agent ergonomics The Rights Foundry +39
Epidemic Sound MCP Server 35
16 tools, in the 11 to 30 band (15). No toolsets or read-only subset an operator can choose. Claude's directory connector drops the voiceover tools, which is the directory's rule, not a control (0 back). Search takes genre, mood, BPM, key and more per the docs, and maxResults appears, with no pagination described (10). A 401 is documented and doesn't say why. No other MCP errors are documented (5). Tool annotations and idempotency couldn't be read, and edits and voiceovers are poll-until-done jobs with no retry guidance (0). No MCP SDK of its own, and the docs point to the official TypeScript SDK. Workflows need several calls and IDs from earlier ones (5). 15 + 10 + 5 + 0 + 5 = 35.
The Rights Foundry 74
limit from 1 to 100 per page and per-request charging keep responses sized, but there is no field selection (15). Page and limit, tag, BPM, key, duration, vocals, decade and explicit filters, and sort fields (20). Errors name the cause, the fix and whether the call was charged, with constraints.empty_because naming the filter to loosen on an empty page (20). Free sync reissue within the paid window and best-effort refunds on server errors, but no idempotency key, and concurrent first syncs can both be charged (12). Few required parameters and sensible defaults, but no official SDK found, although the builders page lists JavaScript, Python and Swift SDKs (7). 15 + 20 + 20 + 12 + 7 = 74.
Transparency & trust The Rights Foundry +36
Epidemic Sound MCP Server 32
Closed service under an MCP Server Software License Agreement that the docs link but our reader couldn't render. The music licence itself is stated plainly on the plan pages, cleared forever for content published during an active subscription and not after (10). The privacy policy and legal pages are drawn by script and weren't readable, so no data-handling statement was checked (0). No deprecation policy or dated notice found. The registry's endpoint moved from /a/mcp-server/mcp to /a/mcp-service/mcp with no notice found (0). The REST API docs say its servers are in Europe with audio on Fastly's CDN. Nothing equivalent for the MCP server, and no subprocessor list read (5). 10 + 0 + 0 + 5 = 15.
The Rights Foundry 68
Closed service with clear terms (26 October 2026) and a licence page that sets out each licence type, its exclusions and that a sync lasts for the life of the content (15). The privacy policy (10 November 2026) gives a retention period for each kind of record, says customer content and assistant activity are not used to train models, and agrees with the terms. No DPA found (25 of 30). The terms give 30 days' notice to change or end BETA access and email notice of material changes. The retired search path answers 410 with a pointer and a date, but no deprecation policy for the API was found (12 of 20). Sub-processors and data locations are listed (Cloudflare, Neon (us-east-1), Stripe, Brevo, Google Analytics and Hugging Face) (20). 15 + 25 + 12 + 20 = 72.
Security & auth The Rights Foundry +27
Epidemic Sound MCP Server 28
OAuth 2.1 with Dynamic Client Registration on the vendor's own login server, limited to an allowlist of redirect URIs to counter phishing, with SSO and a workspace choice. The only scopes are email and openid, so access isn't narrowed by scope. The bearer key reaches the account, expires after a year and is rotated by making a new one, with no revocation described (20). No read-only mode or approval step for downloads or voiceover generation found (0). Results are the vendor's own catalogue metadata, plus Spotify track IDs from SearchExternalReferences, with no injection guidance (8). No audit log or per-call record for the account found (0). security.txt answers 404, and no disclosure policy, bug bounty or certification was found on the pages read (0). 20 + 0 + 8 + 0 + 0 = 28.
The Rights Foundry 55
Dashboard tokens are plain bearer keys that never expire and are revoked from the dashboard. MCP connections use OAuth 2.1 with PKCE and a 30-day expiry, but a single catalog:read scope (22 of 30). No read-only key and no per-purchase approval found. The privacy policy says a connected assistant can license tracks and spend credits, and only the vendor can switch sync off per token (5 of 20). Results are catalogue metadata curated by the vendor, and Acoustic Similarity Search fetches a URL the caller supplies, with no injection guidance found (8 of 15). The dashboard shows usage, credit balance, connected assistants and 30 days of sync reports, and each response carries X-Request-Id (12 of 15). Valid security.txt and a disclosure policy with response times and safe harbour, with no bug bounty or certification found (8 of 20). 22 + 5 + 8 + 12 + 8 = 55.
Reliability The Rights Foundry +25
Epidemic Sound MCP Server 5
Hosted MCP reading of the checklist. No status page found (0). No readable incident history (5). The MCP docs say rate limits aren't published (0). No 429, overload or retry guidance for the MCP server. The REST API's error page documents 429 with a retry delay, but that is a different product with different keys (0). No SLA found (0). The server and its docs are labelled beta (0). 0 + 5 + 0 + 0 + 0 + 0 = 5.
The Rights Foundry 30
Graded on the REST API. No status page found (0). No readable incident history (5). The only limit with a number is the MCP cap of 1,000 calls a UTC day. The docs say dashboard keys have no cap, while the terms say calls are rate limited without figures (10 of 15). 429 and billing 503 carry Retry-After, and each error status says whether it was charged, whether a refund is queued and when to retry. A sync link reissued within its window is free, and the docs warn to serialise concurrent first requests (15). No SLA (0). The terms, licensing page and calculator describe the service as BETA, with access by invitation code (0). 0 + 5 + 10 + 15 + 0 + 0 = 30.
Payments & pricing The Rights Foundry +20
Epidemic Sound MCP Server 15
No x402, MPP or L402 (0). Plan names and terms are public, but the prices are drawn by script on the pricing page and weren't readable to us, so this line scores as absent (0, unchecked). A free account can connect, search and preview per the MCP FAQ, with no card step described, but downloads and licences need a paid plan, so half credit (15). A person signs up and buys the subscription in a browser, and only the account holder can make an MCP key (0). 0 + 0 + 15 + 0 = 15.
The Rights Foundry 35
No x402, MPP or L402 (0). Plan prices and credit allowances are public, and the calculator gives how many syncs, streams and AI searches each plan buys, so per-unit costs can be derived. The exact rate card is returned only by the authenticated GET /v1/credits, and the docs print no prices (20 of 30). A free Foundation tier of 1,000 credits a month and free beta credits for new accounts. No card step is described, but card use was not confirmed, the licensing page says BETA access is by invitation, and the terms say free access carries no commercial licence (15 of 30). A person signs up in a browser with an emailed code, and MCP OAuth needs a person to sign in and approve (0). 0 + 20 + 15 + 0 = 35.
Score by category
| Category | Weight | Epidemic Sound MCP Server | The Rights Foundry | Edge |
|---|---|---|---|---|
| Reliability | 16% | 5 | 30 | The Rights Foundry +25 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 29 | 80 | The Rights Foundry +51 |
| Agent ergonomics | 13% | 35 | 74 | The Rights Foundry +39 |
| Security & auth | 14% | 28 | 55 | The Rights Foundry +27 |
| Payments & pricing | 10% | 15 | 35 | The Rights Foundry +20 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 40 | 27 | Epidemic Sound MCP Server +13 |
| Transparency & trust | 7% | 32 | 68 | The Rights Foundry +36 |
| Negative events | ≤15 | 0 | 0 | |
| Total | F 24.5/100 | D 53.3/100 |
Facts side by side
| Fact | Epidemic Sound MCP Server | The Rights Foundry |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Epidemic Sound | The Rights Foundry |
| Hosted endpoint | https://www.epidemicsound.com/a/mcp-service/mcp | https://mcp.therightsfoundry.com/mcp |
| Transports | Streamable HTTP | Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Your plan | Freemium |
| Price for music search | not published | $0.069 per call |
| x402 | no | no |
| Tools exposed | 16 | 0 |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| MCP registry | com.epidemicsound/mcp-server | not listed |
| Last release | 2026-08-17 | 2026-09-24 |
| Terms last updated | couldn't be read | 2026-10-26 |
| Privacy policy last updated | couldn't be read | 2026-11-10 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | yes |
| Terms restrict benchmarking | couldn't be read | not found in the text |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
Verdicts
Epidemic Sound MCP Server
An agent can search a 55,000-track owned catalogue by mood, BPM, key or a reference song, recut tracks to length and download them under the user's subscription. The server is in beta, with no published rate limits, status page or changelog, and every download needs a person's paid plan.
The Rights Foundry
The REST API has a detailed OpenAPI 3.1 file, three search modes, typed errors with charge rules, and a sync licence that outlasts the account. The service is in beta with no status page, SLA, changelog or SDK, the MCP tools are not documented, and preview streams are due to be charged at a rate not yet published.
Before you call either
Epidemic Sound MCP Server
- If you connect from Claude Code or your own client, use an MCP Server API key from Account > API keys, not a Developer Portal key
- Before you download, confirm the user has an active paid plan. A free account only searches and previews
- For a reference song, call SearchExternalReferences first and pass the Spotify ID to SearchRecordings as
externalID - Use an API key for track adaptation. OAuth connections may lack PollEditRecordingJob, which DownloadRecordingEdit needs
- Tell the user that only content published while the subscription is active stays cleared
The Rights Foundry
- Call
GET /v1/creditsbefore any charged call and read prices fromcosts, since the docs print none - Fetch page 1 of a Deep Search once with
limitup to 100, then page forward. Every page 1 is charged again - Send
{"external_export": true}to/syncwhen the video leaves the product. The default licence covers in-app use only - Serialise sync calls for the same track, because two first requests at once can both be charged
- Send no
Authorizationheader to signed asset URLs, and store track IDs rather than URLs, which expire after one hour
Questions
Which is better for AI agents, Epidemic Sound MCP Server or The Rights Foundry?
The Rights Foundry scores 53.3 (D) on agent readiness against Epidemic Sound MCP Server's 24.5 (F), and leads in 6 of 7 scored categories. Epidemic Sound MCP Server leads on maintenance & community.
Do Epidemic Sound MCP Server and The Rights Foundry need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Epidemic Sound MCP Server and The Rights Foundry without installing anything?
Yes. Epidemic Sound MCP Server has a hosted endpoint at https://www.epidemicsound.com/a/mcp-service/mcp and The Rights Foundry at https://mcp.therightsfoundry.com/mcp.
Other comparisons with Epidemic Sound MCP Server or The Rights Foundry
- Artyfile Music Licensing vs Epidemic Sound MCP Server
- Artyfile Music Licensing vs The Rights Foundry
- Epidemic Sound MCP Server vs Free Music Library MCP
- Epidemic Sound MCP Server vs Lots of Sounds
- Epidemic Sound MCP Server vs Slipstream
- Free Music Library MCP vs The Rights Foundry
- Lots of Sounds vs The Rights Foundry
- Slipstream vs The Rights Foundry
- Epidemic Sound MCP Server vs LGDA Autonomic Pacing Node
- LGDA Autonomic Pacing Node vs The Rights Foundry
Machine-readable
- This page as Markdown
/compare/epidemic-sound-vs-the-rights-foundry.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/epidemic-sound.json·/api/v1/tools/the-rights-foundry.json - From a terminal
anchor compare epidemic-sound the-rights-foundry(the CLI) - Over MCP
compare_tools {"a": "epidemic-sound", "b": "the-rights-foundry"}at/mcp, no key