"Temporal" matching MCP servers:

An experimental MCP server that compresses git commit co-change coupling graphs using the Baligács temporal clique linear spanner algorithm, reducing edge and token counts by ~55-65% while preserving temporal reachability, and exposes tools like index_repository, get_architecture, search_code, and temporal_compress for querying code knowledge graphs.

A local Git intelligence MCP server that provides deep repository analytics including hotspots, temporal coupling, knowledge maps, churn analysis, and risk scoring for AI agents.

Temporal change-impact authority MCP server that tracks per-entity change history across runs and answers downstream propagation queries, enabling impact analysis and reverification worklists.

Provides AI assistants with a Development Time Machine by analyzing git reflogs, commit history, working directory deltas, and shell history for temporal context, including safe git operations and smart commit generation.

One install. 8 IDEs. Your agent works from a structural map of your repo instead of re-reading whole files — so sessions run longer before the context wall — and bi-temporal mistakes are auto-captured from your git revert history, so it stops repeating fixes that already failed. Context packets run ~50–90% smaller per file (structural size, not a bill saving — run engram bench on yours).

MCP server that acts as a temporal verification firewall, checking structured assumptions or diffs against immutable version receipts to return allow/block/abstain with cited evidence.