timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
Read-only history of UTM VMs on a Mac: CPU, memory, disk, network, ping, incidents (macOS only).
作者提供的原文
教 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)排序,由以下部分组成
| 热度 | 9/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 21/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
ChatGPT 暂时无法连接 UTM Watch
开发者尚未在 MCP 注册表中填写安装方式
Claude Code 暂时无法连接 UTM Watch
开发者尚未在 MCP 注册表中填写安装方式
Cursor 暂时无法连接 UTM Watch
开发者尚未在 MCP 注册表中填写安装方式
VS Code 暂时无法连接 UTM Watch
开发者尚未在 MCP 注册表中填写安装方式
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月20日
注册名称已通过 GitHub 账户 DarrickBM 验证,该账户拥有此仓库
代码最后更新于5天前
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/darrickbm-utm-watch)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于5天前,最新版本(0.7.1)于8天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。
同一分类中有: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.
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.
cotal.ai actions: product overview, site search, build log, feedback, Cloud waitlist, updates, calls
| 本项 UTM Watch | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| 运行位置 | 需要安装在电脑上 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 是 | 是 | 是 | 否 | 否 |
| 基础检查 | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
See what each of your [UTM](https://mac.getutm.app) virtual machines is doing, and find out why one was slow.
Install · Features · AI diagnosis · Fleet · How it works
UTM shows whether a VM is on or off. Activity Monitor shows two processes with the same name. Neither tells you which VM is eating the CPU, how close you are to running out of memory, or whether the lag your remote user felt came from the VM, the Mac, or the Wi-Fi. UTM Watch does.
| Question | UTM | Activity Monitor | UTM Watch |
|---|---|---|---|
| Which VM is using the CPU? | No | Process names only | Every VM by name |
| How full is each VM's disk? | No | No | Yes, read from the disk image |
| What happened at 3:12 pm? | No | No | Recorded history you can scrub |
| Was it the VM, the Mac or the network? | No | No | Ping and link quality next to VM load |
UTM Watch is an independent project. It is not affiliated with or endorsed by the UTM project.
Requires an Apple silicon Mac. Built and tested on macOS 26; set to run on macOS 14 or later, but older versions are untested.
One command (recommended). Installs the menu bar app into /Applications, then starts the app:
curl -fsSL https://raw.githubusercontent.com/DarrickBM/utm-watch/main/install.sh | bash
The script is short; read it first if you prefer: install.sh.
Or by hand. Download UTMWatch- -macos-arm64.dmg from the latest release, open it, and drag UTM Watch into Applications. The app is not notarized by Apple, so the first time macOS will refuse to open it. Go to System Settings, then Privacy & Security, and click Open Anyway, or run this once:
xattr -dr com.apple.quarantine /Applications/UTMWatch.app
First launch. macOS asks for three permissions: access to data from other apps (UTM's VM files), control of UTM, and the local network (pings to your router and VMs). The app keeps working if you deny one, with less detail.
[!IMPORTANT]
After an update, give the permissions again.
macOS treats the updated app as new. It asks for control of UTM again, and it may refuse UTM's VM files until you turn Full Disk Access for UTM Watch off and on again in System Settings › Privacy & Security, then quit UTM Watch and open it again. If it keeps refusing, use Reset and ask again… in UTM Watch's Settings › Permissions. Until then VMs show without their names, limits or disk usage.
| Part | What it does |
|---|---|
Menu bar app (UTMWatch.app) | Live figures in the menu bar, a hover brief, and a detail window with trend tracks and recorded history. |
MCP server (utmwatch-mcp, inside the app) | Read-only tools over the recorded history, for AI agents. |
History is stored in ~/Library/Application Support/UTM Watch/history.sqlite.
The app bundle contains utmwatch-mcp, a read-only Model Context Protocol server over standard input/output. An agent on this Mac can use it to read the recorded history and work out why a VM was slow. Connect Claude Code with:
claude mcp add utm-watch -- /Applications/UTMWatch.app/Contents/MacOS/utmwatch-mcp
Then ask, for example: "A user says connecting to one of my VMs is sometimes slow. Use utm-watch to find out why."
| Tool | What it answers |
|---|---|
find_incidents | When were VMs slow? Start here when someone reports slowness without a time. |
summarize | What happened over a time range, VM by VM. |
get_moment | Everything recorded at one moment. |
get_metrics | One metric over time for a VM, the Mac or the network. |
list_events | VM starts and stops, memory pressure and swap, VMs at their CPU limit, Wi-Fi and link changes, sleep and wake. |
get_status | The latest sample: every VM, the Mac and the network now. |
list_macs | Every Mac in the fleet (on a Mac that has joined one). |
Access can be switched off in the app's Settings under AI diagnosis.
UTM Watch on one Mac needs nothing below. With several Macs, one of them hosts a hub and the others report to it; the hub Mac can then open Open Fleet from the menu bar item and see every Mac's VMs, and click a Mac for its history. The other Macs only report: they cannot see the fleet.
A Mac that joins uploads its last 24 hours, then new history every ten seconds. If the hub cannot be reached it keeps recording and fills the gap later. The hub Mac has to stay on and logged in.
Macs on other networks. On the hub Mac, under "Connect Macs on other networks", paste an auth key from your own Tailscale account (reusable, tagged, pre-approved). UTM Watch then carries its own hidden Tailscale node: nothing appears in the menu bar or in System Settings, and a Tailscale you already run is left alone. Pairing codes made after that work from any network.
A hub on a server. The same hub runs on Linux:
docker build -f Hub/Dockerfile -t utm-watch-hub . && docker run -d -p 127.0.0.1:8787:8787 -v hub-data:/data utm-watch-hub
docker exec utmwatch-hub token create --enroll --hub http://hub-address:8787 # a pairing code
Paste the code in each Mac's Settings › Fleet and click Join. Add --view to make a code whose Mac may also view the fleet.
AI diagnosis across the fleet. On a Mac that has joined, the MCP server offers list_macs, and every tool takes an optional mac (a name or UUID). Without mac a tool answers for the Mac it runs on, from its own database, exactly as before; that keeps working when the hub is down.
The design is in docs/DESIGN-fleet.md.
UTM Watch reads each VM's process for CPU and memory, its vmenetN interface for network, and its disk image for disk usage, all read-only and without anything installed in the guest. It matches processes to VMs through the disk image each process holds open, and gets names and states from UTM's AppleScript interface. Only NAT ("Shared") networking is supported in this version; bridged VMs show no network.
docs/HOW-IT-WORKS.md explains what each number means, how VMs are identified, the permissions involved and the implementation details.
Requires macOS 26 on Apple silicon and the Swift toolchain from Xcode or the Command Line Tools. The app has no third-party dependencies and needs no root.
Self-checks for the pure logic (Command Line Tools ship no XCTest, so this is a plain executable):
swift run selftest
Scripts/make-app.sh builds and signs build/UTMWatch.app (with your Apple Development certificate if you have one, otherwise ad hoc); Scripts/make-release.sh produces the downloadable archives in dist/. Design notes are in docs/DESIGN-menu-bar-app.md.
Scripts/make-app.sh
open build/UTMWatch.app
To connect Claude Code to a build from source:
claude mcp add utm-watch -- "$(pwd)/build/UTMWatch.app/Contents/MacOS/utmwatch-mcp"
Bug reports and pull requests are welcome. See CONTRIBUTING.md.
MIT. See LICENSE.
Built by DarrickBM
If UTM Watch is useful to you: