Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Krusch Git is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Git DAG, AST symbol chunking, call-graph blast radius, and hybrid RRF code search MCP server.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user krusch-git-mcp '--' npx -y --package=krusch-git pg-git-mcp
# 2 — ask your agent for something these tools do
# krusch_git_list_repos, krusch_git_read_tree, krusch_git_read_blob and 4 more
Krusch Git costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Krusch Git as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user krusch-git-mcp '--' npx -y --package=krusch-git pg-git-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List all available repositories stored in the database.
No parameter schema on file.
Read the directory structure (DAG node) of a specific repository. If tree_sha/tree_id is omitted or 'HEAD', reads the root tree of the main branch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | Repository name (e.g. 'krusch-git', 'krusch-context-mcp'). |
| project | string | no | Alias for repo. |
| repository_id | number | no | The ID of the repository. |
| tree_sha | string | no | Specific SHA-1 tree hash, or 'HEAD' for root tree. |
| tree_id | string | no | Legacy alias for tree_sha. |
Read the source file contents of a specific blob or file path within a repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | Repository name (e.g. 'krusch-git', 'krusch-context-mcp'). |
| file_path | string | no | Relative file path within repository. |
| blob_id | string | no | The SHA-1 hash of the blob. |
Search code files using Hybrid RRF (BM25 + pgvector), pure semantic vector, or keyword search. Results are decayed by age.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | The search query. |
| repo | string | no | Repository name to filter search (e.g. 'krusch-git', 'krusch-context-mcp'). |
| project | string | no | Alias for repo. |
| repository_id | number | no | Optional repository ID. |
| search_type | string | no | Search mode: 'hybrid' (BM25 + pgvector RRF, default), 'semantic' (pure vector), or 'keyword' (pure BM25). |
| limit | number | no | Number of results to return. |
Search for specific code symbols (functions, classes, methods, routes, markdown sections) across repositories with exact match boost, signatures, and line ranges.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | Function, class, markdown heading, or symbol name to search for. |
| repo | string | no | Repository name to filter search. |
| project | string | no | Alias for repo. |
| symbol_type | string | no | Optional filter for symbol type. |
| limit | number | no | Max symbols to return. |
| repository_id | number | no | Optional repository ID. |
List all code symbols (functions, classes, methods, routes) declared inside a specific file or blob.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repo | string | no | Repository name. |
| file_path | string | no | Relative file path within repository. |
| blob_id | string | no | The SHA-1 hash of the blob. |
Trace symbol dependencies: retrieve outbound imports, inbound callers/dependents, and declared symbols for a specific symbol or file path.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| symbol | string | no | Symbol name to trace callers and dependencies for. |
| file_path | string | no | Relative file path (e.g., 'server/git-engine.js'). |
| repo | string | no | Repository name. |
| project | string | no | Alias for repo. |
| repository_id | number | no | Repository ID. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Krusch Git or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (7 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| krusch_git_list_repos | no tags | |
| krusch_git_read_tree | no tags | |
| krusch_git_read_blob | no tags | |
| krusch_git_semantic_search | no tags | |
| krusch_git_search_symbols | no tags | |
| krusch_git_file_symbols | no tags | |
| krusch_git_dependency_graph | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 1.2.4. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Krusch Git can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.