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.
Skills that teach the AI this kind of work; they work alongside this one
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
Lists are ordered by a usage score (out of 100) built from these parts
| Popularity | 4/80 | GitHub stars or weekly downloads: the larger counts 60, the smaller 20 |
|---|---|---|
| Freshness | 12/12 | Full marks for a release or code change within 30 days |
| Still answering | 0/8 | The cloud endpoint answered at the last check |
| Usage score | 16/100 |
Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)
Pick the AI app you use, then copy the settings.
Passed 3/3 checks · Runs on your computer
First: which AI do you use?
Pick your app and the steps appear below.
Works with Claude, with some setup first
No key, nothing to install · Only the Claude desktop app (Windows or Mac), not the web or phone
Download the maker’s .mcpb file
The .mcpb file comes straight from the maker; we do not change it
Use KARP Inspector and tell me what you can do for me, then show me one thing✓ If Claude says it is using KARP Inspector or shows a KARP Inspector tool in the answer, you are connected
Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version
ChatGPT cannot connect KARP Inspector yet
KARP Inspector runs on your computer, but ChatGPT can only connect servers that run on the web
A · Use an app that can connect KARP Inspector
Claude Code cannot connect KARP Inspector yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect KARP Inspector
Cursor cannot connect KARP Inspector yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect KARP Inspector
VS Code cannot connect KARP Inspector yet
The maker only provides an installer for the Claude desktop app
A · Use an app that can connect KARP Inspector
mcpb: …/karp-inspector.mcpbBased on how this server connects and on each app’s own docs, checked Nov 10, 2026.
Run on your computer in
ClaudeGooseLM StudioMsty StudioCherry StudioVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 22, 2026
The registry name was verified against the domain souldriver.com.au (the registry checks domain ownership)
Code last changed yesterday
Uses MIT
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Not checked: only npm and PyPI packages with a version can be checked
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/servers/au-souldriver-karp-inspector)Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
No reviews yet
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed yesterday, and the latest version (0.5.0) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
In the same category: OpenSEO, Exa, Microsoft Learn MCP, Docs, COTAL actions (cotal.ai)
Same category, other makers, commands already checked. Official ones first, then by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
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
| This one KARP Inspector | OpenSEO | Exa | Microsoft Learn MCP | Docs | COTAL actions (cotal.ai) | |
|---|---|---|---|---|---|---|
| Runs where | Installs on your computer | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install | Runs in the cloud, nothing to install |
| Needs a key | No | No | No | No | No | No |
| Add with + in Claude | No | Yes | Yes | Yes | No | No |
| Basic checks | 3/3 | 5/5 | 2/4 | 4/4 | 4/4 | 4/4 |
| License | MIT | MIT | MIT | CC-BY-4.0 | NOASSERTION | Apache-2.0 |
| Price | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry | No cost listed in the registry |
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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