Developer Tools
forksplorer.com
Analyzes GitHub forks to identify unmerged commits and provides instructions for applying them.
ENDPOINT 1
https://forksplorer.com/mcp
MCP server metadata
- Name
- forksplorer
- Version
- 0.1.0
Known tools 3
get_fork_featuresScan a GitHub repository's forks and return the forks that carry genuinely unmerged commits (are 'ahead' of upstream), ranked by a transparent activity score (commits ahead + recency + stars).
Inferred read-onlyget_feature_diffReturn the concrete base...head comparison for a single fork: files changed with additions/deletions, per-commit summaries with links, and the raw unified patch inline when it is small enough (a .diff URL otherwise).
Inferred read-onlyget_apply_instructionsReturn copy-paste git commands to bring a fork's unmerged commits into a local checkout: a remote-add + fetch + cherry-pick range, plus a diff-apply fallback, plus honest caveats (fork behind upstream, large ranges, verify-before-ship).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.forksplorer]
url = "https://forksplorer.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"forksplorer": {
"type": "http",
"url": "https://forksplorer.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: forksplorer
Remote MCP URL: https://forksplorer.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"forksplorer": {
"url": "https://forksplorer.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"forksplorer": {
"type": "http",
"url": "https://forksplorer.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "forksplorer",
"transport": "streamable-http",
"url": "https://forksplorer.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.