Repocrunch vs Statuscraft

In-depth architectural comparison of the Repocrunch and Statuscraft MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

Which MCP Server Should You Choose?

Choose Repocrunch when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Supports multiple languages and package managers (Python, JS, Rust, Go, Java, Ruby, C/C++), Detects frameworks, CI/CD tools, test frameworks, and architecture traits, Provides repo metadata: stars, forks, license, languages, contributors.

Explore Repocrunch Details

Choose Statuscraft when:

• You need dedicated capabilities in the Monitoring domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: Access normalized live status for 3355 major software services, Fetch structured incident details automatically for non-operational services, Cache status data with 60-second expiry and option to bypass cache.

Feature & Specification Comparison

Specification	Repocrunch kimwwk Monitoring	Statuscraft jabbawocky Monitoring
Summary
Category & Scope	Monitoring	Monitoring
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "kimwwk-repocrunch": {
      "command": "uvx",
      "args": [
        "repocrunch"
      ]
    }
  }
}

{
  "mcpServers": {
    "jabbawocky-statuscraft": {
      "command": "npx",
      "args": [
        "-y",
        "github"
      ]
    }
  }
}

Related MCP Server Comparisons