Git IngestSAFE
A Model Context Protocol (MCP) server that helps read GitHub repository structure and important files.
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://smithery.ai/server/mcp-git-ingest)
A Model Context Protocol (MCP) server that helps read GitHub repository structure and important files.
Inspired by gitingest.
Configuration
{
"mcpServers": {
"mcp-git-ingest": {
"command": "uvx",
"args": ["--from", "git+https://github.com/adhikasp/mcp-git-ingest", "mcp-git-ingest"],
}
}
}Usage
Using mcp-client-cli:
$ llm read https://github.com/adhikasp/mcp-git-ingest and determine how the code technically works I'll help you understand the technical details of the mcp-git-ingest repository. I'll first fetch the directory structure and then read the important files to analyze how the code works. Tool Calls: github_directory_structure Args: repo_url: https://github.com/adhikasp/mcp-git-ingest Now, I'll read the important files to understand the technical implementation: Tool Calls: github_read_important_files Args: repo_url: https://github.com/adhikasp/mcp-git-ingest file_paths: ['README.md', 'src/mcp_git_ingest/main.py', 'pyproject.toml'] Let me break down how this code technically works: 1. Purpose: The `mcp-git-ingest` is a Model Context Protocol (MCP) server designed to help read GitHub repository structures and important files. It provides two main tools: - `github_directory_structure`: Returns a tree-like representation of a repository's directory structure - `github_read_important_files`: Reads and returns the contents of specified files in a repository 2. Technical Implementation: a. Dependencies: - Uses `fastmcp` for creating an MCP server - Uses `gitpython` for Git repository operations - Requires Python 3.8+ b. Key Function
dc9245892939OBSERVED · 2026-10-03Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add mcp-git-ingest -- uvx mcp-git-ingest
{
"mcpServers": {
"mcp-git-ingest": {
"command": "uvx",
"args": [
"mcp-git-ingest"
]
}
}
}Exposed tools (2)
2 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
git_directory_structure | read | |
git_read_important_files | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (2 observation(s))
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (0)
No findings outside the package's declared scope.
Gates applied: no_behavioural_pass.
dc9245892939full audit observations/trust-audit/mcp-server/adhikasp__git-ingest.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-03 | dc9245892939 | SAFE | B | 89 | first audit |
Questions
What is the Git Ingest MCP server?
A Model Context Protocol (MCP) server that helps read GitHub repository structure and important files.
What tools does Git Ingest expose?
2 in total: 2 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Git Ingest safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Git Ingest need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (dc9245892939), read on 2026-10-03. The repository is watched and re-audited when it changes.