MCP server for code archaeology: git blame, file history, contributors, and co-change analysis
MCP server for AI-powered code archaeology — explore git blame, file history, contributor patterns, and co-change analysis through the Model Context Protocol. ------|-------------| | PR review briefing with risk flags, reviewer suggestions, and missing file detection | | Code archaeology narrative — explains why code exists by combining blame, commits, contributors, and co-changes |…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
git_activity_droughtNo description publishedThis tool published no description. Forge does not invent one.
git_author_timelineNo description publishedThis tool published no description. Forge does not invent one.
git_bisect_guideNo description publishedThis tool published no description. Forge does not invent one.
git_blame_contextNo description publishedThis tool published no description. Forge does not invent one.
git_branch_activityNo description publishedThis tool published no description. Forge does not invent one.
git_cherry_pick_detectNo description publishedThis tool published no description. Forge does not invent one.
git_code_ageNo description publishedThis tool published no description. Forge does not invent one.
git_code_churnNo description publishedThis tool published no description. Forge does not invent one.
git_code_ownership_changesNo description publishedThis tool published no description. Forge does not invent one.
git_commit_clusterNo description publishedThis tool published no description. Forge does not invent one.
git_commit_frequencyNo description publishedThis tool published no description. Forge does not invent one.
git_commit_graphNo description publishedThis tool published no description. Forge does not invent one.
git_commit_message_qualityNo description publishedThis tool published no description. Forge does not invent one.
git_commit_patternsNo description publishedThis tool published no description. Forge does not invent one.
git_commit_showNo description publishedThis tool published no description. Forge does not invent one.
git_complexity_hotspotsNo description publishedThis tool published no description. Forge does not invent one.
git_conflict_historyNo description publishedThis tool published no description. Forge does not invent one.
git_contributor_growthNo description publishedThis tool published no description. Forge does not invent one.
git_contributor_networkNo description publishedThis tool published no description. Forge does not invent one.
git_contributor_patternsNo description publishedThis tool published no description. Forge does not invent one.
git_coordination_bottleneckNo description publishedThis tool published no description. Forge does not invent one.
git_dependency_mapNo description publishedThis tool published no description. Forge does not invent one.
git_diff_contextNo description publishedThis tool published no description. Forge does not invent one.
git_expertise_decayNo description publishedThis tool published no description. Forge does not invent one.
git_file_historyNo description publishedThis tool published no description. Forge does not invent one.
git_file_risk_profileNo description publishedThis tool published no description. Forge does not invent one.
git_hotspotsNo description publishedThis tool published no description. Forge does not invent one.
git_impact_analysisNo description publishedThis tool published no description. Forge does not invent one.
git_knowledge_loss_riskNo description publishedThis tool published no description. Forge does not invent one.
git_knowledge_mapNo description publishedThis tool published no description. Forge does not invent one.
git_line_historyNo description publishedThis tool published no description. Forge does not invent one.
git_merge_baseNo description publishedThis tool published no description. Forge does not invent one.
git_merge_timelineNo description publishedThis tool published no description. Forge does not invent one.
git_offboarding_simulationNo description publishedThis tool published no description. Forge does not invent one.
git_pickaxeNo description publishedThis tool published no description. Forge does not invent one.
git_refactor_candidatesNo description publishedThis tool published no description. Forge does not invent one.
git_reflog_analysisNo description publishedThis tool published no description. Forge does not invent one.
git_related_changesNo description publishedThis tool published no description. Forge does not invent one.
git_release_comparisonNo description publishedThis tool published no description. Forge does not invent one.
git_release_notesNo description publishedThis tool published no description. Forge does not invent one.
0 of 40 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
MCP server for AI-powered code archaeology — explore git blame, file history, contributor patterns, and co-change analysis through the Model Context Protocol. ------|-------------| | PR review briefing with risk flags, reviewer suggestions, and missing file detection | | Code archaeology narrative — explains why code exists by combining blame, commits, contributors, and co-changes | ------|-------------| | Multi-dimensional risk assessment for a single file | | Repository-wide health summary |…
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.