
GenPark Distributed Deadlock Wait-For-Graph Detector
io.github.alphaparkincPublished by GitHub account alphaparkincv1.0.1Updated Oct 26, 2026
Real-time Tarjan SCC cycle detection on lock Wait-For-Graphs with victim transaction arbitrator
Overview
A local Python MCP server that detects deadlock cycles in lock wait-for graphs using Tarjan SCC analysis and picks a victim transaction.
- What you can do
- Detect cycles in lock wait-for graphs using real-time Tarjan strongly connected component analysis
- Identify deadlocked transactions and choose a minimal-cost victim transaction to resolve the deadlock
- Run as a local Python process configured in Claude Desktop or Cursor
- Operate with no third-party dependencies, using only the Python 3 standard library
- When to use it
- Useful when an assistant needs to reason about distributed database or lock-manager deadlocks, analyze wait-for graphs, or decide which transaction to abort to break a cycle.
- Requirements
- Runs as a local process on the user's machine, launched with Python (the README shows a python command running mcp_server.py). Python 3 standard library only; no accounts, API keys, or environment variables are declared. Desktop client only.
Installation
In SourceWeft
- Open GenPark Distributed Deadlock Wait-For-Graph Detector in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
genpark-distributed-deadlock-wait-for-graph-detector-skill
[Verified by Smithery] [LinkedIn] [Website]
Real-time Tarjan SCC cycle detection on lock Wait-For-Graphs with minimal-cost victim transaction arbitrator
Quick Installation & MCP Integration
Add to your Claude Desktop or Cursor configuration:
Zero Dependencies
Implemented entirely in Python 3 standard library.
Source: README.md at commit 7dfdfbc
Tools
0Version history
1- v1.0.1LatestOct 19, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.