MCP Audit: CI/CD & Automated Testing for Your MCP Server

[scotia1973-bot]

I ran your MCP server through our automated audit tool — here are the results.

🔍 MCP Auditor Results

Metric	Result
Connectivity	✅ Pass (HTTP 200)
Response Time	471ms
Overall Score	65/100
Schema Validation	Not tested (requires running server)
Certification	❌ Not certified

The full audit requires a running MCP server instance, but your repo's structure and documentation are impressive — 119 tools across Unity editor control with amazing README documentation. Here are my specific suggestions:

📋 Recommendations

1. ✅ Add GitHub Actions CI/CD Pipeline

Your repo has 7,935 tests (per .github/badges/tests.json) but no CI workflow in .github/workflows/. Adding CI would:

• Run tests automatically on every push/PR
• Generate dynamic badge URLs from real test results
• Give contributors confidence their changes don't break anything

Example ci.yml:

name: CI
on: [push, pull_request]
jobs:
  test:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-python@v5
        with:
          python-version: '3.11'
      - run: pip install -e server/
      - run: pytest install/tests/ scripts/tests/ -v

2. 📊 Make Badges Dynamic

The .github/badges/tests.json and .github/badges/tools.json are static files. Consider using GitHub Actions dynamic badges or a service like shields.io endpoint to auto-update from CI results.

3. 🔒 Add a Security Policy Section

Your SECURITY.md exists but the README doesn't link to it. Since this server gives AI assistants direct Unity Editor control (scene edits, play tests, asset manipulation), a prominent security note explaining the trust boundary would help users evaluate risk.

4. 📦 Pin Tool Versions in Examples

Your README examples use npx @krasnikov/unity-mcp. Consider pinning to @latest tag explicitly or adding version recommendations for reproducibility.

5. 🧪 Add Integration Test Workflow

With 119 tools, even a smoke test workflow that starts the TCP bridge and runs a basic connection test would catch regressions early. A test-with-unity.yml workflow could run headless Unity tests.

These changes would make an already impressive project even more maintainable and trustworthy for contributors.

If you'd like a professional MCP server built, security audit, or full automation workflow, check out https://www.gadgethumans.com/services/

[german-krasnikov]

Thanks for the audit! Good suggestions.

I have CI/CD on my roadmap. Right now my priority is MCP server functionality and stability — once that's solid, I'll add GitHub Actions for the 3000+ Python unit tests.

Worth noting that ~80 live integration tests require a running Unity Editor with the MCP plugin (real TCP connection), so those will likely stay local-only. Same for C# NUnit tests — they need a full Unity environment.