# rows.page (remote · rows.page)

Push CSV, JSON, JSONL or Parquet from your agent and get a link a human can explore.

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `rows.page`: 67/100 (this document), [markdown](https://verifymcp.io/servers/page-rows-rows/rows.md), [page](https://verifymcp.io/servers/page-rows-rows/rows)

## Channel facts

- Endpoint: `https://rows.page/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 6 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1441 tokens (~240/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 97% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "push" implies "publish" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the rows.page MCP server?

rows.page is a hosted endpoint at https://rows.page/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http page-rows-rows 'https://rows.page/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "page-rows-rows": {
      "url": "https://rows.page/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "page-rows-rows": {
      "type": "http",
      "url": "https://rows.page/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.page-rows-rows]
url = "https://rows.page/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "page-rows-rows": {
      "type": "remote",
      "url": "https://rows.page/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add page-rows-rows --url 'https://rows.page/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  page-rows-rows:
    url: "https://rows.page/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "page-rows-rows": {
      "Transport": "http",
      "Url": "https://rows.page/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add page-rows-rows -t streamable-http -u 'https://rows.page/mcp'
```

### Other

```json
{
  "mcpServers": {
    "page-rows-rows": {
      "type": "http",
      "url": "https://rows.page/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-24 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (6)

### `push` (~589 tokens)

Publish rows as a rows.page dataset (or a new version of one) and get a shareable URL. Pass exactly one of csv, tsv, jsonl, json, rows or url. Up to 16 MB inline; use url for bigger files. Identical content returns unchanged: true without a new version. Re-pushes report rows_delta, columns_added/removed and a diff_url. Anonymous datasets expire after 7 days unless kept. Finding views use the rows.page query language in q: `word` or `"two words"` searches text columns; `field:value`, `field:"a b"`, `-field:value`, `field:*` (not null), `-field:*` (null), `field:foo*` (prefix); `field:>20`, `>=`, `<`, `<=`, `field:10..20`, ISO dates (`at:>2026-09-01`); dot paths for nested JSON (`payload.customer.country:NL`); `tags:urgent` means the list contains it; combine with `OR` and parentheses. A q starting with SELECT, WITH or FROM runs as SQL against the table `data`. sort is comma-separated columns, `-` for descending (`-price,name`); cols picks and orders visible columns (`a,b,c`).

Input parameters:

- `commit` (string): Commit sha of the code that produced it
- `csv` (string): CSV text with a header row
- `dataset` (string): Existing dataset id to push a new version to
- `findings` (array)
- `format` (string): Format of url when it cannot be told
- `id_column` (string): Column that identifies a row across versions, for changed-row diffs
- `json`: A JSON array of objects (or an object holding one), as text or as a value
- `jsonl` (string): One JSON object per line
- `key` (string): Stable name for upserts with an API key, e.g. nightly-orders
- `name` (string): File name, e.g. orders.csv
- `rows` (array): Rows as an array of objects
- `run` (string): Run id of the job that produced it
- `source` (string): Where the data came from (URL or description)
- `summary` (string): A few sentences for the human: what this is and what to look at
- `title` (string): Dataset title shown on the page
- `token` (string): Dataset token (rpt_...) proving ownership of dataset
- `tsv` (string): TSV text with a header row
- `url` (string): http(s) URL of a CSV, TSV, JSON, JSONL or Parquet file to fetch and publish
- `visibility` (string): private needs Pro or Max

### `pin_finding` (~353 tokens)

Pin a finding (a saved, titled view) to a dataset you own. Finding views use the rows.page query language in q: `word` or `"two words"` searches text columns; `field:value`, `field:"a b"`, `-field:value`, `field:*` (not null), `-field:*` (null), `field:foo*` (prefix); `field:>20`, `>=`, `<`, `<=`, `field:10..20`, ISO dates (`at:>2026-09-01`); dot paths for nested JSON (`payload.customer.country:NL`); `tags:urgent` means the list contains it; combine with `OR` and parentheses. A q starting with SELECT, WITH or FROM runs as SQL against the table `data`. sort is comma-separated columns, `-` for descending (`-price,name`); cols picks and orders visible columns (`a,b,c`).

Input parameters:

- `cols` (string): Visible columns, e.g. id,price,country
- `dataset` (string, required): Dataset id
- `note` (string): Why it matters, in a sentence or two
- `q` (string): Filter in the rows.page query language
- `row_count` (integer): Rows matching the view, if you know it
- `sort` (string): Sort, e.g. -price,name
- `sql` (string): Optional SQL against the table `data`
- `title` (string, required): Short headline of the finding
- `token` (string): Dataset token (rpt_...) when not using an API key
- `version` (integer): Pin to this version instead of the latest

### `get_dataset` (~68 tokens)

Read a dataset: meta, recent versions, findings, columns and the first 20 preview rows.

Input parameters:

- `dataset` (string, required): Dataset id
- `token` (string): Dataset token, needed for private datasets without an API key
- `version` (integer): Version number; latest when omitted

### `list_datasets` (~38 tokens)

List the datasets kept on your account, newest first. Needs an API key.

Input parameters:

- `cursor` (string): next_cursor from the previous page

### `delete_dataset` (~44 tokens)

Delete a dataset you own. Its URL stops working immediately.

Input parameters:

- `dataset` (string, required): Dataset id
- `token` (string): Dataset token when not using an API key

### `get_limits` (~26 tokens)

Show your plan, its caps (file size, datasets, version history) and usage.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/page-rows-rows/rows#diagnostics

## Score history

- 2026-11-04: 67
- 2026-11-03: 67
- 2026-11-02: 66
- 2026-11-01: 66
- 2026-10-31: 65
- 2026-10-30: 65
- 2026-10-29: 64
- 2026-10-28: 64
- 2026-10-27: 63
- 2026-10-26: 63
- 2026-10-25: 62
- 2026-10-24: 62
- 2026-10-23: 61
- 2026-10-22: 61
- 2026-10-21: 61
- 2026-10-20: 60
- 2026-10-19: 60
- 2026-10-18: 59
- 2026-10-17: 59
- 2026-10-16: 58
- 2026-10-15: 58
- 2026-10-14: 57
- 2026-10-13: 57
- 2026-10-12: 56
- 2026-10-10: 55

## Common questions

### What is the rows.page MCP server?

rows.page is an MCP server listed in the public MCP registry as page.rows/rows. Push CSV, JSON, JSONL or Parquet from your agent and get a link a human can explore. This page covers its hosted endpoint (https://rows.page/mcp).

### Is the rows.page MCP server safe to use?

rows.page scores 67 out of 100 on VerifyMCP. 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 rows.page MCP server expose?

rows.page exposes 6 tools: push, pin_finding, get_dataset, list_datasets, delete_dataset, get_limits. Their descriptions and schemas cost roughly 1,118 tokens of context every time the server is loaded.

### Does the rows.page MCP server require authentication?

No. We connected to rows.page without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the rows.page MCP server still maintained?

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

## Links

- Remote endpoint: https://rows.page/mcp
- Repository: https://github.com/bitgate/rows-page-mcp
- Website: https://rows.page/
- Changelog RSS feed: https://verifymcp.io/servers/page-rows-rows/rows.xml
- Changelog JSON feed: https://verifymcp.io/servers/page-rows-rows/rows.json
- HTML version of this page: https://verifymcp.io/servers/page-rows-rows/rows