Skip to content

RowAttest MCP server

com.rowattest/rowattestrowattest.comstreamable-httpv1.0.1Scanned

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

7 tools: 2 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 2 write, 5 read.
  • Reads private data · 1
  • Reads text others write · 3
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the RowAttest MCP server can do

The RowAttest MCP server is published by rowattest.com, a domain the MCP Registry verified. It has 7 tools. It can create or change data (2 tools: run_review and verify_attestation), but cannot delete data. 5 tools only read.

1 tool reads private data (get_findings); 3 tools bring in text other people can write (get_run_status, get_report and verify_attestation).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Changes things 2Claude Code: ask
  • run_reviewStarts an authorization test run on a connected project and returns the run_id and status.No findings

    Why it is in this group

    • The name "run_review" says "run": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • verify_attestationChecks a RowAttest attestation published by a site or MCP server.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Checks a RowAttest attestation published by a site or MCP server. Give it the origin (for example https://example.com); it fetches /.well-known/rowattest.json there, follows the first entry to the signed summary, verifies the signature offline against RowAttest's public key list, and returns whether the proof is valid, when it was issued, its totals, whether findings were present, and whether it is bound to the project ref you pass. It reads public data only, needs no project of yours, and starts no run. A valid proof means the listed checks ran at that time and were signed by RowAttest; it does not mean the application is secure.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 5Show 5 read-only tools
  • get_findingsReturns 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, blo…Reads private dataNo findings

    Why it is in this group

    • The name "get_findings" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "return" and "note": it reads notes.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_reportReturns 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…Reads text others writeNo findings

    Why it is in this group

    • The name "get_report" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • get_run_statusReturns a run's status (queued, running, complete or failed), its current stage, timestamps and, when a signed report exists, its verify_url.Reads text others writeNo findings

    Why it is in this group

    • The name "get_run_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Returns a run's status (queued, running, complete or failed), its current stage, timestamps and, when a signed report exists, its verify_url.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • list_projectsLists the Supabase projects connected to this account with id, name, connection state and whether each is ready to run.No findings

    Why it is in this group

    • The name "list_projects" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false
  • wait_for_runWaits up to timeout_seconds (1 to 60) for a run to finish, then returns the same information as get_run_status.No findings

    Why it is in this group

    • The name "wait_for_run" says "wait": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write3
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:46 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://app.rowattest.com/mcp: tools/list returned 7 tools to an anonymous client, including run_review (write), verify_attestation (write)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 1 to 2

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http rowattest https://app.rowattest.com/mcp
claude mcp add --transport http rowattest https://app.rowattest.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rowattest__list_projects",
      "mcp__rowattest__get_run_status",
      "mcp__rowattest__wait_for_run",
      "mcp__rowattest__get_findings",
      "mcp__rowattest__get_report"
    ],
    "ask": [
      "mcp__rowattest__run_review",
      "mcp__rowattest__verify_attestation"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rowattest. Review it before you use it.

Capability tags behind 4 rules
  • mcp__rowattest__get_run_status untrusted-input
  • mcp__rowattest__get_findings private-data
  • mcp__rowattest__get_report untrusted-input
  • mcp__rowattest__verify_attestation untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.rowattest/rowattest/verify?hash=cfe5c0a431ae3ef8ed6027a925d3a654580d4a46d5ad293acaa6fa47de453827" | jq -e '.changed == false'

Pinned hash cfe5c0a431ae, from Nov 9, 2026, 16:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.rowattest/rowattest/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.rowattest/rowattest
[![Anlyon Radar](https://radar.anlyon.com/badge/com.rowattest/rowattest.svg)](https://radar.anlyon.com/servers/com.rowattest/rowattest)

Source: MCP Registry. Synced Oct 27, 2026, 14:17 UTC.

RowAttest MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RowAttest MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the RowAttest MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the RowAttest MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the RowAttest MCP server have?

7 tools: 2 write, 5 read. run_review, verify_attestation, list_projects, get_run_status, wait_for_run, get_findings and get_report.

Does the RowAttest MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the RowAttest MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the RowAttest MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.