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)のみ。Web やスマホでは使えません
KARP Inspector を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が KARP Inspector を使っていると言うか、回答に KARP Inspector のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT はまだ KARP Inspector につなげません
KARP Inspector はパソコンに入れて使うものですが、ChatGPT は Web 上で動くサーバーにしかつなげません
Claude Code はまだ KARP Inspector につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · KARP Inspector につなげるアプリを使う
Cursor はまだ KARP Inspector につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · KARP Inspector につなげるアプリを使う
VS Code はまだ KARP Inspector につなげません
提供元はパソコン版 Claude アプリ用のインストールファイルしか用意していません
A · KARP Inspector につなげるアプリを使う
mcpb: …/karp-inspector.mcpbこのサーバーのつなぎ方と、各アプリの公式ドキュメントに基づきます。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)がレジストリに届いたのは昨日です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにMCPBも必要です。
同じカテゴリには:OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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.
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
| これ 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