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

Bases, tables, and records in Airtable: list, search, create, update, delete.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@reneturcios/gridbase`
- 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-04.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 30 of 93 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 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1354 tokens (~90/item across 15 items; 15 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_records" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 15 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/gridbase MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 65, +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-02 (score 64, +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-01 (score 63)

First indexed and scored.

## MCP tools (15)

### `list_bases` (~30 tokens)

List every Airtable base the configured token can access, with its ID, name, and permission level.

### `list_tables` (~93 tokens)

List the tables in a base, with fields and views at the requested level of detail.

Input parameters:

- `baseId` (string, required): ID of the Airtable base whose tables to list.
- `detailLevel` (string): Level of detail for the returned tables: tableIdentifiersOnly (table ID and name only), identifiersOnly (IDs and names for tables, fields, and views), or full (the complete schema, the default).

### `describe_table` (~111 tokens)

Describe one table in a base, returning its fields and views at the requested level of detail.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table to describe.
- `detailLevel` (string): Level of detail for the returned table: tableIdentifiersOnly (table ID and name only), identifiersOnly (IDs and names for tables, fields, and views), or full (the complete schema, the default).
- `tableId` (string, required): ID or name of the table to describe.

### `list_records` (~93 tokens)

List records from a table, optionally filtered by an Airtable formula.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `filterByFormula` (string): Optional Airtable formula used to filter the records returned.
- `maxRecords` (number): Maximum number of records to return; defaults to 100.
- `tableId` (string, required): ID of the table to list records from.

### `search_records` (~129 tokens)

Search records in a table for a text term, across all text fields or a chosen subset.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `fieldIds` (array): Optional list of field IDs to restrict the search to; when omitted, all fields are searched.
- `maxRecords` (number): Maximum number of records to search through; defaults to 100.
- `searchTerm` (string, required): Text term to search for in record field values; matching is case-insensitive.
- `tableId` (string, required): ID of the table to search records in.

### `get_record` (~66 tokens)

Fetch a single record from a table by its record ID.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `recordId` (string, required): ID of the record to fetch.
- `tableId` (string, required): ID of the table containing the record.

### `create_record` (~78 tokens)

Create a new record in a table from a set of field values.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `fields` (object, required): Object of field values for the new record, keyed by field name or ID.
- `tableId` (string, required): ID of the table to create the record in.

### `update_records` (~85 tokens)

Update one or more records in a table, setting the given fields on each.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `records` (array, required): Array of records to update, each an object with an id and a fields object of values to set.
- `tableId` (string, required): ID of the table containing the records to update.

### `delete_records` (~70 tokens)

Delete one or more records from a table by their record IDs.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `recordIds` (array, required): Array of IDs of the records to delete.
- `tableId` (string, required): ID of the table to delete records from.

### `create_table` (~99 tokens)

Create a new table in a base with the given name, optional description, and field definitions.

Input parameters:

- `baseId` (string, required): ID of the Airtable base in which to create the table.
- `description` (string): Optional description for the new table.
- `fields` (array, required): Array of field definitions for the new table, each with a name and type and optional description and options.
- `name` (string, required): Name for the new table.

### `update_table` (~71 tokens)

Update a table's name or description.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `description` (string): New description for the table.
- `name` (string): New name for the table.
- `tableId` (string, required): ID of the table to update.

### `create_field` (~123 tokens)

Create a new field in a table with the given name and type.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `description` (string): Optional description for the new field.
- `name` (string, required): Name for the new field.
- `options` (object): Optional options object for the field type, such as choices for a select field.
- `tableId` (string, required): ID of the table to add the field to.
- `type` (string, required): Type of the new field, as an Airtable field type string.

### `update_field` (~88 tokens)

Update a field's name or description.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `description` (string): New description for the field.
- `fieldId` (string, required): ID of the field to update.
- `name` (string): New name for the field.
- `tableId` (string, required): ID of the table containing the field to update.

### `create_comment` (~105 tokens)

Add a comment to a record, optionally as a reply to an existing comment.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `parentCommentId` (string): Optional ID of an existing comment to reply to.
- `recordId` (string, required): ID of the record to add the comment to.
- `tableId` (string, required): ID of the table containing the record to comment on.
- `text` (string, required): Text of the comment.

### `list_comments` (~113 tokens)

List the comments on a record, newest first, with pagination.

Input parameters:

- `baseId` (string, required): ID of the Airtable base containing the table.
- `offset` (string): Optional pagination offset returned by a previous list_comments call, to fetch the next page.
- `pageSize` (number): Maximum number of comments to return per page (1 to 100).
- `recordId` (string, required): ID of the record whose comments to list.
- `tableId` (string, required): ID of the table containing the record.

## Diagnostics

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

## Score history

- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63

## Common questions

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

io.github.CloudCorpRecords/gridbase is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/gridbase. Bases, tables, and records in Airtable: list, search, create, update, delete. This page covers its npm package (@reneturcios/gridbase).

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

io.github.CloudCorpRecords/gridbase scores 65 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 4 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/gridbase MCP server expose?

io.github.CloudCorpRecords/gridbase exposes 15 tools: list_bases, list_tables, describe_table, list_records, search_records, and 10 more. Their descriptions and schemas cost roughly 1,354 tokens of context every time the server is loaded.

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

io.github.CloudCorpRecords/gridbase 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.

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

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

## Links

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