timesfm
TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.
52 tools for Claude Desktop: filesystem, knowledge graph and code search. Runs locally. Free, MIT.
作者提供的原文
教 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)排序,由以下部分组成
| 热度 | 4/80 | GitHub 星标或每周下载量:较大的计 60,较小的计 20 |
|---|---|---|
| 新鲜度 | 12/12 | 30 天内有发布或代码更新得满分 |
| 仍在响应 | 0/8 | 上次检查时云端端点有响应 |
| 使用分 | 16/100 |
质量: 基础检查通过 3/3 项(仅展示,不用于排序) · 上升势头: 暂无数据 (只用于“上升中”标签)
选择你使用的 AI 应用,然后复制设置。
通过 3/3 项检查 · 在你的电脑上运行
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude,但需要先准备
不需要密钥,不用安装程序 · 仅限电脑上的 Claude 应用(Windows 或 Mac),网页和手机不可用
用 KARP Inspector 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 KARP Inspector,或回答中出现 KARP Inspector 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
ChatGPT 暂时无法连接 KARP Inspector
KARP Inspector 需要安装在你的电脑上,而 ChatGPT 只能连接在网上运行的服务器
Claude Code 暂时无法连接 KARP Inspector
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 KARP Inspector 的应用
Cursor 暂时无法连接 KARP Inspector
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 KARP Inspector 的应用
VS Code 暂时无法连接 KARP Inspector
开发者只提供了电脑版 Claude 应用的安装文件
A · 使用能连接 KARP Inspector 的应用
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
在你的电脑上运行,适用于
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月22日
注册名称已通过域名 souldriver.com.au 验证(注册中心会核实域名所有权)
代码最后更新于昨天
使用 MIT
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/au-souldriver-karp-inspector)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于昨天,最新版本(0.5.0)于昨天进入注册中心。
支持 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.
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
| 本项 KARP Inspector | 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、图片和脚本已被移除。链接会离开本站。
Version: 0.5.0 Author: SoulDriver (Adelaide, Australia) Licence: MIT — free and open source, every tool included
Formerly KARP Inspector Premium. Up to v0.4.0 it was a paid extension with a licence key. From v0.5.0 all 52 tools are free for everyone.
KARP Inspector is a single MCP server that gives Claude everything it needs to understand, navigate, modify, and reason about your codebase — plus a persistent knowledge graph that remembers decisions, tracks changes, and connects code to context.
52 tools. One server. One database. Zero external services.
Everything runs locally. Your code never leaves your machine.
Inspector Lite is the lightweight, search-only sibling. Inspector is the full toolkit.
| Capability | Inspector Lite | Inspector |
|---|---|---|
| Semantic code search | ✅ | ✅ |
| Grep / file outline / diff | ✅ | ✅ |
| Read files | ❌ | ✅ |
| Write / patch files | ❌ | ✅ (atomic, corruption-safe) |
| Move / copy / delete | ❌ | ✅ (soft delete with trash) |
| Find files (glob + filters) | ❌ | ✅ |
| Search & replace (cross-file) | ❌ | ✅ (with dry-run preview) |
| Knowledge graph | ❌ | ✅ (remember, recall, connect) |
| Custom node types | ❌ | ✅ (propose any schema) |
| Semantic graph search | ❌ | ✅ (ONNX embeddings) |
| Repo map (compressed overview) | ❌ | ✅ |
| Dependency graph | ❌ | ✅ (with circular dep detection) |
| Impact analysis | ❌ | ✅ (blast radius + symbol tracking) |
| Dead code detection | ❌ | ✅ |
| TODO / FIXME scanner | ❌ | ✅ |
| Security audit | ❌ | ✅ (secrets, keys, high-entropy) |
| Git checkpoint | ❌ | ✅ (or SQLite fallback) |
| Undo / rollback | ❌ | ✅ (snapshot-based revert) |
| Run terminal commands | ❌ | ✅ (pre-approved patterns only) |
| Disk usage analysis | ❌ | ✅ |
| File checksums | ❌ | ✅ (SHA256) |
| Unified database | ❌ | ✅ (single SQLite file) |
| Version history | File snapshots | SQLite snapshots (searchable) |
| Index observability | ❌ | ✅ (list, status, forget, export/import) |
| Server diagnostics | ❌ | ✅ (server_status) |
| Total tools | 9 | 52 |
karp-inspector.mcpb from the latest release.Then ask Claude to run server_status: it should report version 0.5.0 and 52 tools.
The server runs directly via stdio (no proxy, no background process) — same pattern as every other KARP MCP server.
The new extension installs under a different name, so it sits alongside the old one. Disable or remove KARP Inspector Premium first so the two never write to the same database at once, then install KARP Inspector and choose the same Data Folder you used before. Your knowledge graph, code index and snapshots carry straight over: the database file names (premium.db, premium-*.db) are unchanged for exactly this reason. There are no licence fields any more, so there's nothing to enter.
git clone https://github.com/souldriver007/karp-inspector.gitnpm install, then npm run download-model (the embedding model isn't committed to git; about 33MB)claude_desktop_config.json:{
"mcpServers": { "karp-inspector": { "command": "node", "args": ["C:\\path\\to\\karp-inspector\\server\\index.js"], "env": { "ALLOWED_DIRS": "C:\\Users\\You\\Projects;D:\\Code", "DATA_PATH": "C:\\path\\to\\your\\chosen\\data\\folder", "ALLOWED_COMMANDS": "node --check" } } } }
ALLOWED_COMMANDSabove is the safe default. Addingnpm test,npm run buildorpytestlets the project you point at execute its own code — only do that for repositories you trust.
npm install
npm run download-model npm run build
The extension is written to dist/karp-inspector.mcpb.
Linux (x64): run installs as
ONNXRUNTIME_NODE_INSTALL_CUDA=skip npm install(ornpm ci). Otherwise onnxruntime-node's install script tries to download optional GPU binaries, and that download currently fails. Inspector only needs the CPU binaries, which are already in the package.
npm run smoke
Spawns the server and drives it over stdio with a real JSON-RPC client — no Claude Desktop, no GUI, no SDK dependency. 32 assertions, a few seconds.
Every assertion corresponds to something that actually broke during development, so this is a regression net rather than a formality:
| Assertion | The bug it guards against |
|---|---|
set_project outside the boundary is denied | The directory sandbox once covered only one module in four, making grep_code an arbitrary-file reader |
Two roots sharing a README.md both index | Chunk ids were filepath:line, so any two projects sharing a relative path collided on the primary key |
A one-line const a = () => {}, b = () => {} indexes | Two chunks with the same start line produced duplicate ids |
index_project returns chunks > 0 | File hashes committed before chunks; an interrupted run left the index claiming N files with zero chunks, unrecoverable |
search_code ranks the right file first | Proves the vectors are meaningful, not merely present |
| Hybrid finds a file semantic search misses | count-lines.js contains totalLines; semantic search returned countFiles and countRows instead |
Export records embedding_dtype | An index recording only the model name imports cleanly into a server on the other precision and returns plausible nonsense |
Deleting a file yields pruned: 1 | Deleted files' chunks previously survived forever |
| Ambiguous relative path errors | resolveInRoots used to return the first match and call it an answer |
security_audit, git_checkpoint, run_check and export → import all run | Before v0.5.0 these were licence-gated, so CI only reached them when licence secrets were set, and import_index shipped broken because nothing exercised it |
The fixture is created under the OS temp directory, which on macOS is a symlink into /private/var/... — so the run also exercises the realpath handling in assertAllowed.
CI runs the same suite on macOS, Windows and Linux on every push, covering every tool, including run_check's non-Windows which branch. See .github/workflows/smoke-test.yml.
search_code runs two rankers over the same chunks and fuses the results.
Semantic compares the query's embedding against each chunk's. Good at concepts — "validate a token before the request runs" finds the middleware even though it never uses those words.
Literal scores term frequency over each chunk's text and name, with identifiers split on camelCase and snake_case so totalLines matches "total lines". Good at the thing semantic search is worst at: you half-remember an identifier, a config key, or an error string.
Fusion uses Reciprocal Rank Fusion — Σ 1/(60 + rank) across both lists. RRF works on ranks rather than raw scores, which matters because cosine similarity and term frequency aren't on comparable scales. Every result reports semantic_score, lexical_score and the fused rrf value, so a ranking can be explained rather than taken on trust.
Why both: on a real codebase, a query for "count the number of lines of code" returned countFiles, countRows and getRecordCounts from semantic search alone — and missed a file named count-lines.js containing totalLines. Literal matching finds it instantly. Neither ranker is sufficient by itself.
Pass mode: "semantic" or mode: "literal" to force one.
A note on queries. Search quality depends more on vocabulary than on any setting. Search the way the code is *written*, not the way you'd describe it to a colleague — "service worker cache" rather than "works offline". The embedding model matches vocabulary in context; it does not reliably infer that caches.match() means offline support.
Text and source files up to 1MB:
.py .js .jsx .ts .tsx .html .css .md .txt
.sql .sh .ps1 .bat .go .rs .java .cs .rb .php .vue .svelte .kt .swift .c .h .cpp .hpp .scala .ex .exs
Config and data formats (.json, .yaml, .toml, .ini) are deliberately not indexed: generated files like package-lock.json crowd out real code in search results. grep_code reads straight from disk, so literal lookups in those files still work.
Three of these get structural parsing rather than fixed-size windows:
acorn is parsed as JavaScript with correct absolute line numbers, inline is skipped, and remaining markup is chunked as prose only when it reads like prose rather than a navigation menuEverything else is chunked into overlapping windows, which works acceptably for uniform content.
.gitignore is respected, along with a default skip list (node_modules, .git, dist, build, __pycache__ and similar). If a root contains nothing indexable, index_project says so and lists what it looks for, rather than reporting a successful index of nothing.
| Environment Variable | Required | Description | Example |
|---|---|---|---|
ALLOWED_DIRS | Required (manual config) | Semicolon-separated list of directories the server may access. There is no unrestricted mode — if this is empty and no project_dirs are passed, every filesystem, search and analysis tool refuses to run. The .mcpb extension config uses project_dirs (a folder picker, see below) instead of this env var — both feed the same boundary. | C:\Users\Me\Desktop;D:\Projects |
DATA_PATH | Required via .mcpb config screen (Data Folder); optional in manual config | Where the unified SQLite database is stored, including automatic snapshots (DATA_PATH/snapshots/). Manual-config default is ~/.karp-premium (the name dates from the Premium release and is kept so existing data still loads). | C:\path\to\data |
ALLOWED_COMMANDS | Optional | Semicolon-separated command prefixes for run_check. Defaults to node --check only. Leave empty to disable terminal execution entirely. Adding test or build runners lets a project execute its own code — npm test/npm run build run scripts from that project's package.json, and pytest runs its conftest.py. Only add them for repositories you trust. | node --check;npm test;pytest |
TRASH_DIR | Optional | Where soft-deleted files go. Defaults to DATA_PATH/trash. | C:\path\to\trash |
Users configure these two fields via Claude Desktop's built-in settings UI when installing the .mcpb. data_path is a single folder picker; project_dirs is a multi-select folder picker ("multiple": true) — click it again to add more folders, and it expands to as