Add SandBase Harness to agentic DevOps catalog

[liyangbing]

Summary

• add SandBase Harness to the community MCP server catalog
• classify it as a prototype, write-capable MCP runtime with approval and evidence labels
• document the real DevOps-relevant use case and backend-dependent isolation boundary
• update the community README table and Recently added section

Evidence:

• Repository: https://github.com/sandbaseai/sandbase-harness
• Installation guide: https://github.com/sandbaseai/sandbase-harness/blob/main/docs/installation.md
• Latest release: https://github.com/sandbaseai/sandbase-harness/releases/tag/v0.3.8
• License: https://github.com/sandbaseai/sandbase-harness/blob/main/LICENSE

Validation:

• python3 scripts/validate_repos_yaml.py passed (81 entries, 15 categories)
• python3 scripts/sync_readme_counts.py passed
• git diff --check passed
• python3 -m pytest -q could not collect on the host's Python 3.10 because the existing test suite imports datetime.UTC, which requires Python 3.11+.

The description intentionally treats isolation as deployment-dependent and calls for least-privilege credentials and approval gates.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[liyangbing]

Maintainer verification for the SandBase Harness entry:

• Source of truth: https://github.com/sandbaseai/sandbase-harness
• Current release: v0.3.8 — https://github.com/sandbaseai/sandbase-harness/releases/tag/v0.3.8
• Official MCP installation/configuration: https://github.com/sandbaseai/sandbase-harness/blob/main/docs/mcp-server.md
• The proposed DevOps classification is appropriate for a local-first/self-hosted runtime exposing MCP tools, persistent sessions, approvals, credentials, artifacts, audit, and replay.
• Isolation must remain described as deployment/backend dependent; Docker, Kubernetes, and worker backends have different guarantees.

The host repository's YAML validation and README synchronization results are useful evidence. The Python 3.10 test-collection limitation is pre-existing/environmental and does not represent a SandBase Harness test failure.