Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

rowstile

NPM · ROWSTILE

Check, test, prove and review a rowstile policy: access rules for Postgres row-level security

Available components

80 Trust /100

Last scanned (21 hours ago)

Scores higher than 65% of npm servers

Category Databases

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 0 of 7 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to rowstile/rowstile). View diagnostics → Pass
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 676 tokens (~96/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 83% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 14 Oct 26 +41
    • Injection markers: unverified → pass ▲ security
    • Known CVEs: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Dependency health: unverified → 1.00 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 83 functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 100 functional
  • 13 Oct 26 −11
    • Known CVEs: pass → unverified ▼ security
    • Dependency health: 1.00 → unverified ▼ functional
    • Package version: 0.1.0-alpha.6 → 0.1.0-alpha.7 functional
  • 12 Oct 26 +1
    • Security disclosure: unverified → pass ▲ functional
  • 11 Oct 26 49

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 16 Oct 2026 · Analysed npm/rowstile@0.1.0-alpha.7

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo rowstile/rowstile
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/rowstile/rowstile/.github/workflows/release.yml@refs/tags/v0.1.0-alpha.7
Rekor log index 3243798380
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:df741d8f275c20ed068120d3804e480da0665e2f435a539c924453d36e545619de1eefe1efa691cf7dfef31693ea3429ee431724bf2b70f5725453ff0

Background: How many MCP packages publish verified provenance →

Dependencies 7 packages
Packages resolved 7
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~511 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
check ~48

Compile the policy without a database and report its first mistake, with the file, line and code.

NameTypeReqDescription
policystring–the policy file (default: rowstile.toml's `policy`)
NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

lint ~46

The ways around row-level security the database leaves open (authz.lint()): the app role owning a table, bypassing RLS, tables without rules, grants on masked columns, ...

Input schema present but exposes no named parameters.

NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

prove ~69

Check every invariant of the policy in many small worlds (no database): the smallest counterexample, or that none was found.

NameTypeReqDescription
policystring–the policy file (default: rowstile.toml's `policy`)
worldsinteger–how many worlds to try (default 400)
NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

push ~84

Bring the development database to the policy, with the migration production would get. Only a database marked as a development database (a person marks one with rowstile push --development; the first push to one with no policy marks it): production takes migrations (rowstile migrate).

NameTypeReqDescription
policystring–the policy file (default: rowstile.toml's `policy`)
NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

review ~75

What the policy change since a git ref does: meaning, access, risk, tests and deploy (the pull request comment, as markdown). Needs git.

NameTypeReqDescription
basestring–the ref to compare with (default: main)
policystring–the policy file (default: rowstile.toml's `policy`)
NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

test ~78

Run the policy's tests, the test files rowstile.toml names (or these), and the invariants, on the database; nothing stays. With coverage, the branches of each permission no test makes true.

NameTypeReqDescription
coverageboolean––
filesarray–test files (default: rowstile.toml's `tests`)
NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

why ~111

Whether someone holds a permission on an object, and why; if not, why not, and the smallest changes to the data that would grant it (each tried on the database and undone).

NameTypeReqDescription
asstringyeswho asks: user:42, bot:7 (a principal type and id), or anyone
idstringyes–
permstringyesa permission of the type, e.g. view
typestringyesthe policy's type, e.g. folder
NameTypeReqDescription
errorobject–check: the mistake, when there is one
exit_codeintegeryes–
okbooleanyestrue when the command found nothing wrong
outputstringyeswhat the command printed

No examples provided.

Install

How do I install the rowstile MCP server?

rowstile runs locally as an npm package, launched with npx -y rowstile. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · rowstile

# add to Claude Code
claude mcp add rowstile-rowstile -- npx -y rowstile
Common questions

What is the rowstile MCP server?

rowstile is an MCP server listed in the public MCP registry as io.github.rowstile/rowstile. Check, test, prove and review a rowstile policy: access rules for Postgres row-level security. This page covers its npm package (rowstile).

Is the rowstile MCP server safe to use?

rowstile scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 16 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the rowstile MCP server expose?

rowstile exposes 7 tools: check, prove, review, test, why, and 2 more. Their descriptions and schemas cost roughly 511 tokens of context every time the server is loaded.

Is the rowstile MCP server still maintained?

rowstile is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the rowstile MCP server under?

rowstile declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.