rows.page
REMOTE · ROWS.PAGE
Push CSV, JSON, JSONL or Parquet from your agent and get a link a human can explore.
Available components
Last scanned (21 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Data and Analytics
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. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
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 4 Nov 2026 · Probed https://rows.page/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rows.page | CN=WE1,O=Google Trust Services,C=US | 29 Sept 2026 | 28 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | f53a1f8ab15f01bd0e6abe1f8d745da5 |
| SANs: rows.page, www.rows.page, *.www.rows.page | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rows.page. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| page. | present | 64712 | 8 | Verified |
| rows.page. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rows.page/mcp | Verified | 200 | |
| http (plaintext) | http://rows.page/mcp | Served over HTTP | 200 |
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 →
delete_dataset ~44
Delete a dataset you own. Its URL stops working immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Dataset id |
| token | string | – | Dataset token when not using an API key |
No output schema declared.
No examples provided.
get_dataset ~68
Read a dataset: meta, recent versions, findings, columns and the first 20 preview rows.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Dataset id |
| token | string | – | Dataset token, needed for private datasets without an API key |
| version | integer | – | Version number; latest when omitted |
No output schema declared.
No examples provided.
get_limits ~26
Show your plan, its caps (file size, datasets, version history) and usage.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_datasets ~38
List the datasets kept on your account, newest first. Needs an API key.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | next_cursor from the previous page |
No output schema declared.
No examples provided.
pin_finding ~353
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| cols | string | – | Visible columns, e.g. id,price,country |
| dataset | string | yes | 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 | yes | 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 |
No output schema declared.
No examples provided.
push ~589
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`).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
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.
remote · rows.page
claude mcp add --transport http page-rows-rows 'https://rows.page/mcp'
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.