# io.github.CloudCorpRecords/limslens (npm · @reneturcios/limslens)

Query the Limslane dataset: search rows, compare values, column statistics.

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@reneturcios/limslens`: 73/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens.md), [page](https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens)
- oci · `ghcr.io/cloudcorprecords/limslens`: 43/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-limslens/ghcr-io-cloudcorprecords-limslens.md), [page](https://verifymcp.io/servers/cloudcorprecords-limslens/ghcr-io-cloudcorprecords-limslens)

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/limslens`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 92 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 404 tokens (~57/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.CloudCorpRecords/limslens MCP server?

io.github.CloudCorpRecords/limslens runs locally as an npm package, launched with npx -y @reneturcios/limslens mcp. 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 cloudcorprecords-limslens -- npx -y @reneturcios/limslens mcp
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-limslens": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/limslens",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-limslens": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/limslens",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-limslens -- npx -y @reneturcios/limslens mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-limslens": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@reneturcios/limslens",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cloudcorprecords-limslens --command npx --arg -y --arg @reneturcios/limslens --arg mcp
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-limslens:
    command: "npx"
    args: ["-y", "@reneturcios/limslens", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-limslens": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@reneturcios/limslens",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add cloudcorprecords-limslens -t stdio -c npx -a -y @reneturcios/limslens mcp
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-limslens": {
      "command": "npx",
      "args": [
        "-y",
        "@reneturcios/limslens",
        "mcp"
      ]
    }
  }
}
```

## 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-21 (score 73, +1)

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

### 2026-11-19 (score 72, +1)

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

### 2026-11-17 (score 71, +1)

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

### 2026-11-16 (score 70)

First indexed and scored.

## MCP tools (7)

### `dataset_columns` (~39 tokens)

Dataset columns and shape

The columns, which of them are numeric, the row count and the provenance banner of the Limslane dataset. Call this first to learn the schema.

### `dataset_search` (~57 tokens)

Search the dataset

Rows of the Limslane dataset whose cells contain the query (case-insensitive), up to 50.

Input parameters:

- `limit` (integer): maximum number of rows to return
- `query` (string, required): text to look for in any cell

### `dataset_row` (~58 tokens)

Look a row up by an exact key

The rows of the Limslane dataset where a column equals a value exactly (case-insensitive).

Input parameters:

- `column` (string, required): name of the column to match exactly
- `value` (string, required): value the column must equal (case-insensitive)

### `dataset_compare` (~70 tokens)

Compare rows side by side

The rows of the Limslane dataset whose column is any of the given values, in the order given — for "X vs Y" questions.

Input parameters:

- `column` (string, required): name of the column to compare on
- `values` (array, required): values to match in the column, in the order given

### `dataset_stats` (~62 tokens)

Summary statistics for a numeric column

count, min, max, mean, median and sum of a numeric column of the Limslane dataset (grouping commas and currency are handled; non-numeric rows are excluded and counted).

Input parameters:

- `column` (string, required): name of the numeric column to summarise

### `dataset_top` (~79 tokens)

Rank rows by a numeric column

The highest (or lowest) rows of the Limslane dataset by a numeric column — "which is the most/least X".

Input parameters:

- `ascending` (boolean): true for the lowest first; default highest first
- `column` (string, required): name of the numeric column to rank by
- `limit` (integer): maximum number of rows to return

### `dataset_provenance` (~39 tokens)

Where this data comes from, and how to cite it

The source, the date it was computed, the licence and the citation for the Limslane dataset. Read this to attribute a figure correctly.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70

## Common questions

### What is the io.github.CloudCorpRecords/limslens MCP server?

io.github.CloudCorpRecords/limslens is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/limslens. Query the Limslane dataset: search rows, compare values, column statistics. This page covers its npm package (@reneturcios/limslens).

### Is the io.github.CloudCorpRecords/limslens MCP server safe to use?

io.github.CloudCorpRecords/limslens scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/limslens MCP server expose?

io.github.CloudCorpRecords/limslens exposes 7 tools: dataset_columns, dataset_search, dataset_row, dataset_compare, dataset_stats, and 2 more. Their descriptions and schemas cost roughly 404 tokens of context every time the server is loaded.

### Is the io.github.CloudCorpRecords/limslens MCP server still maintained?

io.github.CloudCorpRecords/limslens is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.CloudCorpRecords/limslens MCP server under?

io.github.CloudCorpRecords/limslens declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.CloudCorpRecords/limslens MCP server?

VerifyMCP ran 16 checks on io.github.CloudCorpRecords/limslens, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@reneturcios/limslens
- Socket report: https://socket.dev/npm/package/@reneturcios/limslens
- Repository: https://github.com/CloudCorpRecords/limslens
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-limslens/reneturcios-limslens
