com.rowattest/rowattest·Databases

RowAttest

Runs an eight-stage isolation test against your staging Supabase and issues a signed attestation.

Stars
—
Version
1.0.0
License
—
Review
Passed
Registry update
Oct 10, 2026

Connect

remote
Terminal
$claude mcp add --transport http rowattest https://app.rowattest.com/mcp \  --header "Authorization: <authorization>"

Headers

  • Authorization

    RowAttest API key. Create one on the API keys page in the RowAttest app.

Security review

Review passed

Reviewed 2h ago.

tools
6 tools scanned
metadata
scanned

No findings.

Tools

6
  • list_projects

    Lists the Supabase projects connected to this account with id, name, connection state and whether each is ready to run. Call this first to get a project_id.

  • run_review

    Starts an authorization test run on a connected project and returns the run_id and status. If the project already has a run waiting to start, returns that run instead of starting another. Runs that do not fail count against the monthly allowance.

  • get_run_status

    Returns a run's status (queued, running, complete or failed), its current stage, timestamps and, when a signed report exists, its verify_url.

  • wait_for_run

    Waits up to timeout_seconds (1 to 60) for a run to finish, then returns the same information as get_run_status. Call it again while the status is still queued or running.

  • get_findings

    Returns the cells that did not pass in a complete run that has a signed report — verdict, surface, operation, boundary, identity, layer outcomes and notes — plus tenancy flags, blocking findings and, when the report includes catalog hygiene checks, the hygiene block (the checks run, each finding's check, severity, object, detail and hint, and any check not run). For a complete run with no signed report, while one can still be bought on the run page, it returns the run's unverified result instead: the verdict, surface, operation and principal of each cell that did not pass, the run page's finding lines, the counts, the coverage lines, the access model summary and the same hygiene block. The list of cells is empty when every tested cell passed. Cell results contain no fix suggestions: the engine records only what it observed. Hygiene findings are catalog observations, never verdicts; each carries the engine's one-line hint for the project owner's review.

  • get_report

    Returns the full signed report of a complete run as the exact stored JSON, with its verify_url and report_sha256 (sha256 of the canonical signed bytes, the fingerprint shown on the verify page). Use get_findings for the compact view.

More in Databases

Listing from the official MCP Registry.