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.
Available components
Last scanned (3 hours ago)
Scores higher than 38% of npm servers
Category Code Search and Documentation
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 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- 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 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage92
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 75% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
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.
- 15 Oct 26 +29
- 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). security
- Tool coverage: unverified → 100 ▲ functional
- 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 functional
- 14 Oct 26 39
First indexed and scored.
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 17 Oct 2026 · Analysed npm/git-for-me@0.1.1
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 93 packages
| Packages resolved | 93 |
|---|---|
| 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 →
git_for_me Git for me! ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| license | string | – | What the result may be used for, such as "commercial, closed source" or "open source" |
| need | string | yes | 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" |
No output schema declared.
No examples provided.
git_for_me_search Git for me! (searched live) ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| parts | array | yes | – |
No output schema declared.
No examples provided.
git_for_me_verify Git for me! (checked live) ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| components | array | yes | – |
| need | string | yes | What you want to build, in plain words: what goes in, what should come out, and what it is for |
No output schema declared.
No examples provided.
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.
npm · git-for-me
claude mcp add bikemeardsley-git-for-me -- npx -y git-for-me
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.