io.github.instagitai/instagit
NPM · INSTAGIT · SCANNED SEP 20
MCP server for Instagit — AI-powered Git repository analysis for coding agents
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 219 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 284 tokens (~284/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.instagitai/instagit MCP server?
io.github.instagitai/instagit runs locally as an npm package, launched with npx -y instagit. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · instagit
claude mcp add instagitai-instagit -- npx -y instagit
{
"mcpServers": {
"instagitai-instagit": {
"command": "npx",
"args": [
"-y",
"instagit"
]
}
}
} {
"servers": {
"instagitai-instagit": {
"command": "npx",
"args": [
"-y",
"instagit"
]
}
}
} codex mcp add instagitai-instagit -- npx -y instagit
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"instagitai-instagit": {
"type": "local",
"command": [
"npx",
"-y",
"instagit"
],
"enabled": true
}
}
} openclaw mcp add instagitai-instagit --command npx --arg -y --arg instagit
mcp_servers:
instagitai-instagit:
command: "npx"
args: ["-y", "instagit"] {
"McpServers": {
"instagitai-instagit": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"instagit"
]
}
}
} assistant mcp add instagitai-instagit -t stdio -c npx -a -y instagit
{
"mcpServers": {
"instagitai-instagit": {
"command": "npx",
"args": [
"-y",
"instagit"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 0
- Security disclosure: unverified → fail ▼ functional
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/instagit@0.1.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_repo ~284
Analyze any Git repository with AI. Point it at a repo and ask questions about the codebase. Use cases include: - Understanding unfamiliar codebases: 'Explain the architecture and main components' - Code review assistance: 'Review the authentication implementation for security issues' - Documentation generation: 'Document the public API of this library' - Dependency analysis: 'What external services does this app depend on?' - Onboarding help: 'How would I add a new API endpoint following existing patterns?' - Bug investigation: 'Where might null pointer exceptions occur in the data pipeline?' - Migration planning: 'What would it take to upgrade from React 17 to 18?' If you hit a rate limit (429), the user's monthly token credits are exhausted — they can wait for the reset or upgrade their plan. Free-tier repos larger than 2 GB will be rejected with a 413 error; suggest upgrading to Pro or Max for unlimited repo size.
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | string | yes | What to analyze or ask about the codebase |
| ref | string|null | – | Branch, commit SHA, or tag to analyze (default: repository's default branch) |
| repo | string | yes | Repository to analyze. Accepts GitHub URLs (https://github.com/owner/repo), shorthand (owner/repo), GitLab/Bitbucket URLs, or any public Git URL |
No output schema declared.
No examples provided.
What is the io.github.instagitai/instagit MCP server?
io.github.instagitai/instagit is an MCP server listed in the public MCP registry as io.github.instagitai/instagit. MCP server for Instagit, AI-powered Git repository analysis for coding agents. This page covers its npm package (instagit).
Is the io.github.instagitai/instagit MCP server safe to use?
io.github.instagitai/instagit scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.instagitai/instagit MCP server expose?
io.github.instagitai/instagit exposes 1 tool: ask_repo. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.
Is the io.github.instagitai/instagit MCP server still maintained?
io.github.instagitai/instagit is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.instagitai/instagit MCP server under?
io.github.instagitai/instagit declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.