Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"op3": {
"env": {
"OP3_API_TOKEN": "your-op3-token"
},
"args": [
"-y",
"@conorbronsdon/op3-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Podcast analytics for AI agents through OP3: downloads over time, listener geography, apps, and per-episode breakdowns. Read-only.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'npm' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
Packing does not respect root-level ignore files in workspaces
### Impact `npm pack` ignores root-level `.gitignore` & `.npmignore` file exclusion directives when run in a workspace or with a workspace flag (ie. `--workspaces`, `--workspace=<name>`). Anyone who has run `npm pack` or `npm publish` with workspaces, as of [v7.9.0](https://github.com/npm/cli/releases/tag/v7.9.0) & [v7.13.0](https://github.com/npm/cli/releases/tag/v7.13.0) respectively, may be affected and have published files into the npm registry they did not intend to include. ### Patch - Up
Incorrect Permission Assignment for Critical Resource in NPM
An issue was discovered in an npm 5.7.0 2018-02-21 pre-release (marked as "next: 5.7.0" and therefore automatically installed by an "npm upgrade -g npm" command, and also announced in the vendor's blog without mention of pre-release status). It might allow local users to bypass intended filesystem access restrictions because ownerships of /etc and /usr directories are being changed unexpectedly, related to a "correctMkdir" issue.
Local Privilege Escalation in npm
Affected versions of `npm` use predictable temporary file names during archive unpacking. If an attacker can create a symbolic link at the location of one of these temporary file names, the attacker can arbitrarily write to any file that the user which owns the `npm` process has permission to write to, potentially resulting in local privilege escalation. ## Recommendation Update to version 1.3.3 or later.
npm CLI exposing sensitive information through logs
Versions of the npm CLI prior to 6.14.6 are vulnerable to an information exposure vulnerability through log files. The CLI supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
npm Vulnerable to Global node_modules Binary Overwrite
Versions of the npm CLI prior to 6.13.4 are vulnerable to a Global node_modules Binary Overwrite. It fails to prevent existing globally-installed binaries to be overwritten by other package installations. For example, if a package was installed globally and created a `serve` binary, any subsequent installs of packages that also create a `serve` binary would overwrite the first binary. This will not overwrite system binaries but only binaries put into the global node_modules directory. This b
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in entertainment
MCP Security Weekly
Get CVE alerts and security updates for io.github.conorbronsdon/op3-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Podcast analytics for AI agents through OP3: downloads over time, listener geography, apps, and per-episode breakdowns. Read-only.
An MCP server for OP3, the Open Podcast Prefix Project. It gives AI assistants podcast analytics that most hosting APIs do not expose: downloads over time, listener geography, the apps people listen in, and per-episode breakdowns.
Read-only by design. OP3 is an analytics service. This server only reads data. It cannot change anything, so it is safe to give an agent.
Why this exists. Most podcast hosts expose almost nothing through their API. Transistor's API, for example, returns download counts and not much else: no geography, no app share, no per-episode recency curve. OP3 has all of that, because it logs each download at the redirect. This server puts that data in front of an agent.
OP3 is a free, open analytics prefix for podcasts. You add https://op3.dev/e/ in front of your enclosure URLs, and OP3 logs each download before redirecting to your real audio file. It then reports downloads, geography, and app share. Stats pages are public; the API needs a token. See https://op3.dev for details.
If your feed does not use the OP3 prefix yet, OP3 has no data for it. See "Adding the OP3 prefix" below.
| Tool | What it returns | OP3 endpoint |
|---|---|---|
op3_get_show | Show UUID, title, podcast GUID, stats page URL, optional episode list | GET /shows/{showUuidOrPodcastGuidOrFeedUrlBase64} |
op3_show_downloads | Monthly downloads, weekly breakdown, weekly average | GET /queries/show-download-counts |
op3_episode_downloads | Per-episode downloads at 1/3/7/30 days and all-time | GET /queries/episode-download-counts |
op3_top_apps | Top apps/players by download share, last 3 calendar months | GET /queries/top-apps-for-show |
op3_top_countries | Top listener countries or regions (computed from raw records) | GET /downloads/show/{showUuid} |
op3_downloads_timeseries | Raw download events over a date range (time, country, app, device) | GET /downloads/show/{showUuid} |
Most tools need a show UUID. Start with op3_get_show to turn a feed URL or podcast GUID into a UUID.
Every list tool takes a limit and defaults it low (10) to keep responses small. Agents pay tokens per response.
preview07ce, which works against public shows.If you know your feed URL or podcast GUID, ask the assistant to run op3_get_show with it and it will return your UUID. You can also read the UUID from your show's OP3 stats page URL: https://op3.dev/show/{showUuid}.
Add to your .mcp.json:
{
"mcpServers": {
"op3": {
"command": "npx",
"ar
... [View full README on GitHub](https://github.com/conorbronsdon/op3-mcp#readme)