MCP servers › io.github.mrfentmen › listennotes-mcp

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.github.mrfentmen/listennotes-mcp

Query Listen Notes: podcast search, best lists, episode details. — the publisher's description

3 of 6 record checks metversion 1.1.0MITstandard input/output

Summary

io.github.mrfentmen/listennotes-mcp is a local MCP server listed in the official MCP registry at version 1.1.0.

Record checks

3 of 6 record checks met · 3 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
met: Package names its licence with a standard (SPDX) identifier
not met: The version the registry lists can be installed and is not withdrawn
not met: npm package carries build provenance (attestation)
met: No known critical or high advisory in the package or its dependencies

#4,298 of 15,112 packages by monthly downloads, tied with 5 others
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: local package
Transport: standard input/output
Package: npm · listed version behind the latest release
License: MIT
Dependencies: no known high or critical advisories
Repository: link does not open publicly
Last tested: 2026-10-23

Add to your client

Worth knowing before you connect it

The registry lists 1.1.0; 1.1.1 is newer (1 release).
The listed version is deprecated on npm.
The linked repository does not open publicly, so the code cannot be reviewed through it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: attempted, see below
Last tested: 2026-10-23
Latest version: 1.1.0, published 2026-10-17 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-17 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.1.0 (published 2026-10-17).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

How do I add it to my client?

Config from the registry entry

From the npm package listennotes-mcp

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.

Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)

{
  "mcpServers": {
    "listennotes-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "listennotes-mcp@1.1.0"
      ]
    }
  }
}

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "listennotes-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "listennotes-mcp@1.1.0"
      ]
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "listennotes-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "listennotes-mcp@1.1.0"
      ]
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"listennotes-mcp","type":"stdio","command":"npx","args":["-y","listennotes-mcp@1.1.0"]}'

Claude Code

claude mcp add --transport stdio listennotes-mcp -- npx -y listennotes-mcp@1.1.0

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 -- npx -y listennotes-mcp@1.1.0

This runs the publisher's code on your machine (npx). Read its README first.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Can it be installed, and is it up to date?

Version pin · advisories

Listed version

Registry lists: 1.1.0
Latest stable: 1.1.1
Status: behind the latest release (1 releases, 2 days)
Withdrawn: deprecated upstream

“Private commercial package — removed from public npm. Source: https://github.com/mrfentmen/premium-mcps” — the publisher's message

Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.

Dependency advisories

Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).

Integrity, provenance, license

Integrity: sha512-BGPHd+Wb3L1ufo2Ys…
Signature: signed
License: MIT

Source: the package registry · 2026-10-23.

Usage

Downloads: 646 in the last month

Source: api.npmjs.org · 2026-10-23.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Published package can be started	Did not start	differs	our test · 2026-10-23
Version 1.1.0 on npm	Exists and can be installed	matches	npm · 2026-10-23
Repository github.com/mrfentmen/premium-mcps	Does not open (not found or private)	differs	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.github.mrfentmen · 897 servers

Repository: github.com/mrfentmen/premium-mcps — does not open publicly

Source: the registry entry and api.github.com · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

3 of 6 record checks met · 3 do not apply

#4,298 of 15,112 packages by monthly downloads, tied with 5 others
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe linked repository returned HTTP 404: it does not exist or is private.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
MetPackage names its licence with a standard (SPDX) identifierMIT
Not metThe version the registry lists can be installed and is not withdrawnThe listed version is deprecated (npm) or yanked (PyPI).
Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.
MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.github.mrfentmen/listennotes-mcp

Answered from the data above

Is io.github.mrfentmen/listennotes-mcp safe to install?

We do not rate servers as safe or unsafe. 3 of its 6 applicable record checks are met (facts from public records, each listed on this page). What the records show: The repository it links to does not open publicly, so its code cannot be inspected through that link. A newer stable release exists than the one listed. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.mrfentmen/listennotes-mcp been security tested?

We tried, but no check could run. None of the 18 checks that apply to it could be exercised. The published package does not install or start cleanly today, so no check could run. No security verdict is published before verification.

Is the listed version current?

No. The registry lists 1.1.0; the latest stable release on npm is 1.1.1.

Where is the source code of io.github.mrfentmen/listennotes-mcp?

The registry links to github.com/mrfentmen/premium-mcps, but that link does not open publicly, so the code cannot be inspected through it.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Package does not start

The published package does not install or start cleanly today, so no check could run. No security score is given; a check we did not run is never counted as passed.

Why not security-tested: The published package provides no runnable server (no executable, or one the system cannot start), so no session could be opened. — a defect in the package

The 18 checks at a glanceour test · 2026-10-23

Inventory: not run · package does not start
Hidden instructions: not run · package does not start
Real execution: not run · package does not start
Secret leak: not run · package does not start
Internal addresses: not run · package does not start
Unconfirmed changes: not run · package does not start
Bad input: not run · package does not start
Model requests: not run · package does not start
Sensitive questions: not run · package does not start
Folder boundary: not run · package does not start
Log leaks: not run · package does not start
Hidden content: not run · package does not start
Fake assistant turns: not run · package does not start
Token passthrough: not run · package does not start
Token audience: not run · package does not start
Sign-in redirect: not run · package does not start
Consent handling: not run · package does not start
Sign-in metadata: not run · package does not start

0 exercised18 not run (reason given)0 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). None of the 18 checks that apply to it could be exercised. We do not publish security-check outcomes for named servers.

Not run, with the reason · 18

1Inventory
tool-listReads the declared tools, resources and prompts.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
3Real execution
real-executionCalls a tool and checks what really happens.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
7Bad input
error-handlingSends bad input and watches how the server answers.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
8Model requests
samplingChecks whether the server asks the client's model to act for it.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
12Hidden content
audience-hidingChecks resources that hide content from the user.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
17Consent handling
confused-deputyChecks consent handling when one service acts for another.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The npm package's executable has no interpreter line, so the operating system cannot run it.not run · package does not start

Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted the published package in an isolated sandbox
The package did not start.
2,890 msFinished: 0 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

no value

No value: the two AI models (Gemini and Claude) disagreed, so neither answer is shown.

Pricing modelAI-classified

not checked

no website in the registry entry

Programming language

does not apply

no existing GitHub repository

Hosting type

local package

registry · 2026-10-23

MCP capability

not checked

not read (no session)

Transport

standard input/output

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

npm

registry · 2026-10-23

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

permissive

package registry · 2026-10-23

Integrity hash

declared (sri)

package registry · 2026-10-23

Signature / provenance

signed

package registry · 2026-10-23

Dependency advisories

none known

npm audit · 2026-10-23

Popularity

646 downloads a month

package registry · 2026-10-23

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

not stated

repository link is dead (HTTP 404), so activity cannot be read

Environment

your machine

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.mrfentmen/listennotes-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.mrfentmen/listennotes-mcp

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.mrfentmen/listennotes-mcp)](https://protocolprobe.com/mcp/servers/io.github.mrfentmen/listennotes-mcp)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology