Git Log Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Git Log Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
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.
<!-- git-log-mcp - FastMCP server exposing a git_log tool
Written in 2026 by Amir Yalon <[email protected]>
To the extent possible under law, the author(s) have dedicated all copyright and related and neighboring rights to this software to the public domain worldwide. This software is distributed without any warranty.
You should have received a copy of the CC0 Public Domain Dedication along with this software. If not, see <http://creativecommons.org/publicdomain/zero/1.0/>. -->
FastMCP server exposing a single typed tool, git_log. Use this tool to investigate when a code/configuration change happened and infer why it happened from commit history. Choose it when you need commit timelines, authorship context, or intent signals from commit messages and diffs for a specific module or identifier. It is not for repository file content reads or branch manipulation; it is for history analysis and change attribution.
From the project root, run:
uv syncThen configure your MCP client to use the full path to .venv/bin/git-log-mcp.
Example Roo Code MCP configuration:
{
"mcpServers": {
"git-log": {
"command": "/full/path/to/.venv/bin/git-log-mcp"
}
}
}Run tests:
pytest -q~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.