timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
First-party Provenote MCP server for drafts, research threads, auditable runs, and knowledge search.
Skills that teach the AI this kind of work; they work alongside this one
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Open-source intelligence for the global theater. Track everything from the corporate/private jets of the wealthy, and spy satellites, to seismic events in one unified interface. Hook an AI agent up to have it parse through data and find previously unseen correlations. The knowledge is available to…
scrape data from Google Maps. Extracts data such as the name, address, phone number, website URL, rating, reviews number, latitude and longitude, reviews,email and more for each place
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 7/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 11/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Claude cannot connect Provenote MCP yet
The maker has not listed install details in the MCP Registry yet
ChatGPT cannot connect Provenote MCP yet
The maker has not listed install details in the MCP Registry yet
Claude Code cannot connect Provenote MCP yet
The maker has not listed install details in the MCP Registry yet
Cursor cannot connect Provenote MCP yet
The maker has not listed install details in the MCP Registry yet
VS Code cannot connect Provenote MCP yet
The maker has not listed install details in the MCP Registry yet
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 20, 2026
The registry name was verified with the GitHub account xiaojiou176-open, which owns the repo
Code last changed 3 months ago
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/xiaojiou176-open-provenote-mcp)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed 3 months ago, and the latest version (1.8.5) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Official Exa MCP for web search, content fetching, and multi-step research.
Official Microsoft Learn MCP Server – real-time, trusted docs & code samples for AI and LLMs.
Search and read Empryo's documentation. Read-only, no auth, no local access.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| This one Provenote MCP | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Teach agents and operators to turn messy long context into structured outcomes they can carry into notes, research threads, drafts, and inspectable results.
Quick Result Path · Long Context · Public Proof · Project Status · Docs
Second ring: MCP & Integrations · Companion Host Bundles · Distribution · FAQ · Discussions
Star Notebooklab if you want a source-heavy AI workbench that stays inspectable after the chat scrollback is gone.
This illustrated overview is a repo-authored summary of the shortest documented path. It is intentionally not presented as a live product recording.
Canonical product path:
messy long context -> structured insight -> note / research thread / draft -> inspectable outcome
That is the first door. MCP, starter bundles, distribution pages, and promotion assets are valuable second-ring surfaces, but they should not outrank the product path.
Agent-facing truth comes first: Notebooklab teaches an agent to read messy context, structure it, move it into note / research-thread / draft lanes, and only then carry that outcome workflow forward through the first-party notebooklab-mcp server. Public skills, host bundles, and registry packs are companion surfaces around that workbench, not the product root.
If you only want the shortest truthful filter before reading deeper, use this table first:
| What you need to know | Current answer |
|---|---|
| Product thesis | turn messy long context into structured insight and inspectable outcomes you can carry into notes, research threads, and drafts |
| Fastest result path | import one source -> run Auditable Markdown -> download one inspectable result |
| First proof | the quick-result overview plus the public proof page |
| Second ring only | MCP, host bundles, public skills, and distribution surfaces |
| What it must never be reduced to | a hosted one-minute trial or a generic chat wrapper |
If you only want the fastest honest map, use this:
| Question | Open this first | Why |
|---|---|---|
| "Can this help with messy long context?" | Long Context | This is the product center, not a side use case. |
| "Can I get one real result quickly?" | Quick Result Path | This is the shortest repo-documented local proof loop. |
| "Is this real or just copywriting?" | Public Proof | This is the evidence layer. |
| "What is still intentionally unclaimed?" | Project Status | This is the boundary page. |
Judge the workbench before you judge the side doors. MCP pages, starter bundles, distribution packs, and promotion assets matter, but they are second-layer surfaces around the main product path.
Most AI note tools make it easy to generate words and hard to verify where those words came from.
That gets even worse when the raw material is long and messy: a huge chat log, a copied forum thread, a meeting recap, or a web page pile you do not want to flatten into one more throwaway summary.
Notebooklab is built for the opposite direction:
Think of it like moving from a loose pile of research tabs to a workbench with labeled drawers, measuring tools, and a clean export lane.
If your problem starts as "I have too much messy context," the strongest current repo-backed answer is not another empty chat box. It is the path from long context to structured notes and then into reusable outcome objects.
If you want one visible outcome before learning the whole workbench, keep the order this short:
That is the shortest repo-documented result path today. MCP, starter bundles, podcasts, and distribution surfaces stay second ring until this outcome path already makes sense.
The strongest current first-entry path is:
Import the source
-> Run Chat Knowledgeization -> Inspect the structured insight -> Continue it as a note or notebook research thread -> Keep draft work inside the notebook lane
In plain language: first turn the pile into labeled folders, then decide whether it belongs in your notes, your active research lane, or your notebook draft workflow.
notebooklab CLI when you want notebook outcome inspection, auditable markdown, or research-thread-to-draft handoffs without treating MCP host setup as the only operator path.If you only remember one first-entry rule, make it this:
messy long context
-> structured insight -> note / seeded research lane / notebook research thread -> draft-adjacent notebook work
That is the product center. MCP host pages come after that path, not before it.
Think of these surfaces like rooms around the main workshop:
| Surface | What it is today | What it is not |
|---|---|---|
| Claude Code / Codex / Cursor / OpenCode pages | repo-backed compatibility guides through the first-party MCP server, with public-ready starter bundles under examples/hosts/ | official partnership, bundled integration, plugin, or marketplace listing |
notebooklab CLI | a first-party local operator surface for outcome inspection and research_thread -> draft -> verify/download workflows | a separate distributed product line or a renamed MCP server |
| public skills surface | tracked public-ready skill packets now exist under public-skills/ for host-specific submission flows | a public skills catalog, live marketplace listing, or host-specific skills program endorsement |
| OpenClaw | a live ClawHub skill listing now exists at https://clawhub.ai/xiaojiou176/notebooklab-mcp-outcome-workflows, and public-ready OpenClaw-compatible bundles still live under examples/hosts/openclaw | official OpenClaw partnership, vendor endorsement, or every other marketplace surface being live |
| Official MCP Registry | a live websiteUrl-backed notebooklab-mcp entry already points to the repo-owned MCP docs/install surface | a package-backed public artifact, official host marketplace listing, or vendor endorsement |
| release / listing / domain / trademark / partnership | external decision and publication work | completed repo-side truth |
If you want the shortest public page that keeps those boundaries honest, start with docs/project-status.md.
If you want repo-owned install artifacts instead of prose-only setup pages, start with examples/hosts/README.md. That index points to the public-ready Claude Code, Codex, Cursor, and OpenCode starter bundles plus the OpenClaw-compatible bundles and the ClawHub submission pack.
If you want the standalone host-facing skill folders used for OpenHands/extensions or ClawHub-style submissions, start with public-skills/README.md.
If you want the full claim ladder instead of inferring it from scattered host pages, use docs/distribution.md.
Once the product path is clear, use one second-ring page instead of reading every host, registry, and distribution page in order.
| If you need... | Open this first | Why it stays second-ring |
|---|---|---|
| a host-compatible MCP path | docs/mcp.md | coding-agent carry-forward matters, but it is not the product center |
| checked-in bundle artifacts | examples/hosts/README.md and examples/hosts/packet-index.json | bundle installs are packaging truth, not the first doorway |
| public claim ladder and listing boundary | docs/distribution.md | it is a truth ledger, not the main product story |
| what is still intentionally unclaimed | docs/project-status.md | this is the boundary page, not the first impression |
| terminal/operator workflows | docs/runbooks/operator-cli.md | the CL