updated 2026-11-10 04:07 UTC

NotebookLM MCP (PleasePrompto)

Repository

MCP server for NotebookLM - Let your AI agents (Claude Code, Codex) research documentation directly with grounded, citation-backed answers from Gemini. Persistent auth, library management, cross-client sharing. Zero hallucinations, just your knowledge base.

MCP Servers TypeScript Needs review MIT

Is NotebookLM MCP (PleasePrompto) safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 1.4 / 10
Provenance None
Signed commits 0%
Last push 61d ago
Advisories None known
Compare NotebookLM MCP (PleasePrompto)

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: NotebookLM MCP (PleasePrompto) scores 49.5/100 (Grade D), ranked #1025 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 1.4/10; recent commits are unsigned; no published advisory affects its latest release (notebooklm-mcp); last pushed 2026-09-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How NotebookLM MCP (PleasePrompto) could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge
Active listing, but review is needed
  • [5.1] repository is archived

Chain of custody

Scanners check what the code says. This traces who ships NotebookLM MCP (PleasePrompto) and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/PleasePrompto/notebooklm-mcp, MIT, last pushed 2026-09-10. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 1.4/10 (scanned Nov 8, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflown/a
    • Token Permissionsn/a
    • Pinned Dependenciesn/a
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 0
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow -1
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging -1
    Pinned-Dependencies -1
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions -1
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm notebooklm-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: notebooklm-mcp 2.0.0. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-08-29 OSSF Scorecard: 1.4/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues NotebookLM MCP (PleasePrompto)’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How NotebookLM MCP (PleasePrompto) compares in MCP Servers

  1. #579 Debridge MCP 49.5 ±0
  2. #580 MCP Abap Abap Adt Api 49.5 ±0
  3. #581 NotebookLM MCP (PleasePrompto) 49.5 this agent
  4. #582 Mac Control MCP 49.3 −0.2
  5. #583 Synter Media AI MCP Server 49.3 −0.2

Bars show each HVTrust score; the tick marks NotebookLM MCP (PleasePrompto)’s 49.5.

Where the 49.5 comes from

HVTrust dimensions vs the MCP Servers average

49.5 / 100 · 100.0% confidence

NotebookLM MCP (PleasePrompto) MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.7 / 25
9.1 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
9.7 / 17
2.6 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
7.9 / 20
4.3 below avg 12.2
AdoptionLog-scaled stars · package downloads
13.4 / 20
5.8 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-29
Rank Moved
Rank rose 11 spots (#1031 → #1020)
2026-10-23
Grade Changed
Trust grade C → D
2026-10-16
Rank Moved
Rank dropped 12 spots (#975 → #987)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 1.4/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 61 days ago. Fresh activity helps separate stable projects from stale ones.
Review Flags
[5.1] repository is archived
Compare with another agent
View MCP Servers Report missing data
50.7
Activity sub-score · out of 100
#581
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 61 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
3.4k
Forks
573
Last Push
2026-09-10
61 days ago
Commits (4 wk)
0
Downloads (7d)
4,971
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1025

Analysis

Activity Inputs

50.7 / 100
StarsRepository reach
21.2 / 30
FreshnessLast push recency
16.5 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
12.8 / 20

Common questions about NotebookLM MCP (PleasePrompto)

Public trust evidence for NotebookLM MCP (PleasePrompto) is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does NotebookLM MCP (PleasePrompto) publish package provenance?
No published build provenance is currently detected for NotebookLM MCP (PleasePrompto). This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does NotebookLM MCP (PleasePrompto) have an OpenSSF Scorecard?
NotebookLM MCP (PleasePrompto) has an OpenSSF Scorecard score of 1.4/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is NotebookLM MCP (PleasePrompto) actively maintained?
Slowing down. Last push was 61 days ago — keep an eye on whether activity resumes.
What license does NotebookLM MCP (PleasePrompto) use?
NotebookLM MCP (PleasePrompto) ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are NotebookLM MCP (PleasePrompto)'s commits signed?
0% of the last 100 commits to NotebookLM MCP (PleasePrompto) are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
NotebookLM MCP (PleasePrompto) appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to NotebookLM MCP (PleasePrompto)'s runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-10
Activity Resumed
Activity resumed

Maintain NotebookLM MCP (PleasePrompto)?

For maintainers

HVTrust scores NotebookLM MCP (PleasePrompto) from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 25Warning Issued 4HVTrust 3Grade 3Warning Cleared 2Scorecard 1Score 1Fresh 1Delisted 1Listed 1MCP 1
2026-10-29
Rank Moved
Rank rose 11 spots (#1031 → #1020)
2026-10-23
Grade Changed
Trust grade C → D
2026-10-16
Rank Moved
Rank dropped 12 spots (#975 → #987)
2026-10-14
Rank Moved
Rank dropped 10 spots (#968 → #978)
2026-10-10
Rank Moved
Rank dropped 43 spots (#909 → #952)
2026-10-09
Rank Moved
Rank dropped 17 spots (#892 → #909)
2026-10-05
Warning Issued
Warning: eligibility issues detected
2026-10-03
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-30
Warning Issued
Warning: eligibility issues detected
2026-09-29
Warning Cleared
Warning cleared: eligibility issues resolved
2026-09-28
Warning Issued
Warning: eligibility issues detected
2026-09-25
Rank Moved
Rank dropped 11 spots (#838 → #849)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 226 spots (#1066 → #840)
2026-09-23
HVTrust Changed
HVTrust up 30.2pts (23.1 → 53.3)
2026-09-22
Newly Listed
First tracked at rank #1066
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 14 spots (#793 → #807)
2026-09-10
Activity Resumed
Activity resumed
2026-09-10
Warning Issued
Warning: eligibility issues detected
2026-09-10
Grade Changed
Trust grade D → C
2026-09-10
Rank Moved
Rank rose 256 spots (#1049 → #793)
2026-09-10
HVTrust Changed
HVTrust up 9.3pts (44.7 → 54.0)
2026-09-10
Activity Score Changed
Activity score up 22pts (41 → 63)
2026-09-09
Rank Moved
Rank dropped 19 spots (#1030 → #1049)
2026-09-08
Rank Moved
Rank dropped 12 spots (#1018 → #1030)
2026-09-07
Rank Moved
Rank dropped 36 spots (#982 → #1018)
2026-09-06
Rank Moved
Rank dropped 12 spots (#970 → #982)
2026-09-05
Rank Moved
Rank dropped 49 spots (#921 → #970)
2026-09-04
Rank Moved
Rank dropped 31 spots (#890 → #921)
2026-09-03
Rank Moved
Rank dropped 53 spots (#837 → #890)
2026-09-02
Rank Moved
Rank dropped 47 spots (#790 → #837)
2026-09-01
Rank Moved
Rank dropped 32 spots (#758 → #790)
2026-08-31
Rank Moved
Rank dropped 35 spots (#723 → #758)
2026-08-30
Rank Moved
Rank dropped 26 spots (#697 → #723)
2026-08-29
Scorecard Added
OSSF Scorecard: 1.4/10
2026-08-29
Rank Moved
Rank rose 247 spots (#944 → #697)
2026-08-29
HVTrust Changed
HVTrust up 15.1pts (30.6 → 45.7)
2026-08-28
Rank Moved
Rank dropped 35 spots (#909 → #944)
2026-08-27
Rank Moved
Rank dropped 28 spots (#881 → #909)
2026-08-26
Rank Moved
Rank dropped 108 spots (#773 → #881)
2026-08-16
Rank Moved
Rank dropped 14 spots (#751 → #765)
GitHub → npm: notebooklm-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 49.5 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/notebooklm-mcp-pleaseprompto.svg)](https://hvtracker.net/agents/notebooklm-mcp-pleaseprompto)
HTML:
<a href="https://hvtracker.net/agents/notebooklm-mcp-pleaseprompto"><img src="https://hvtracker.net/badge/notebooklm-mcp-pleaseprompto.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON