# Project Bourne (npm · @project-bourne/mcp)

Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance.

- Trust score: 39/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- npm · `@project-bourne/mcp`: 39/100 (this document), [markdown](https://verifymcp.io/servers/kozakhou-project-bourne/project-bourne-mcp.md), [page](https://verifymcp.io/servers/kozakhou-project-bourne/project-bourne-mcp)

## Channel facts

- Registry: `npm`
- Package: `@project-bourne/mcp`
- Version: `0.6.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-08-22.

- **Supply Chain Security**: 100/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.
  - No production dependencies, so there is no dependency health to assess.
- **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 (Apache-2.0).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package 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 Project Bourne MCP server?

Project Bourne runs locally as an npm package, launched with npx -y @project-bourne/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 kozakhou-project-bourne -- npx -y @project-bourne/mcp
```

### Cursor

```json
{
  "mcpServers": {
    "kozakhou-project-bourne": {
      "command": "npx",
      "args": [
        "-y",
        "@project-bourne/mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kozakhou-project-bourne": {
      "command": "npx",
      "args": [
        "-y",
        "@project-bourne/mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kozakhou-project-bourne -- npx -y @project-bourne/mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add kozakhou-project-bourne --command npx --arg -y --arg @project-bourne/mcp
```

### Hermes

```yaml
mcp_servers:
  kozakhou-project-bourne:
    command: "npx"
    args: ["-y", "@project-bourne/mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "kozakhou-project-bourne": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@project-bourne/mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kozakhou-project-bourne -t stdio -c npx -a -y @project-bourne/mcp
```

### Other

```json
{
  "mcpServers": {
    "kozakhou-project-bourne": {
      "command": "npx",
      "args": [
        "-y",
        "@project-bourne/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-08-22 (score 39)

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/kozakhou-project-bourne/project-bourne-mcp#diagnostics

## Score history

- 2026-08-22: 39

## Common questions

### What is the Project Bourne MCP server?

Project Bourne is an MCP server listed in the public MCP registry as io.github.KozakHou/project-bourne. Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance. This page covers its npm package (@project-bourne/mcp).

### Is the Project Bourne MCP server safe to use?

Project Bourne scores 39 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 August 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.

### Is the Project Bourne MCP server still maintained?

Project Bourne is still listed as active in the MCP registry. We last reached this channel on 22 August 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 Project Bourne MCP server under?

Project Bourne declares the Apache-2.0 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/@project-bourne/mcp
- Socket report: https://socket.dev/npm/package/@project-bourne/mcp
- Repository: https://github.com/KozakHou/project-bourne
- Changelog RSS feed: https://verifymcp.io/servers/kozakhou-project-bourne/project-bourne-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kozakhou-project-bourne/project-bourne-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kozakhou-project-bourne/project-bourne-mcp