MCP.so
ログイン

RowAttest MCP Server

@RowAttest

基本情報

トランスポート

streamable-http

認証方式

APIキー

作者

RowAttest

投稿者

RowAttest

RowAttest MCP Server について

Run an eight-stage isolation test against a staging Supabase environment and receive a signed attestation.

接続情報

https://app.rowattest.com/mcp

セットアップ

claude mcp add rowattest --transport http https://app.rowattest.com/mcp --header "Authorization: Bearer YOUR_API_KEY"

RowAttest MCP Server のツール

6

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.

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.

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

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.

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.

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.

概要

What is RowAttest?

Run an eight-stage isolation test against a staging Supabase environment and receive a signed attestation.

How to use RowAttest?

Add https://app.rowattest.com/mcp as a remote HTTP server in an MCP-compatible client. Obtain your own API key from the service and configure it as documented.

Key features of RowAttest

  • list_projects — Lists the Supabase projects connected to this account with id, name, connection state and whether each is read
  • run_review — Starts an authorization test run on a connected project and returns the run_id and status. If the project alre
  • get_run_status — Returns a run's status (queued, running, complete or failed), its current stage, timestamps and, when a signed
  • 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

Connection details

  • Transport: Remote Streamable HTTP
  • Authentication: API key

Documentation

Website

よくある質問

1

RowAttest のリモート MCP サーバーとは何ですか?

RowAttest のリモート MCP サーバーは、https://app.rowattest.com/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。

2

RowAttest の MCP サーバーにはどう接続しますか?

エンドポイント https://app.rowattest.com/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。

3

RowAttest の MCP サーバーは認証が必要ですか?

はい。RowAttest は API キーが必要です——取得方法は公式ドキュメントを確認し、クライアントの設定に追加してください。

4

RowAttest の MCP サーバーはどのトランスポートを使用しますか?

RowAttest は streamable-http エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。

コメント