_ registry / mcp streamable-http · checked 1h ago

csv-tools

https://csvfile.tools

Registry code: 878131f570220459

api record

Inspect and transform explicitly supplied CSV text. Limits: 256 KiB UTF-8 input/output, 50,000 cells, 200 columns. No file paths, URLs, storage, fetching or formula evaluation. All cell values remain literal strings. Row and column indices are zero-based. Returned CSV is complete; never truncated.

endpoint
https://csvfile.tools/api/csv/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 csv-tools live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is csv-tools free to use?
Yes — the hub reached it with no key and no payment.
What tools does csv-tools have?
4 tools: edit_csv_cells, filter_csv_rows, inspect_csv, sort_csv_rows.
Is csv-tools 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
648ms

last good check

priced tools
0

of 4 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • edit_csv_cells unknown never probed

    Apply up to 1,000 explicit edits to existing cells only. Zero-based row indices include the header. Duplicate coordinates apply in input order. Return complete CSV with literal string values; never evaluate formulas.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "csv",
    "edits"
  ],
  "properties": {
    "csv": {
      "type": "string",
      "maxLength": 262144,
      "description": "Complete UTF-8 CSV text, up to 256 KiB. All cells remain strings; formulas are never evaluated."
    },
    "edits": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "row",
          "column",
          "value"
        ],
        "properties": {
          "row": {
            "type": "integer",
            "maximum": 49999,
            "minimum": 0
          },
          "value": {
            "type": "string",
            "maxLength": 262144
          },
          "column": {
            "type": "integer",
            "maximum": 199,
            "minimum": 0,
            "description": "Zero-based column index. Every data record must contain this column."
          }
        },
        "additionalProperties": false
      },
      "maxItems": 1000
    },
    "delimiter": {
      "enum": [
        ",",
        "\t",
        ";",
        "|"
      ],
      "type": "string",
      "default": ",",
      "description": "Explicit delimiter; no delimiter inference."
    }
  },
  "additionalProperties": false
}
    arguments 57 lines
  • filter_csv_rows unknown 1h ago

    Keep data records whose explicit zero-based column equals an exact string. Header defaults to preserved. Reject missing target columns; preserve empty and ragged records otherwise.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "csv",
    "column",
    "value"
  ],
  "properties": {
    "csv": {
      "type": "string",
      "maxLength": 262144,
      "description": "Complete UTF-8 CSV text, up to 256 KiB. All cells remain strings; formulas are never evaluated."
    },
    "value": {
      "type": "string",
      "maxLength": 262144
    },
    "column": {
      "type": "integer",
      "maximum": 199,
      "minimum": 0,
      "description": "Zero-based column index. Every data record must contain this column."
    },
    "delimiter": {
      "enum": [
        ",",
        "\t",
        ";",
        "|"
      ],
      "type": "string",
      "default": ",",
      "description": "Explicit delimiter; no delimiter inference."
    },
    "hasHeader": {
      "type": "boolean",
      "default": true,
      "description": "Preserve the first record as a header."
    }
  },
  "additionalProperties": false
}
    arguments 43 lines
  • inspect_csv unknown 1h ago

    Return record, maximum column and cell counts with up to 20 preview records. Preserve ragged and empty records; never infer types or a delimiter.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "csv"
  ],
  "properties": {
    "csv": {
      "type": "string",
      "maxLength": 262144,
      "description": "Complete UTF-8 CSV text, up to 256 KiB. All cells remain strings; formulas are never evaluated."
    },
    "delimiter": {
      "enum": [
        ",",
        "\t",
        ";",
        "|"
      ],
      "type": "string",
      "default": ",",
      "description": "Explicit delimiter; no delimiter inference."
    },
    "previewRows": {
      "type": "integer",
      "default": 20,
      "maximum": 20,
      "minimum": 0
    }
  },
  "additionalProperties": false
}
    arguments 32 lines
  • sort_csv_rows unknown 1h ago

    Stably sort data records by an explicit zero-based column using literal code-unit string order, asc or desc. Header defaults to preserved. No numeric, date or locale inference. Reject missing target columns.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "csv",
    "column"
  ],
  "properties": {
    "csv": {
      "type": "string",
      "maxLength": 262144,
      "description": "Complete UTF-8 CSV text, up to 256 KiB. All cells remain strings; formulas are never evaluated."
    },
    "column": {
      "type": "integer",
      "maximum": 199,
      "minimum": 0,
      "description": "Zero-based column index. Every data record must contain this column."
    },
    "delimiter": {
      "enum": [
        ",",
        "\t",
        ";",
        "|"
      ],
      "type": "string",
      "default": ",",
      "description": "Explicit delimiter; no delimiter inference."
    },
    "direction": {
      "enum": [
        "asc",
        "desc"
      ],
      "type": "string",
      "default": "asc"
    },
    "hasHeader": {
      "type": "boolean",
      "default": true,
      "description": "Preserve the first record as a header."
    }
  },
  "additionalProperties": false
}
    arguments 46 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 878131f570220459.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/878131f570220459/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/878131f570220459/badge.svg)](https://brick.blue/agent/878131f570220459?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
80%

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.