Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@quality-assurance run the comprehensive quality suite and report critical issues"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pixi-first quality assessment MCP server: lint, type-check, security, complexity, baselines and trend analysis behind a lean 3-meta-tool interface.
quality-assurance is an MCP server (package src/quality_assurance) that runs quality tooling through pixi and returns compact, structured results. The lean server (quality_assurance.lean_server) exposes only discover_tools, get_tool_spec and execute_tool to keep client context small; the HTTP transport (quality_assurance.http_lean_server) serves it on port 4106 at http://127.0.0.1:4106/mcp.
Tools reachable through execute_tool:
Assessment: quality_execute_lint_assessment, quality_execute_typecheck_assessment, quality_execute_security_scan, quality_execute_complexity_analysis, quality_execute_comprehensive_suite
Analysis: quality_calculate_quality_score, quality_generate_recommendations, quality_detect_quality_patterns, quality_prioritize_issues
Baselines and trends: quality_establish_baseline, quality_compare_against_baseline, quality_analyze_trends
Fixes and reports: quality_apply_automated_fixes, quality_generate_comprehensive_report
Pixi integration: quality_execute_pixi_aware_assessment, quality_optimize_pixi_environment, quality_generate_pixi_tasks, quality_validate_pixi_integration
Health: quality_get_system_health
Related MCP server: glintefy
This project is pixi-only; the package installs itself editable via [tool.pixi.pypi-dependencies]. Do not use pip or uv directly.
pixi install -e ci
# Tests (use -e py312 / -e py313 for a specific interpreter)
pixi run test
# Lint + type-check + tests
pixi run -e ci quality
# Start the HTTP MCP server (port 4106)
pixi run http-serverTask | Environment | Description |
| all | Run the test suite on the selected environment's interpreter |
|
| Run |
|
| Ruff critical rules / all rules / auto-fix |
|
| Ruff format / verify formatting |
|
| mypy over |
| default | Tests with coverage (runs in |
|
| bandit, safety and radon |
|
| Build the distribution |
| default | Start the HTTP MCP server (port 4106) |
| default | Start the lean stdio MCP server |
| default | Start the full stdio MCP server |
Run pixi task list -e <env> for the complete list.
Feature, fix and chore branches open PRs into development only.
Only development may open a PR into main; the Branch Policy check enforces this.
Required checks: CI Success (plus Branch Policy on PRs to main).
No direct pushes to development or main.
MIT License - see LICENSE for details.
This server cannot be deployed
Scan, fix and justify your application code until it is approved to ship.
Free MCP tools: the only MCP linter, health checks, cost estimation, and trust evaluation.
Scan any MCP server for tool-poisoning, security, auth & license. Trust score before install.
AI-native git hosting — repos, PRs, issues, CI gates, and AI code review over MCP (60 tools).
