Add official RowSafe database operations MCP integration

[Dramex]

Summary

Add the official RowSafe CLI/MCP integration under Official Data Platform MCP Servers, with structured action capability, approval/evidence status and operational risk notes. Update the README entry count.

Submitted on behalf of RowSafe. The agent, CLI and MCP server are Apache-2.0. The described service-connected MCP mode uses authenticated access to the separate hosted service. The catalog marks it write-capable and records human approval as unknown. Its isolated previews and opt-in startup flags are documented alongside the broader production/database/cloud write surface.

Official source: https://github.com/rowsafe/rowsafe . MCP documentation: https://rowsafe.sh/docs/reference/mcp .

Entry checklist

• The repo URL is public and reachable.
• The entry has a specific category.
• The risk_notes field explains what could go wrong.
• The operator_note field explains why an infrastructure operator should care.
• Labels match the observed behavior, not marketing claims.
• data/repos.yaml and README.md are both updated.

Safety checklist

• No secrets, tokens, kubeconfigs, customer data, or private logs are included.
• Write-capable tools document approval gates, preview behavior, audit/evidence output and rollback expectations.
• Credential guidance uses least privilege and separates read-only credentials from write-capable credentials.
• The hosted service and authenticated external API dependency are disclosed in operator-facing risk notes.

The approval checkbox concerns the entry's documented boundaries: human_approval is explicitly unknown, startup flags are not universal per-action gates, and the risk note advises checking restore coverage and recovery steps before relying on a Mark for rollback.

Validation

• Relevant commands pass locally, or the nonapplicable full-catalog command is explained below.

Passed YAML validation (81 entries), README count generation/check, catalog JSON check, 149 pytest tests, seven mock evaluation scenarios and git diff --check. Scoped unauthenticated GitHub API verification confirms the added RowSafe repository is public, unarchived, Go and active on October 15, 2026.

The full-catalog live reachability audit was not run for this single-entry metadata contribution: the new repository was checked directly, and unchanged catalog links were not re-audited. No MCP tools or production operations were invoked. Only the intended YAML and README changed.

Copy refresh: feature descriptions retain documented authentication, transport, permissions and write-safety boundaries. Source and licensing reference: https://github.com/rowsafe/rowsafe/blob/af1d8103c072def013131820dddc6f1989554270/README.md and https://github.com/rowsafe/rowsafe/blob/af1d8103c072def013131820dddc6f1989554270/LICENSE.

Prepared on behalf of Emad Alharbi, Founder of RowSafe, with AI assistance. This refresh changes descriptive text only; it does not claim a live MCP connection or production execution test.

Refresh validation (October 17, 2026): diff check; exactly one descriptive line per source file; URL/inline-code/flag preservation; line endings preserved; changed lines and body pass wording scan; Fresh isolated-environment validation passed: YAML validator (81 entries), README counts (81 entries/15 sections), catalog JSON synchronization (8 skill sources), all 149 pytest tests, and seven mock scenarios. Full live catalog reachability audit remains omitted for this prose-only refresh; no production connections were tested.. Earlier validation results above refer to the original submission.

[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