_ registry / mcp streamable-http · checked 59m ago

rows.page

https://rows.page

Registry code: b635f979178ceb52

api record

rows.page turns rows into a shareable page where humans explore, filter and chart them, and it shows what changed between pushes. push works without an account: it returns a public url plus an owner_url carrying a dataset token (rpt_...). Always give your human the owner_url and tell them when the dataset expires; they keep it by opening that link and signing in. Push again with dataset + token to add a version. With an API key ('Authorization: Bearer rpk_...' or ?apiKey=rpk_... on the endpoint URL) datasets are kept on the account and key= upserts one named dataset per run. Pin findings so…

endpoint
https://rows.page/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is rows.page live?
Yes — it answered the hub's last check (checked 59m ago). It answered 100% of checks over the last 30 days.
Is rows.page free to use?
Yes — the hub reached it with no key and no payment.
What tools does rows.page have?
6 tools: delete_dataset, push, pin_finding, get_dataset, list_datasets, get_limits.
Is rows.page safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
221ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 6 tools
1 open 5 never probed 1 of 6 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_limits open 59m ago

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

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • delete_dataset unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "dataset"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Dataset token when not using an API key"
        },
        "dataset": {
          "type": "string",
          "description": "Dataset id"
        }
      }
    }
    arguments 16 lines
  • push unknown never probed

    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`).

    mcp-tool

    {
      "type": "object",
      "properties": {
        "csv": {
          "type": "string",
          "description": "CSV text with a header row"
        },
        "key": {
          "type": "string",
          "description": "Stable name for upserts with an API key, e.g. nightly-orders"
        },
        "run": {
          "type": "string",
          "description": "Run id of the job that produced it"
        },
        "tsv": {
          "type": "string",
          "description": "TSV text with a header row"
        },
        "url": {
          "type": "string",
          "description": "http(s) URL of a CSV, TSV, JSON, JSONL or Parquet file to fetch and publish"
        },
        "json": {
          "description": "A JSON array of objects (or an object holding one), as text or as a value"
        },
        "name": {
          "type": "string",
          "description": "File name, e.g. orders.csv"
        },
        "rows": {
          "type": "array",
          "items": {
            "type": "object"
          },
          "description": "Rows as an array of objects"
        },
        "jsonl": {
          "type": "string",
          "description": "One JSON object per line"
        },
        "title": {
          "type": "string",
          "description": "Dataset title shown on the page"
        },
        "token": {
          "type": "string",
          "description": "Dataset token (rpt_...) proving ownership of dataset"
        },
        "commit": {
          "type": "string",
          "description": "Commit sha of the code that produced it"
        },
        "format": {
          "enum": [
            "csv",
            "tsv",
            "json",
            "jsonl",
            "parquet"
          ],
          "type": "string",
          "description": "Format of url when it cannot be told"
        },
        "source": {
          "type": "string",
          "description": "Where the data came from (URL or description)"
        },
        "dataset": {
          "type": "string",
          "description": "Existing dataset id to push a new version to"
        },
        "summary": {
          "type": "string",
          "description": "A few sentences for the human: what this is and what to look at"
        },
        "findings": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "title"
            ],
            "properties": {
              "q": {
                "type": "string",
                "description": "Filter in the rows.page query language"
              },
              "sql": {
                "type": "string",
                "description": "Optional SQL against the table `data`"
              },
              "cols": {
                "type": "string",
                "description": "Visible columns, e.g. id,price,country"
              },
              "note": {
                "type": "string",
                "description": "Why it matters, in a sentence or two"
              },
              "sort": {
                "type": "string",
                "description": "Sort, e.g. -price,name"
              },
              "title": {
                "type": "string",
                "description": "Short headline of the finding"
              }
            }
          },
          "maxItems": 20
        },
        "id_column": {
          "type": "string",
          "description": "Column that identifies a row across versions, for changed-row diffs"
        },
        "visibility": {
          "enum": [
            "public",
            "private"
          ],
          "type": "string",
          "description": "private needs Pro or Max"
        }
      }
    }
    arguments 126 lines
  • pin_finding unknown never probed

    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`).

    mcp-tool

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

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

    mcp-tool

    {
      "type": "object",
      "required": [
        "dataset"
      ],
      "properties": {
        "token": {
          "type": "string",
          "description": "Dataset token, needed for private datasets without an API key"
        },
        "dataset": {
          "type": "string",
          "description": "Dataset id"
        },
        "version": {
          "type": "integer",
          "description": "Version number; latest when omitted"
        }
      }
    }
    arguments 20 lines
  • list_datasets unknown never probed

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

    mcp-tool

    {
      "type": "object",
      "properties": {
        "cursor": {
          "type": "string",
          "description": "next_cursor from the previous page"
        }
      }
    }
    arguments 9 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b635f979178ceb52.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b635f979178ceb52/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b635f979178ceb52/badge.svg)](https://brick.blue/agent/b635f979178ceb52?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.