Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
@rethunk/mcp-multi-root-git
git tools over MCP: status, multi-root inventory, HEAD parity, presets, logs, structured and raw diff views, commit inspection, fetch, stash, tag, batch commit, push, merge, cherry-pick, worktrees, soft-reset, blame, branch listing, and reflog. Install and MCP client wiring: [docs/install.md](docs/install.md) only — do not duplicate those steps elsewhere.
Repository: github.com/Rethunk-AI/mcp-multi-root-git · npmjs (manual releases): @rethunk/mcp-multi-root-git · GitHub Packages (CI on each tag): @rethunk-ai/mcp-multi-root-git — see docs/install.md and HUMANS.md Publishing.
Documentation
| Doc | Audience |
|---|---|
| [docs/install.md](docs/install.md) | Single source for prerequisites, running the package, and every supported MCP client (plus from-source and troubleshooting) |
| [docs/mcp-tools.md](docs/mcp-tools.md) | Tool ids, client naming, format / JSON, resource URI, workspace root resolution (canonical reference) |
| [schemas/index.json](schemas/index.json) | Published JSON schemas for all MCP tool parameters (JSON Schema draft 2020-12 format) |
| [HUMANS.md](HUMANS.md) | Preset file, dev commands, CI, publishing |
| [AGENTS.md](AGENTS.md) | Contributors: implementation map (src/server/ + entry src/server.ts), contract bumps, CI |
| [CONTRIBUTING.md](CONTRIBUTING.md) | Dev setup, hooks, commit conventions, release checks, and how to add tools |
| [SECURITY.md](SECURITY.md) | Disclosure policy, threat model, and repository safety guidance |
| [specs/README.md](specs/README.md) | Active / done / parked specification layout used for repo planning |
Tools at a glance: see the table in [docs/mcp-tools.md](docs/mcp-tools.md).
JSON Schemas
All MCP tool parameters are published as JSON Schema (draft 2020-12) documents in the [`schemas/`](schemas/) directory. Tools and validators can use these schemas to validate tool input arguments without reading source code.
Schema files:
schemas/index.json— Index of all 20 tool schemas with file pathsschemas/{tool_name}.json— Individual schema for each tool (e.g.,schemas/batch_commit.json,schemas/git_status.json)
For programmatic use, read schemas/index.json to discover available tools and their schema files.