Quality Screener vs Gitscrum Core MCP

In-depth architectural comparison of the Quality Screener and Gitscrum Core MCP 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?

Q

Choose Quality Screener when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: auth_status, account_profile, health.

Explore Quality Screener Details

Choose Gitscrum Core MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: task, sprint, workspace.

Explore Gitscrum Core MCP Details

Feature & Specification Comparison

Specification	Q Quality Screener Developer Tools	Gitscrum Core MCP Developer Tools
Summary	Screen and score stocks with the Quality Screener engine: filters, custom scores, and history.	MCP server for GitScrum — manage tasks, sprints, time tracking, and client workflows via AI
Category & Scope	Developer Tools	Developer Tools
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": {
    "quality-screener": {
      "url": "https://modelcontextprotocol.io"
    }
  }
}

{
  "mcpServers": {
    "mcp-93": {
      "command": "npx",
      "args": [
        "-y",
        "@gitscrum-studio/mcp-server"
      ]
    }
  }
}

Related MCP Server Comparisons