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
教 AI 做这类工作的 Skill,可与本项一起使用
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
列表按使用分(满分 100)排序,由以下部分组成
| 热度 | 0/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 12/100 |
质量: 基础检查通过 2/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 2/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 CoreScout 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 CoreScout,或回答中出现 CoreScout 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 CoreScout
CoreScout 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
Claude Code 暂时无法连接 CoreScout
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 CoreScout 的应用
Cursor 暂时无法连接 CoreScout
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 CoreScout 的应用
VS Code 暂时无法连接 CoreScout
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 CoreScout 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
发布者(tensorust.com)不是仓库所有者(Mattbusel);可能是其他人代为上架的
代码最后更新于3天前
使用 Apache-2.0
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/tensorust-corescout)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 2 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于3天前,最新版本(1.4.0)于3天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 MCPB。
同一分类中有:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
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.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 CoreScout | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 2/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | Apache-2.0 | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.