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)은 어제 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 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.
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