Project Bourne
NPM · @PROJECT-BOURNE/MCP · SCANNED AUG 22
Run reproducible scientific workloads on GPUs, local compute, Slurm, and PBS with provenance.
Available components
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 →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
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. How we score packages →
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.
npm · @project-bourne/mcp
claude mcp add kozakhou-project-bourne -- npx -y @project-bourne/mcp
{
"mcpServers": {
"kozakhou-project-bourne": {
"command": "npx",
"args": [
"-y",
"@project-bourne/mcp"
]
}
}
} {
"servers": {
"kozakhou-project-bourne": {
"command": "npx",
"args": [
"-y",
"@project-bourne/mcp"
]
}
}
} codex mcp add kozakhou-project-bourne -- npx -y @project-bourne/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kozakhou-project-bourne": {
"type": "local",
"command": [
"npx",
"-y",
"@project-bourne/mcp"
],
"enabled": true
}
}
} openclaw mcp add kozakhou-project-bourne --command npx --arg -y --arg @project-bourne/mcp
mcp_servers:
kozakhou-project-bourne:
command: "npx"
args: ["-y", "@project-bourne/mcp"] {
"McpServers": {
"kozakhou-project-bourne": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@project-bourne/mcp"
]
}
}
} assistant mcp add kozakhou-project-bourne -t stdio -c npx -a -y @project-bourne/mcp
{
"mcpServers": {
"kozakhou-project-bourne": {
"command": "npx",
"args": [
"-y",
"@project-bourne/mcp"
]
}
}
} 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.
- 22 Aug 26 39
First indexed and scored.
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 22 Aug 2026 · Analysed npm/@project-bourne/mcp@0.6.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
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.
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.
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.