# io.github.bikemeardsley/git-for-me (npm · git-for-me)

Which parts of what you want to build open source already covers. Every repo checked live.

- Trust score: 68/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- npm · `git-for-me`: 68/100 (this document), [markdown](https://verifymcp.io/servers/bikemeardsley-git-for-me/git-for-me.md), [page](https://verifymcp.io/servers/bikemeardsley-git-for-me/git-for-me)

## Channel facts

- Registry: `npm`
- Package: `git-for-me`
- Version: `0.1.1`
- 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-10-17.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/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 1 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 521 tokens (~173/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 92/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 75% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.bikemeardsley/git-for-me MCP server?

io.github.bikemeardsley/git-for-me runs locally as an npm package, launched with npx -y git-for-me. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add bikemeardsley-git-for-me -- npx -y git-for-me
```

### Cursor

```json
{
  "mcpServers": {
    "bikemeardsley-git-for-me": {
      "command": "npx",
      "args": [
        "-y",
        "git-for-me"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bikemeardsley-git-for-me": {
      "command": "npx",
      "args": [
        "-y",
        "git-for-me"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add bikemeardsley-git-for-me -- npx -y git-for-me
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add bikemeardsley-git-for-me --command npx --arg -y --arg git-for-me
```

### Hermes

```yaml
mcp_servers:
  bikemeardsley-git-for-me:
    command: "npx"
    args: ["-y", "git-for-me"]
```

### Netclaw

```json
{
  "McpServers": {
    "bikemeardsley-git-for-me": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "git-for-me"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add bikemeardsley-git-for-me -t stdio -c npx -a -y git-for-me
```

### Other

```json
{
  "mcpServers": {
    "bikemeardsley-git-for-me": {
      "command": "npx",
      "args": [
        "-y",
        "git-for-me"
      ]
    }
  }
}
```

## 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-10-15 (score 68, +29)

- [security improvement] Injection markers: unverified → pass
- [security] First check of Judged manipulation: pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] MCP protocol: unverified → pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 75
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: good
- [functional] Package version: 0.1.0 → 0.1.1

### 2026-10-14 (score 39)

First indexed and scored.

## MCP tools (3)

### `git_for_me` (~280 tokens)

Git for me!

Step 1 of 3, before recommending any open-source repo or writing something that might already exist. If stack, platform, license or upkeep is missing, returns the questions to ask the user first: call again with the answers ("unknown" is fine). Then returns the method: split what the user wants to build into parts, search GitHub, GitLab and Codeberg for each with git_for_me_search, and decide from what it finds which parts an existing repo covers (use it as is or adapt it), which nothing covers (build it), and which are not worth a dependency (write them). Follow it.

Input parameters:

- `license` (string): What the result may be used for, such as "commercial, closed source" or "open source"
- `need` (string, required): What you want to build, in plain words: what goes in, what should come out, and what it is for
- `platform` (string): Where it will run, such as "a web app", "a CLI" or "a server"
- `stack` (string): What it will be written in, such as "TypeScript on Node" or "Python 3.12"
- `upkeep` (string): How much code you are willing to own, such as "needs to stay maintained" or "happy to own a fork"

### `git_for_me_search` (~101 tokens)

Git for me! (searched live)

Step 2 of 3: searches for each part: on GitHub the topic's most starred and rising repos, names and descriptions holding each keyword, and README text; on GitLab and Codeberg the topic and the keywords. Returns what it found, with stars, license, language, last activity and how each turned up, to pick each part's verdict and candidates from. Then call git_for_me_verify.

Input parameters:

- `parts` (array, required)

### `git_for_me_verify` (~140 tokens)

Git for me! (checked live)

Step 3 of 3: checks every picked repo live on its forge, drops the ones that are not there, flags no license, copyleft, archived, stale, little used, forks and mirrors, marks picks the search didn't turn up as from memory, shows what it found that wasn't picked, and returns the report to show the user. If nextAction is SEARCH_FIRST or RECALL_REPLACEMENTS, do what its instructions say and call again.

Input parameters:

- `components` (array, required)
- `need` (string, required): What you want to build, in plain words: what goes in, what should come out, and what it is for

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/bikemeardsley-git-for-me/git-for-me#diagnostics

## Score history

- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 39

## Common questions

### What is the io.github.bikemeardsley/git-for-me MCP server?

io.github.bikemeardsley/git-for-me is an MCP server listed in the public MCP registry as io.github.bikemeardsley/git-for-me. Which parts of what you want to build open source already covers. Every repo checked live. This page covers its npm package (git-for-me).

### Is the io.github.bikemeardsley/git-for-me MCP server safe to use?

io.github.bikemeardsley/git-for-me scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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.bikemeardsley/git-for-me MCP server expose?

io.github.bikemeardsley/git-for-me exposes 3 tools: git_for_me, git_for_me_search, git_for_me_verify. Their descriptions and schemas cost roughly 521 tokens of context every time the server is loaded.

### Is the io.github.bikemeardsley/git-for-me MCP server still maintained?

io.github.bikemeardsley/git-for-me is still listed as active in the MCP registry. We last reached this channel on 17 October 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.bikemeardsley/git-for-me MCP server under?

io.github.bikemeardsley/git-for-me declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/git-for-me
- Socket report: https://socket.dev/npm/package/git-for-me
- Repository: https://github.com/bikemeardsley/git-for-me
- Changelog RSS feed: https://verifymcp.io/servers/bikemeardsley-git-for-me/git-for-me.xml
- Changelog JSON feed: https://verifymcp.io/servers/bikemeardsley-git-for-me/git-for-me.json
- HTML version of this page: https://verifymcp.io/servers/bikemeardsley-git-for-me/git-for-me