MCP servers › io.github.selfagency › git-mcp
MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23
io.github.selfagency/git-mcp
A Git MCP server that doesn't suck — the publisher's description
Summary
io.github.selfagency/git-mcp is a local MCP server listed in the official MCP registry at version 0.4.2. On 2026-10-23 ProtocolProbe started its published package in an isolated sandbox in read-only mode and read its inventory: 27 tools, 0 resources and 0 prompts.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- not met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- met: npm package carries build provenance (attestation)
- not met: No known critical or high advisory in the package or its dependencies
- #10,042 of 15,112 packages by monthly downloads, tied with 44 others
- Not ranked by stars: 0 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Key facts
- Runs
- local package
- Transport
- standard input/output
- Package
- npm · listed version current
- License
- MIT
- Dependencies
- 2 critical, 1 high advisories
- Repository
- public
- Tools
- 27
- Described as changing data
- 18 of 27 toolsAI-classified
- Mainly works on
- files and code on the machine it runs onAI-classified
- Topic
- developer-toolsAI-classified
- Last tested
- 2026-10-23
Worth knowing before you connect it
- 18 tools are described as changing something (git_commits, git_branches, git_remotes, …): our AI model's reading of the descriptions, not something we tested. We did not call them.
- 2 critical and 1 high advisories in its dependencies (as resolved on 2026-10-23).
- Its package is signed and carries a build record naming its source.
Each line comes from a section below, with its source and date.
How fresh this is
- Live-tested
- yes, a real session (not a text-only review)
- Last tested
- 2026-10-23
- Mode
- read-only (no tool calls)
- Latest version
- 0.4.2, published 2026-10-14 (registry, as of the 2026-10-23 snapshot)
- First listed version
- 2026-10-14 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 2 versions listed, all on 2026-10-14; 2 in the 90 days before the 2026-10-23 snapshot.(versions still listed in the registry only)
Most recent 2 versions
0.4.2· 2026-10-140.4.1· 2026-10-14
- Registry data
- snapshot 2026-10-23
- Package and repository
- checked 2026-10-23
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Changes since the last refresh
New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 0.4.2 (published 2026-10-14).
Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.
What it is
What does this server offer?
Observed inventoryWhat it mainly works on, as our AI model read its tool descriptions: files and code on the machine it runs on.
18 of 27 tools are described as changing something (creating, editing, deleting, sending or running).
“Status and diff tool.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
8 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringmodestringfrom_refstringto_refstringfilteredbooleanbase_branchstringresponse_formatstring“Output format for the response.”
“History tool.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
18 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringlimitintegeroffsetintegerfirst_parentbooleanno_mergesbooleanall_branchesbooleansimplify_mergesbooleanorderstringrevision_rangestringpathspecsarrayauthorstringgrepstringsincestringuntilstringfile_pathstringrefstringresponse_formatstring“Output format for the response.”
- git_commitscreates or changes datadescribed as changing data
“Commit-area tool.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
20 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringallbooleanpathsarraymessagestringamendbooleanno_editbooleansignboolean“Sign the commit.”signing_keystringno_verifybooleanmodestringtargetstringconfirmbooleanstagedbooleanworktreebooleansourcestringrefstringno_commitbooleanmainlineintegerresponse_formatstring“Output format for the response.”
“Branch tool.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
14 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringallbooleannamestringold_namestringnew_namestringfrom_refstringrefstringcreatebooleanforcebooleanbranchstringupstreamstringcountintegerresponse_formatstring“Output format for the response.”
“Remote tool.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
22 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringremote_actionstringnamestringurlstringremotestringbranchstringrefspecsarrayprunebooleanprune_tagsbooleannegotiation_tipsarrayrebasebooleanrebase_modestringff_onlybooleanset_upstreambooleanforce_with_leasebooleanforcebooleanno_verifybooleantagsbooleanpush_optionsarrayatomicbooleanresponse_formatstring“Output format for the response.”
- git_workspacedescribed as changing data
“Workspace tool for stash/rebase/cherry-pick/merge/bisect/tag/worktree/submodule actions plus stash_all shortcut.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
57 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringstash_actionstringmessagestringindexintegerinclude_untrackedbooleanrebase_actionstringrebase_interactivebooleanrebase_autosquashbooleanrebase_mergesbooleanrebase_ontostringrebase_upstreamstringrebase_branchstringcherry_pick_actionstringcherry_pick_refsarraycherry_pick_mainlineintegercherry_pick_record_originbooleancherry_pick_no_commitbooleancherry_pick_strategystringcherry_pick_strategy_optionsarraymerge_actionstringmerge_refsarraymerge_no_ffbooleanmerge_ff_onlybooleanmerge_squashboolean
and 32 more not listed here.
- git_contextreads or searchesdescribed as changing data
“Context/config tool.”
Publisher declares: read-only no · destructive yes · idempotent yes · open-world no
7 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringquerystringlimitintegerkeystringvaluestringresponse_formatstring“Output format for the response.”
- git_but_checkreads or searches
“Detects whether the GitButler `but` CLI is available and returns guidance on whether to prefer `but mcp` / `but` commands over git-mcp tools.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
response_formatstring“Output format for the response.”
- git_jj_checkreads or searches
“Detect whether the Jujutsu `jj` CLI is available and whether the repository is jj-managed (has a .jj/ directory).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
repo_pathstring“Absolute path to the local Git repository.”response_formatstring“Output format for the response.”
- git_tangled_checkreads or searches
“Detect whether the repository origin remote points at a Tangled host (tangled.org or a self-hosted knot).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
repo_pathstring“Absolute path to the local Git repository.”response_formatstring“Output format for the response.”
- git_entire_checkreads or searches
“Detect whether the Entire CLI is available and whether the repository is Entire-managed (has a .entire/ directory).”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
2 inputs
repo_pathstring“Absolute path to the local Git repository.”response_formatstring“Output format for the response.”
- git_analyticsreads or searches
“Read-only repository analytics computed from local git history.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
3 inputs, 1 required
repo_pathstring“Absolute path to the local Git repository.”actionstringrequired“Analytics operation.”response_formatstring“Output format for the response.”
Show 15 more tools
- git_prcreates or changes datadescribed as changing data
“Create, list, or merge pull requests / merge requests on the detected forge provider (GitHub, GitLab, Forgejo, Gitea, Bitbucket).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
10 inputs, 1 required
repo_pathstring“Absolute path to the local Git repository.”actionstringrequired“Pull request operation.”titlestring“PR/MR title (create).”bodystring“PR/MR body/description (create).”basestring“Target branch (create, default main).”headstring“Source branch (create, default HEAD).”statestring“Filter for list (default open).”numberinteger“PR/MR number (merge).”methodstring“Merge method (merge).”response_formatstring“Output format for the response.”
- git_lfscreates or changes datadescribed as changing data
“Manage Git Large File Storage (LFS).”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
8 inputs, 1 required
repo_pathstring“Absolute path to the local Git repository.”actionstringrequiredpatternsarray“File glob patterns for track/untrack (e.g.”remotestring“Remote name for pull/push operations.”includestring“Comma-separated include patterns for migrate or pull operations.”excludestring“Comma-separated exclude patterns for migrate or pull operations.”everythingboolean“Pass --all/--everything to include all refs in push/migrate operations.”response_formatstring“Output format for the response.”
- git_rewritecreates or changes datadescribed as changing data
“Rewrite commit history.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
10 inputs, 1 required
repo_pathstring“Absolute path to the local Git repository.”actionstringrequired“History rewrite operation.”refstring“Commit ref to reword (defaults to HEAD).”messagestring“New commit message (reword/squash).”countinteger“Number of commits to squash.”rangestring“Commit range to rewrite (e.g.”messagesobject“Map of commit SHA to replacement message (rewrite-messages).”namestring“Backup branch name (backup/restore).”confirmboolean“Confirm destructive history rewrite.”response_formatstring“Output format for the response.”
- git_flowdescribed as changing data
“Drives the git-flow-next CLI.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
46 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstring“Legacy-compatible action alias.”operationstring“Canonical git_flow operation.”config_actionstring“config_action is required for operation=config.”topic_actionstring“Topic branch lifecycle operation.”control_actionstring“Continue or abort an in-progress flow finish operation.”recoverstring“Which in-progress operation control_action targets (default: finish).”topicstring“Topic branch type for generalized actions such as topic-start, topic-list, or topic-publish.”namestring“Branch short name, branch type name, or release/hotfix version depending on the action.”new_namestring“New short name or branch type name for rename operations.”branch_kindstring“Whether a flow config operation targets a base branch or topic branch type.”parentstring“Parent/base branch for flow config mutations.”prefixstring“Branch prefix for topic type definitions, such as "feature/".”start_pointstring“Configured start point for a topic type.”base_refstring“Explicit starting ref for topic-start.”presetstring“git-flow-next preset to initialize.”scopestring“Git config scope used for init writes.”config_filestring“Path to a git config file when scope is "file".”sharedboolean“Write a committable .gitflow file (init, or config edit).”forceboolean“Force re-initialization even if git-flow is already configured.”no_create_branchesboolean“Skip base branch creation during init and only write configuration.”main_branchstring“Override the main branch name (default: gitflow.branch.master config or "main").”develop_branchstring“Override the develop branch name (default: gitflow.branch.develop config or "develop").”staging_branchstring“NOT SUPPORTED by git-flow-next 2.1.0 init; use preset=gitlab instead.”production_branchstring“NOT SUPPORTED by git-flow-next 2.1.0 init; use preset=gitlab instead.”
and 21 more not listed here.
- git_workflowdescribed as changing data
“Run named multi-step Git workflows with resumable lifecycle controls.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world yes
21 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstring“Lifecycle action for git_workflow execution and state management.”workflowstring“Named workflow family for multi-step Git orchestration.”base_branchstring“Base branch for snapshot merge-base checks (default: main).”log_countinteger“Commit count for snapshot log output.”modestring“Replay mode for replay workflow.”target_branchstring“Target branch for replay/branch_surgery/publish workflows.”source_commitsarray“Commit list for replay and branch_surgery flows.”patch_filesarray“Patch/mailbox file list for replay mode=am.”three_wayboolean“Use --3way when applying patch series via git am.”backup_branchstring“Backup branch name for branch_surgery workflow.”reset_tostring“Optional hard-reset target in replay/branch_surgery workflows.”confirm_hard_resetboolean“Required true when reset_to is provided because hard reset is destructive.”auto_publishboolean“Automatically publish after replay/branch_surgery sequence.”publishboolean“Deprecated alias for auto_publish; retained for backward compatibility.”remotestring“Remote name for publish-related steps (default: origin).”force_with_leaseboolean“Use --force-with-lease for publish push steps.”set_upstreamboolean“Use --set-upstream for publish push steps.”fetch_firstboolean“Fetch before publish workflow steps.”rebase_ontostring“Optional rebase target before publish push step.”response_formatstring“Output format for the response.”
“Stash, list, apply, pop, or drop stashes.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
6 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringmessagestringindexintegerinclude_untrackedbooleanresponse_formatstring“Output format for the response.”
“Rebase: start, continue, abort, or skip.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
9 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringinteractivebooleanautosquashbooleanmergesbooleanontostringupstreamstringbranchstringresponse_formatstring“Output format for the response.”
“Cherry-pick: start, continue, or abort.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
9 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringrefsarraymainlineintegerrecord_originbooleanno_commitbooleanstrategystringstrategy_optionsarrayresponse_formatstring“Output format for the response.”
“Merge: start, continue, or abort.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
12 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringrefsarrayno_ffbooleanff_onlybooleansquashbooleanno_commitbooleanlogbooleanstrategystringstrategy_optionsarrayconflict_stylestringresponse_formatstring“Output format for the response.”
- git_bisectdescribed as changing data
“Bisect: start, good, bad, skip, run, or reset.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
8 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringrefstringgood_refstringbad_refstringcommandstringcommand_argsarrayresponse_formatstring“Output format for the response.”
“Tag: list, create, or delete.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
8 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringnamestringtargetstringmessagestringsignboolean“Sign the tag.”signing_keystringresponse_formatstring“Output format for the response.”
“Worktrees, two ways.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
10 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringpathstringbranchstringforcebooleandetachedbooleanlock_reasonstringexpirestringpathsarrayresponse_formatstring“Output format for the response.”
- git_submodulecreates or changes datadescribed as changing data
“Submodule: add, list, update, sync, or set_branch.”
Publisher declares: read-only no · destructive yes · idempotent no · open-world no
11 inputs
repo_pathstring“Absolute path to the local Git repository.”actionstringurlstringpathstringbranchstringrecursivebooleanremotebooleandepthintegerjobsintegerpathsarrayresponse_formatstring“Output format for the response.”
- git_docsreads or searches
“Search and browse official Git documentation from git-scm.com.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes
3 inputs, 2 required
actionstringrequiredquerystringrequired“For action="search": search terms (e.g.”response_formatstring“Output format for the response.”
- git_pingreads or searches
“Returns a simple response to verify the server is running.”
Publisher declares: read-only yes · destructive no · idempotent yes · open-world no
1 input
messagestring
Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.
How well are its tools described?
Features #4 and #5
How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.
Descriptions
AI reading of each description
- Says what the tool does
- 100% of 27 tools
- Says what it returns
- 100% of 27 tools
- States limits, defaults or errors
- 4% of 27 tools
- Says when to use it
- 100% of 5 tools
- Items covered per tool
- 3.0 of 4 on average
Counted from the listing
- Parameters with a description
- 42% of 328
- Tools with a description
- 100% of 27
- Typical description length
- 158 characters
The tool set
Counted from the listing
- Tools
- 27
- Size of the list
- about 10,794 tokens for an agent to load (characters ÷ 4)
- Naming
- 27 of 27 names use snake_case
AI reading: easy to mix up
No pair found.
The AI items cover 27 of 27 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.
How do I add it to my client?
Config from the registry entry
From the npm package @selfagency/git-mcp
Our sandbox started this package on 2026-10-23 (a read-only session: no tool was called).
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"git-mcp": {
"command": "npx",
"args": [
"-y",
"@selfagency/git-mcp@0.4.2"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"git-mcp": {
"command": "npx",
"args": [
"-y",
"@selfagency/git-mcp@0.4.2"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"git-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@selfagency/git-mcp@0.4.2"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"git-mcp","type":"stdio","command":"npx","args":["-y","@selfagency/git-mcp@0.4.2"]}'Claude Code
claude mcp add --transport stdio git-mcp -- npx -y @selfagency/git-mcp@0.4.2
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y @selfagency/git-mcp@0.4.2
- Optional settings the entry also lists (left out above): GIT_REPO_PATH, GIT_ALLOW_NO_VERIFY, GIT_ALLOW_FORCE_PUSH, GIT_ALLOW_FLOW_HOOKS, GIT_SIGNING_KEY, GIT_SIGNING_FORMAT, GIT_AUTO_SIGN_COMMITS, GIT_AUTO_SIGN_TAGS.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.4.2
- Latest stable
- 0.4.2
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-10-23. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-10-23 (npm audit). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-j06nR82tIE4eIcGd1…
- Signature
- signed and attested
- License
- MIT
Source: the package registry · 2026-10-23.
Usage
- Downloads
- 192 in the last month
Source: api.npmjs.org · 2026-10-23.
Does the registry listing match what we found?
Feature #6The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Published package can be started | Started and answered | matches | our test · 2026-10-23 |
| Version 0.4.2 on npm | Exists and can be installed | matches | npm · 2026-10-23 |
| Repository github.com/selfagency/git-mcp | Opens publicly | matches | api.github.com · 2026-10-23 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.selfagency · 2 servers
- GitHub owner
- a personal account (selfagency)
- Build record
- signed and attested
- Repository
- github.com/selfagency/git-mcp
- Stars
- 0
- Repository age
- 181–365 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)
Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating7 of 9 record checks met
- #10,042 of 15,112 packages by monthly downloads, tied with 44 others
- Not ranked by stars: 0 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
- MetPackage names its licence with a standard (SPDX) identifierMIT
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Metnpm package carries build provenance (attestation)Signed, with a build attestation naming the source and workflow.
- Not metNo known critical or high advisory in the package or its dependencies3 critical or high advisories in its dependencies.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards
Common questions about io.github.selfagency/git-mcp
Answered from the data aboveIs io.github.selfagency/git-mcp safe to install?
We do not rate servers as safe or unsafe. 7 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its npm package carries a build-provenance attestation that names its source repository and build workflow. Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has advisories (2 critical and 1 high; npm audit). 18 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Has io.github.selfagency/git-mcp been security tested?
Partly. 2 of the 12 checks that apply to it were exercised. We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security verdict is published before verification.
What can io.github.selfagency/git-mcp do?
It lists 27 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.
Can io.github.selfagency/git-mcp change or delete data?
18 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.
Does io.github.selfagency/git-mcp publish a security policy?
We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.
Is the listed version current?
Yes. The registry lists 0.4.2, the latest stable release on npm.
Where is the source code of io.github.selfagency/git-mcp?
In github.com/selfagency/git-mcp, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Similar servers
Same topic · AI-read
- io.github.DeusData/codebase-memory-mcpCodebase Memoryalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.mobile-next/mobile-mcpalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.cameroncooke/XcodeBuildMCPalso has tools that creates or changes data, reads or searchescompare with this one
- io.github.FlorianBruniaux/claude-code-guideClaude Code Ultimate Guidealso has tools that creates or changes data, reads or searchescompare with this one
- io.github.callstack/agent-deviceagent-devicealso has tools that creates or changes data, reads or searchescompare with this one
- io.github.A9T9/uivision-mcpUi.Vision MCPalso has tools that creates or changes data, reads or searchescompare with this one
Active servers whose topic is also “developer-tools” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Not probed (read-only run)
We started the package in an isolated sandbox and read what it declares, but this test round was read-only, so its tools were not called. No security score is given; a check we did not run is never counted as passed.
- Inventory: exercised
- Hidden instructions: exercised
- Real execution: not run · our policy
- Secret leak: not run · nothing to check it against
- Internal addresses: not run · our policy
- Unconfirmed changes: not run · our policy
- Bad input: not run · our policy
- Model requests: not run · nothing to check it against
- Sensitive questions: not run · nothing to check it against
- Folder boundary: not run · our policy
- Log leaks: not run · nothing to check it against
- Hidden content: not run · nothing to check it against
- Fake assistant turns: not applicable
- Token passthrough: not applicable
- Token audience: not applicable
- Sign-in redirect: not applicable
- Consent handling: not applicable
- Sign-in metadata: not applicable
2 exercised10 not run (reason given)6 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 2 of the 12 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.
- 1Inventory
tool-listReads the declared tools, resources and prompts.exercised - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
- 3Real execution
real-executionCalls a tool and checks what really happens.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the package's tools. This test round was read-only, so no tool was called; tools can act on outside services with the publisher's or a user's account.not run · our policy - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against - 12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
- 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable - 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.The server runs locally over standard input/output, so there is no sign-in flow to check.not applicable
Source: our own test in an isolated sandbox, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted the published package in an isolated sandbox (read-only mode)
- 4,354 msConnected after 0 redirects.
- Read the inventory: 27 tools, 0 resources, 0 prompts.
- 13,544 msFinished: 2 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.selfagency/git-mcp: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.github.selfagency/git-mcp
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.selfagency/git-mcp)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.
Write to hello@protocolprobe.com · corrections log · methodology