Remote MCP · Endpoint

NotebookLM MCP server

No. NotebookLM answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_notebooklm

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/notebooklm-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
49 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Google NotebookLM via natural language: create notebooks, add sources (PDF, URL, YouTube) and ask gr
Listing
From the official MCP registry (active).
Recent checks of NotebookLM
CheckedResultHandshake
1 day agoHandshake completed49 ms
4 days agoHandshake completed55 ms
5 days agoHandshake completed38 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed202 ms
9 days agoHandshake completed3.29 s
12 days agoHandshake completed58 ms
13 days agoHandshake completed57 ms
15 days agoHandshake completed970 ms
16 days agoHandshake completed68 ms
18 days agoHandshake completed58 ms
19 days agoHandshake completed137 ms
20 days agoHandshake completed51 ms
20 days agoHandshake completed60 ms
21 days agoHandshake completed3.20 s
23 days agoHandshake completed91 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with NotebookLM and makes no claim about it beyond what these checks measured.