updated 2026-08-12 05:02 UTC

NotebookLM MCP

roomi-fields/notebooklm-mcp

Google NotebookLM over MCP + a local HTTP REST API. Citation-backed Q&A, audio/video/content generation, multi-account r

MCP Servers TypeScript Grade D Listed MIT
23.0/100
Rank #927 of 1283
Compare NotebookLM MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade D · 1/5 signals
Last push
2026-08-07 · 5d ago
Recent change
Rank +1

Is NotebookLM MCP safe? NotebookLM MCP scores 23.0/100 (Grade D), ranked #927 of 1283 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 6% of recent commits are signed; last pushed 2026-08-07. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#464 XamlMcp — 23.0 (D) → #465 Cli Microsoft365 MCP Server — 23.0 (D) → #467 Prometheus MCP Server — 22.9 (D) → #468 Agent Search MCP — 22.9 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 53 spots (#865 → #918)
2026-08-08
Newly Listed
First tracked at rank #862
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
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.
Compare with another agent Get email alerts for NotebookLM MCP View MCP Servers Report missing data
66.6
Activity sub-score · out of 100
#466
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 D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 5 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
151
Forks
49
Last Push
2026-08-07
5 days ago
Commits (4 wk)
49
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
7
Rank Change
=
was #927

Analysis

HVTrust Dimensions vs MCP Servers

23.0 / 100 · 40.0% confidence

NotebookLM MCP MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
0.3 / 25
4.7 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
18.4 / 20
6.0 above avg 12.4
AdoptionLog-scaled stars · package downloads
5.2 / 20
0.6 below avg 5.8

Activity Inputs

66.6 / 100
StarsRepository reach
13.1 / 30
FreshnessLast push recency
24.3 / 25
ActivityRecent commits
21.2 / 25
CommunityFork signal
7.9 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
6%
of last 100 commits verified

Is NotebookLM MCP safe?

Public trust evidence for NotebookLM MCP 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 publish package provenance?
No published build provenance is currently detected for NotebookLM MCP. 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 have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for NotebookLM MCP. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is NotebookLM MCP actively maintained?
Actively maintained. The repository was pushed to within the last 5 day(s).
What license does NotebookLM MCP use?
NotebookLM MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are NotebookLM MCP's commits signed?
6% of the last 100 commits to NotebookLM MCP 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 appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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

Maintain NotebookLM MCP?

For maintainers

HVTrust scores NotebookLM MCP 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
Listed 1Rank 1
2026-08-10
Rank Moved
Rank dropped 53 spots (#865 → #918)
2026-08-08
Newly Listed
First tracked at rank #862
GitHub → npm: @roomi-fields/notebooklm-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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