timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Operational memory for the machine your AI works on: what failed here, what is verified, its state
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 | 0/80 | Estrellas de GitHub o descargas semanales: la mayor cuenta 60, la menor 20 |
|---|---|---|
| Actualidad | 12/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 | 12/100 |
Calidad: Pasó 2/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ó 2/3 revisiones · Funciona en tu computadora
Primero: ¿qué IA usas?
Elige tu app y los pasos aparecen abajo.
Funciona con Claude, pero hay que preparar algo antes
Sin clave y sin instalar nada · Solo en la app de Claude para computadora (Windows o Mac), no en la web ni en el móvil
Descargar el archivo .mcpb del creador
El archivo .mcpb viene directo del autor; no lo modificamos
Usa CoreScout y dime qué puedes hacer por mí; luego muéstrame una cosa✓ Si Claude dice que está usando CoreScout o muestra una herramienta de CoreScout en la respuesta, ya está conectado
Nombres de menú comprobados con la ayuda de Anthropic el 11 nov 2026 · tu pantalla puede variar un poco según la versión
ChatGPT todavía no puede conectar CoreScout
CoreScout se instala en tu computadora, pero ChatGPT solo conecta servidores que funcionan en la web
A · Usa una app que pueda conectar CoreScout
Claude Code todavía no puede conectar CoreScout
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar CoreScout
Cursor todavía no puede conectar CoreScout
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar CoreScout
VS Code todavía no puede conectar CoreScout
El autor solo ofrece un instalador para la app de Claude de escritorio
A · Usa una app que pueda conectar CoreScout
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
mcpb: …/CoreScout.mcpbSegún cómo se conecta este servidor y la documentación de cada app, comprobado el 10 nov 2026.
Se ejecutan en tu computadora en
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
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 19 nov 2026
Quien lo publicó (tensorust.com) no es el dueño del repo (Mattbusel); puede que otra persona lo haya listado
Último cambio de código: hace 3 días
Usa Apache-2.0
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
No revisado: solo se pueden revisar paquetes npm y PyPI con versión
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/servers/tensorust-corescout)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ó 2 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 días, y la última versión (1.4.0) llegó al registro hace 3 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas MCPB en tu computadora.
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 CoreScout | 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 | 2/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| Licencia | Apache-2.0 | 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.
Your AI stops rediscovering the same failures every session: CoreScout remembers what happened on your machine and tells your AI before it repeats a mistake.
Why this over the alternatives: Notes files and memory prompts only hold what someone wrote down. CoreScout observes it, and labels what it has verified separately from what it has only seen together. Free, open source, local-first, with an MCP server.
Guarantee: if it doesn't do what this README says, open an issue and I'll fix it.
Your AI forgets everything between sessions. CoreScout lets the computer remember what went wrong, test what actually fixes it, and tell the next AI.
Free, open source, and local-first: no account, no server, no telemetry. Written in Rust, with a desktop app and an MCP server so Claude Code, Claude Desktop, Cursor or any MCP client can ask it questions.
| You have | Get |
|---|---|
| Windows 10 or 11 | CoreScoutSetup.exe (desktop app + background service + MCP bridge) |
| Mac (Apple Silicon or Intel) or Linux | the .tar.gz for your machine from Releases |
| Rust | cargo install corescout-cli corescout-service corescout-mcp |
No admin rights, and no Node, Python, WSL or Docker. The downloads are not signed yet, so Windows may say "unknown publisher" (More info, then Run anyway) and a Mac wants right-click, Open. Every file's SHA-256 is in SHA256SUMS.txt on the release page.
claude mcp add corescout --scope user -- "C:\Program Files\CoreScout\corescout-mcp.exe"
The app's AI screen writes the config for other clients, and can add a hook so every tool call is recorded without the AI having to remember.
Those numbers are what CoreScout returned on the author's PC on 2026-10-04, after a few weeks of real use. It caught a rebuild script that failed every time and was never checked afterwards. It has not yet promoted anything to Verified there, because a claim only gets that label after enough coin-flip trials. It would rather tell you that than invent a win.
Most tools that "learn" just notice that two things happened together and act on it. That is how you end up with superstitions. CoreScout keeps the two apart, and the labels never blur:
| label | means |
|---|---|
| Seen together | Two things kept happening together. CoreScout has not tested whether one causes the other. |
| Verified | CoreScout let a coin flip decide whether to try the change, then measured the difference. |
It also never prints 0% for something it has never measured. A capability that has never run reads *never used*, because zero out of zero is not zero per cent.
Your AI starts every session from nothing. The build that fails the same way each time, the deploy that reports success forty seconds before the service is reachable, the test that only breaks when the machine is busy: it rediscovers all of that, every time, and then the window closes.
Nobody writes any of it down, because the thing that would know is the computer, and computers do not learn from their own experience.
The model doesn't learn from every task. Its computer does.
Everything stays on your computer. No account, no server, no telemetry.
After a while, the Home screen says something like:
Your computer is learning how to work with Claude Code.
Today 3 useful patterns learned 1 capability created 2 beliefs retired
Latest Regenerate schema, then build Verified Builds here read a generated file that goes stale. strong evidence · 94% of 12 uses worked
Open any of it and you get the evidence: what was observed, how many times, whether it was tested or merely noticed, what the alternative was, and what happened. That is the whole point. A tool that tells you what to do without telling you how it knows is asking for trust it has not earned.
Four modes, and you can change them at any time.
| Observe | Watches and learns. Changes nothing. |
| Suggest | Recommends improvements. You approve every change. *(the default)* |
| Assist | Makes small reversible changes on its own. Anything bigger waits for you. |
| Autopilot | Applies changes it has verified, inside limits you set. |
Raising the mode never widens what CoreScout may touch; that is a separate setting, and no mode overrides it. There is a Pause that stops everything immediately, and it is checked before anything else in the system. See SECURITY.md.
corescout run -- <cmd> Run something, measure it exactly, record it
corescout connect Set an AI up to report its work automatically corescout status Is it running, and what is connected corescout learned Everything it has learned corescout explain The evidence behind one of those corescout failures Operations that recur and go wrong here corescout hypotheses What it is testing and cannot yet answer corescout ai setup How to connect an AI corescout mode assist Change how much it may do corescout pause Stop everything now corescout privacy Exactly what is stored, and where
--json on any of them gives the same object the application receives.
your machine
↓ computational mirror what this computer physically is, right now ↓ machine experience what it has been like to be this machine ↓ science falsifiable claims, and what refutes them ↓ concepts structure it found and named itself ↓ AI operational experience what working with an AI has taught it ↓ capabilities procedures that survived being tested ↓ your AI through one standard tool interface ↓ bounded changes scoped, reversible, audited, visible ↓ your machine again
The first time this ran on hardware (a 13th Gen Intel Core i7-13700KF, 16 physical cores, 24 logical), it made over 900 reflections in 36 seconds:
86 observable parts × 9 channels
32 recurring states discovered, which nothing told it to look for 3 concepts promoted, 29 refused knowing which state it was in reduced prediction error by 42.4%
Its own account of itself, generated from what it had measured:
I distinguish 32 recurring states of myself, which I found rather than being
told about.
I do not predict my own next state better than assuming nothing changes.
Both of those are in REAL.md, along with the lineage experiment that returned −4.1% and the four bugs only real hardware could expose. The project's habit is to publish the results that go the wrong way, and the product kept it.
CoreScout began as an experiment about whether a machine can discover useful structure in itself: falsifiable hypotheses, concepts it coins and refuses, association held apart from causal evidence, beliefs withdrawn when the evidence ages out. All of that is still here and still runs, under corescout-lab.
pwsh scripts/release.ps1 builds CoreScoutSetup.exe into dist/ (details in WINDOWS.md); cargo build --release -p corescout-cli -p corescout-service -p corescout-mcp builds just the programs.
cargo test --workspace # ~1,300 tests
cargo clippy --workspace --all-targets cargo fmt --all -- --check pwsh scripts/release.ps1 # installers into dist/
The desktop shell is deliberately outside the Cargo workspace, so the tests above still run in seconds.
CoreScout is local-first. Everything it records stays in %LOCALAPPDATA%\CoreScout\ on the machine that produced it.