MCP server that drives a classic Notebook through the nbclassic-mcp-bridge relay
Listed on its own since 2026-09-24. Until then it was part of nbclassic-mcp-bridge, where its earlier checks remain.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"nbclassic-mcp-bridge-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# nbclassic-mcp-bridge-mcp The MCP-server half of [nbclassic-mcp-bridge](https://github.com/jessegrabowski/nbclassic-mcp-bridge): lets an AI assistant read, edit, and run cells in a notebook you have open in the classic Jupyter Notebook (`nbclassic`) UI, and follow your edits as you make them. ```bash pip install nbclassic-mcp-bridge-mcp # in the MCP client's environment ``` Register with your MCP client as the `nbclassic-mcp-bridge` command, passing `JUPYTER_URL` and `JUPYTER_TOKEN`. Requires the [`nbclassic-mcp-bridge`](https://pypi.org/project/nbclassic-mcp-bridge/) package installed in the Jupyter environment. See the repository README for setup and usage.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.