Side-by-side comparison · mcp servers
repowise-dev/repowise vs Wolfe-Jam/faf-mcp
What we have checked about each, line by line. Every value shows where it came from and when we last confirmed it.
MCP Servers
repowise-dev/repowise
Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
MCP Servers
Wolfe-Jam/faf-mcp
Persistent Project Context for Cursor, IDEs and VS Code — IANA-registered .faf format · 25 tools
Checked facts
Line by line
| Measure | repowise-dev/repowise | Wolfe-Jam/faf-mcp |
|---|---|---|
| Lab install check in claude-desktop | Lab error | Not checked yet |
| Security check (static checks) | 100 out of 100 | Not checked yet |
| Days since the last commit | 0 | 0 |
| GitHub forks | 986 | 3 |
| GitHub stars | 8,099 | 7 |
| Days to a first reply on issues | 0.3 | 113.8 |
| Open issues | 198 | 0 |
| Releases in the last 90 days | 22 | 8 |
A line appears only when at least one record has a value we confirmed from a source. Values we have not confirmed are left out, never guessed. Records of different types share fewer lines.
Add a third
Compare with one more record
How this works
Share it, or build your own
This page works for any two or three records in the directory, of any type. The link stays the same whichever order you name them in, so you can share it as it is. Change the records in the address, for example /directories/vs/claude-code-vs-cursor, or start from our editorial comparisons.