
limslens
io.github.CloudCorpRecords/limslens
Query the Limslane dataset: search rows, compare values, column statistics.
Documentation
limslens
A window onto one published dataset, without downloading it. limslens is a local forwarding client for the hosted Limslane MCP service: it answers tools/list on your own machine from the captured tool definitions and forwards every query to Limslane, returning the answers exactly as the service sends them back.
The surface is read-only querying of the Limslane dataset. You can learn its shape first (columns, which of them are numeric, row count), search rows by text appearing in any cell, look rows up by an exact column value, pull several values side by side for comparison, ask for summary statistics on a numeric column, rank rows by a numeric column, and read the provenance record — source, date, licence and citation — so a figure can be attributed correctly. Nothing is cached, stored or computed locally — the package is a pipe, not a database.
The tools
dataset_columns— The columns of the dataset, which of them are numeric, the row count and the provenance banner. Takes no arguments; call it first to learn the schema.dataset_search— Rows whose cells contain the query text (case-insensitive), up to 50.queryis required;limitcaps the rows returned (1–50).dataset_row— The rows where a column equals a value exactly (case-insensitive). Bothcolumnandvalueare required.dataset_compare— The rows whose column is any of the given values, in the order given — built for "X vs Y" questions.columnandvalues(2–10 values) are required.dataset_stats— count, min, max, mean, median and sum of a numeric column. Grouping commas and currency are handled; non-numeric rows are excluded and counted.columnis required.dataset_top— The highest rows by a numeric column, or the lowest whenascendingis true.columnis required;limitcaps the rows (1–50).dataset_provenance— The source, the date the data was computed, the licence and the citation for the dataset. Takes no arguments.
Install and run
As an MCP server via npm:
npx -y @reneturcios/limslens mcp
MCP client configuration:
{
"mcpServers": {
"limslens": {
"command": "npx",
"args": ["-y", "@reneturcios/limslens", "mcp"]
}
}
}
As a container:
docker run -i ghcr.io/cloudcorprecords/limslens
docker run --rm ghcr.io/cloudcorprecords/limslens dataset_search '{"query":"example"}'
CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
limslens dataset_columns
limslens dataset_search '{"query":"example","limit":10}'
limslens dataset_row '{"column":"name","value":"example"}'
limslens dataset_compare '{"column":"name","values":["a","b"]}'
limslens dataset_stats '{"column":"score"}'
limslens dataset_top '{"column":"score","limit":5}'
limslens dataset_provenance
limslens --version
Exit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
LIMSLANE_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://limslane.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The Limslane registry record declares no headers on its remote, so limslens sends no authentication header of any kind — queries are keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with limslens error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from source
The test suite checks the served tool list against the captured surface, exercises the session handshake and its reuse, asserts that no Authorization header is sent under any environment, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
@reneturcios/limslensnpm install @reneturcios/limslensghcr.io/cloudcorprecords/limslens:0.1.0docker pull ghcr.io/cloudcorprecords/limslens:0.1.0:undefinedRelated Servers
io.github.CloudCorpRecords/abandoncheck
Judge whether a dependency is maintained, from factual signals: releases, commits, archival.
io.github.CloudCorpRecords/actionbridge
Zapier exposed actions as MCP tools via a generic action runner.
io.github.CloudCorpRecords/actionpin
GitHub Actions supply-chain hardener: audit workflows for unpinned actions and build a SHA pin plan.