# io.github.instagitai/instagit (npm · instagit)

MCP server for Instagit — AI-powered Git repository analysis for coding agents

- Trust score: 68/100 (medium)
- Change this week: +24
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `instagit`: 68/100 (this document), [markdown](https://verifymcp.io/servers/instagitai-instagit/instagit.md), [page](https://verifymcp.io/servers/instagitai-instagit/instagit)

## Channel facts

- Registry: `npm`
- Package: `instagit`
- Version: `0.1.5`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (95 of 99), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 171 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add instagitai-instagit -- npx -y instagit
```

### Codex

```bash
codex mcp add instagitai-instagit -- npx -y instagit
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "instagitai-instagit": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "instagit"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add instagitai-instagit --command npx --arg -y --arg instagit
```

### Hermes

```yaml
mcp_servers:
  instagitai-instagit:
    command: "npx"
    args: ["-y", "instagit"]
```

### Other

```json
{
  "mcpServers": {
    "instagitai-instagit": {
      "command": "npx",
      "args": [
        "-y",
        "instagit"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 67, +48)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] First check of Schema quality: unverified
- [functional] Licence: MIT

### 2026-08-01 (score 19, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 26, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (1)

### `ask_repo` (~284 tokens)

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.

Input parameters:

- `prompt` (string, required): 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, required): Repository to analyze. Accepts GitHub URLs (https://github.com/owner/repo), shorthand (owner/repo), GitLab/Bitbucket URLs, or any public Git URL

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/instagitai-instagit/instagit#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 19
- 2026-07-31: 26
- 2026-07-30: 44
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/instagit
- Socket report: https://socket.dev/npm/package/instagit
- Repository: https://github.com/InstalabsAI/instagit
- Changelog RSS feed: https://verifymcp.io/servers/instagitai-instagit/instagit/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/instagitai-instagit/instagit/changelog.json
- HTML version of this page: https://verifymcp.io/servers/instagitai-instagit/instagit