GitingestSAFE
mcp server for gitingest
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
An MCP server for gitingest. This allows MCP clients like Claude Desktop, Cline, Cursor, etc to quickly extract information about Github repositories including
- Repository summaries
- Project directory structure
- File content
https://github.com/user-attachments/assets/c1fa596b-a70b-4d37-91d9-ea5e80284793
Table of Contents
- Installation
- Installing via Smithery
- Install via Github
- Installing Repo Manually
- Updating the MCP client configuration
- Debug
Installation
Installing via Smithery
- To install gitingest-mcp via Smithery:
npx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client claude --config "{}" # Claudenpx -y @smithery/cli@latest run @puravparab/gitingest-mcp --client cursor --config "{}" # Cursornpx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client windsurf --config "{}" # Windsurfnpx -y @smithery/cli@latest install @puravparab/gitingest-mcp --client cline --config "{}" # ClineInstall via Github
- Add this to the MCP client config file
{
"mcpServers": {
"gitingest-mcp": {
"command": "/uvx",
"args": [
"--from",
"git+https://github.com/puravparab/gitingest-mcp",
"gitingest-mcp"
]
}
}
}Installing Repo Manually
- Clone the repo
git clone https://https://github.com/puravparab/Gitingest-MCP cd Gitingest-MCP
- Install depend
be719fa1d0f4OBSERVED · 2026-10-07Connect
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 gitingest-mcp -- uvx gitingest-mcp
{
"mcpServers": {
"gitingest-mcp": {
"command": "uvx",
"args": [
"gitingest-mcp"
]
}
}
}Exposed tools (3)
3 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
git_files | read | |
git_summary | read | |
git_tree | 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
- none-observed
- Network
- declared (1 observation(s))
- 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.
be719fa1d0f4full audit observations/trust-audit/mcp-server/puravparab__gitingest.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-07 | be719fa1d0f4 | SAFE | B | 89 | first audit |
Questions
What is the Gitingest MCP server?
mcp server for gitingest
What tools does Gitingest expose?
3 in total: 3 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Gitingest 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 Gitingest need?
No credential environment variables were found in its source, so it appears to need none.
How does Gitingest run?
It speaks stdio, so it runs as a local process your client starts. It is published on PyPI as gitingest-mcp.
How current is this page?
The grade is for one exact copy of the source (be719fa1d0f4), read on 2026-10-07. The repository is watched and re-audited when it changes.