A local MCP server providing tools for exploring code change history and developer insights.
MCPpedia last refreshed this data
GitWho2Blame is an MCP server that a local MCP server providing tools for exploring code change history and developer insights. Its tool list has not been published yet over stdio and http, requires no API key, and scores 28/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"gitwho2blame": {
"url": "<see-readme-for-url>"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Ever wondered why a piece of code was changed, or who made a subtle modification deep in a file? GitWho2Blame brings the power of large language models (LLMs) directly into your development workflow. Ask natural language questions about specific lines or changes, and get contextual, AI-powered answers — all without ever leaving your IDE.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in developer-tools
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
XcodeBuildMCP provides tools for Xcode project management, simulator management, and app utilities.
Manage Supabase projects — databases, auth, storage, and edge functions
MCP server for using the GitLab API
MCP Security Weekly
Get CVE alerts and security updates for GitWho2Blame and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.