Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IBM Db2 for i

NPM · MCP-SERVER-DB2I · SCANNED SEP 27

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

Available components

npm · mcp-server-db2i 49
49 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 225 of 226 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 225 of 226 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to Strom-Capital/mcp-server-db2i). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 0 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • 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.Unverified
Stability & Change Management0
  • 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.Unverified
Tool Coverage0
  • 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.Unverified
Tool Safety0
  • 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.Unverified
Capabilities0
  • 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

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. How we score packages →

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.

npm · mcp-server-db2i

# add to Claude Code
claude mcp add strom-capital-mcp-server-db2i -- npx -y mcp-server-db2i
// .cursor/mcp.json
{
  "mcpServers": {
    "strom-capital-mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "strom-capital-mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
# add to Codex CLI
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
    }
  }
}
# add to OpenClaw
openclaw mcp add strom-capital-mcp-server-db2i --command npx --arg -y --arg mcp-server-db2i
# ~/.hermes/config.yaml
mcp_servers:
  strom-capital-mcp-server-db2i:
    command: "npx"
    args: ["-y", "mcp-server-db2i"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "strom-capital-mcp-server-db2i": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
# add to Vellum
assistant mcp add strom-capital-mcp-server-db2i -t stdio -c npx -a -y mcp-server-db2i
// mcp.json
{
  "mcpServers": {
    "strom-capital-mcp-server-db2i": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-server-db2i"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 27 Sept 26 0
    • 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. security
    • 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
  • 26 Sept 26 0
    • 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. security
    • 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 functional
  • 25 Sept 26 +10
    • 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. security
    • 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 See what changed → functional
  • 24 Sept 26 +5
    • Known CVEs: partial → unverified ▼ security
    • 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. security
    • 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 functional
  • 23 Sept 26 34

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 27 Sept 2026 · Analysed npm/mcp-server-db2i@2.12.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo Strom-Capital/mcp-server-db2i
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/Strom-Capital/mcp-server-db2i/.github/workflows/release.yml@refs/heads/main
Rekor log index 2969504913
Predicate type https://slsa.dev/provenance/v1
Subject digest sha512:e32785cee5bf28200eb6fada611e67107dc9ed61c5b5ef990a0a0f6c73e736ca1f2072c5373ad1f8efa09f388bb47934aaf790ff3e6c1945db7560bb7

Background: How many MCP packages publish verified provenance →

Dependencies 225 packages
Packages resolved 225
Deprecated 2
Stale 68
No linked repository 1
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

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.

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.