# IBM Db2 for i (npm · mcp-server-db2i)

Read-only SQL queries and schema inspection for IBM Db2 for i over ODBC, JT400 or Mapepire (SSH).

- Trust score: 49/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-27

## Components

- npm · `mcp-server-db2i`: 49/100 (this document), [markdown](https://verifymcp.io/servers/strom-capital-mcp-server-db2i/mcp-server-db2i.md), [page](https://verifymcp.io/servers/strom-capital-mcp-server-db2i/mcp-server-db2i)

## Channel facts

- Registry: `npm`
- Package: `mcp-server-db2i`
- Version: `2.12.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-09-27.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 225 of 226 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 225 of 226 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Strom-Capital/mcp-server-db2i).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.

**Unverified: 5 categories.** Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### How do I install the IBM Db2 for i MCP server?

IBM Db2 for i runs locally as an npm package, launched with npx -y mcp-server-db2i. 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 strom-capital-mcp-server-db2i -- npx -y mcp-server-db2i
```

### Cursor

```json
{
  "mcpServers": {
    "strom-capital-mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "strom-capital-mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add strom-capital-mcp-server-db2i -- npx -y mcp-server-db2i
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "strom-capital-mcp-server-db2i": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "mcp-server-db2i"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add strom-capital-mcp-server-db2i --command npx --arg -y --arg mcp-server-db2i
```

### Hermes

```yaml
mcp_servers:
  strom-capital-mcp-server-db2i:
    command: "npx"
    args: ["-y", "mcp-server-db2i"]
```

### Netclaw

```json
{
  "McpServers": {
    "strom-capital-mcp-server-db2i": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add strom-capital-mcp-server-db2i -t stdio -c npx -a -y mcp-server-db2i
```

### Other

```json
{
  "mcpServers": {
    "strom-capital-mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
```

## 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-09-27 (score 49, 0)

- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.

### 2026-09-26 (score 49, 0)

- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 2.11.0 → 2.12.0

### 2026-09-25 (score 49, +10)

- [security improvement] Known CVEs: unverified → partial
- [security] Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.
- [security] Tool safety: Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.
- [functional improvement] Dependency health: unverified → partial
- [functional] Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.
- [functional] Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.
- [functional] Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.
- [functional] Package version: 2.8.0 → 2.11.0
- [functional] Package version: 2.8.0 → 2.10.0
- [functional] Package version: 2.8.0 → 2.9.0
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 39, +5)

- [security regression] Known CVEs: partial → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Tool safety: Tool safety not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Dependency health: partial → unverified
- [functional] Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet.
- [functional] Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet.
- [functional] Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional] Package version: 2.2.1 → 2.8.0
- [functional] Package version: 2.2.1 → 2.5.1
- [functional] Package version: 2.2.1 → 2.5.0
- [functional] Package version: 2.2.1 → 2.4.0
- [functional] Package version: 2.2.1 → 2.3.0

### 2026-09-23 (score 34)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/strom-capital-mcp-server-db2i/mcp-server-db2i#diagnostics

## Score history

- 2026-09-27: 49
- 2026-09-26: 49
- 2026-09-25: 49
- 2026-09-24: 39
- 2026-09-23: 34

## Common questions

### What is the IBM Db2 for i MCP server?

IBM Db2 for i is an MCP server listed in the public MCP registry as io.github.Strom-Capital/mcp-server-db2i. Read-only SQL queries and schema inspection for IBM Db2 for i over ODBC, JT400 or Mapepire (SSH). This page covers its npm package (mcp-server-db2i).

### Is the IBM Db2 for i MCP server safe to use?

IBM Db2 for i scores 49 out of 100 on VerifyMCP. It declares no install or post-install scripts. Its build provenance is signed and verified. 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.

### Is the IBM Db2 for i MCP server still maintained?

IBM Db2 for i is still listed as active in the MCP registry. We last reached this channel on 27 September 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 IBM Db2 for i MCP server under?

IBM Db2 for i 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/mcp-server-db2i
- Socket report: https://socket.dev/npm/package/mcp-server-db2i
- Repository: https://github.com/Strom-Capital/mcp-server-db2i
- Website: https://db2i-mcp.com/
- Changelog RSS feed: https://verifymcp.io/servers/strom-capital-mcp-server-db2i/mcp-server-db2i.xml
- Changelog JSON feed: https://verifymcp.io/servers/strom-capital-mcp-server-db2i/mcp-server-db2i.json
- HTML version of this page: https://verifymcp.io/servers/strom-capital-mcp-server-db2i/mcp-server-db2i