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 que enseñan a la IA este tipo de trabajo; funcionan junto a este
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
Las listas se ordenan por una puntuación de uso (sobre 100) con estas partes
| Popularidad | 4/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 7/12 | Puntuación completa con una versión o cambio de código en 30 días |
| Sigue respondiendo | 0/8 | El endpoint en la nube respondió en la última revisión |
| Puntuación de uso | 11/100 |
Calidad: Pasó 3/3 revisiones básicas (se muestra, no ordena) · Impulso: Sin datos aún (Solo se usa en la pestaña En auge)
Elige la app de IA que usas y copia la configuración.
Pasó 3/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Claude todavía no puede conectar Provenote MCP
El autor aún no ha puesto cómo instalarlo en el registro MCP
ChatGPT todavía no puede conectar Provenote MCP
El autor aún no ha puesto cómo instalarlo en el registro MCP
Claude Code todavía no puede conectar Provenote MCP
El autor aún no ha puesto cómo instalarlo en el registro MCP
Cursor todavía no puede conectar Provenote MCP
El autor aún no ha puesto cómo instalarlo en el registro MCP
VS Code todavía no puede conectar Provenote MCP
El autor aún no ha puesto cómo instalarlo en el registro MCP
Otras apps que usan MCP, como Windsurf, Zed o Gemini CLI, añaden servidores de forma distinta. Míralo en la lista de apps
Ver todas las apps que usan MCP →
La configuración JSON está en “Para desarrolladores”, abajo
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 20 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub xiaojiou176-open, dueña del repo
Último cambio de código: hace 3 meses
Usa MIT
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/xiaojiou176-open-provenote-mcp)Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Aún no hay reseñas
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 3 de 3 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
El registro no indica ninguna clave obligatoria, aunque algunos servidores te piden iniciar sesión la primera vez que los usas.
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez hace 3 meses, y la última versión (1.8.5) llegó al registro hace 7 meses.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code.
En la misma categoría: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Misma categoría, otros creadores, comandos ya revisados. Primero los oficiales, luego por estrellas.
Cómo leer una tarjeta:↓ Descargas por semanai★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
Keyword research, site audits, rank tracking and AI visibility for your AI agent.
Connect AI agents to Exa 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
| Este Provenote MCP | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Dónde se ejecuta | Se instala en tu equipo | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada | Funciona en la nube, sin instalar nada |
| Necesita clave | No | No | No | No | No | No |
| Se añade con + en Claude | No | Sí | Sí | Sí | No | No |
| Revisiones básicas | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| Licencia | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Precio | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro | Sin coste en el registro |
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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