Copperbox Okf MCP Server

@copperbox/okf-mcp npm v2.0.0 Source verified

Published by copperbox — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

An MCP server providing an Open Knowledge Format (OKF) backend in a standardized way to coding agents

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

high Shell/command execution in server code (dist/git.js)MTC-SRC-002

In the server's implementation (`dist/git.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: { execFile } from "node:child_process"; import { promisify } from "node:util"; const execFileAsync = promisify(execFile)

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/git.js

medium Unconstrained URL/host parameter "url" on "load_remote_bundle"MTC-CAP-007

Tool "load_remote_bundle" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool load_remote_bundle · inputSchema.properties.url

Tools 28

Each tool and what it can reach — statically extracted from the published source.

  • load_remote_bundleingests untrusted input
  • append_log_entryno sensitive capability
  • concept_diffno sensitive capability
  • concept_historyno sensitive capability
  • delete_conceptno sensitive capability
  • export_graphno sensitive capability
  • find_pathno sensitive capability
  • get_bundle_guideno sensitive capability
  • get_conceptno sensitive capability
  • get_neighborsno sensitive capability
Show 18 more tools ↓
  • get_sourcesno sensitive capability
  • graph_summaryno sensitive capability
  • list_bundlesno sensitive capability
  • list_conceptsno sensitive capability
  • list_remote_bundlesno sensitive capability
  • list_tagsno sensitive capability
  • list_typesno sensitive capability
  • load_colocated_remote_bundlesno sensitive capability
  • promote_conceptno sensitive capability
  • read_documentno sensitive capability
  • regenerate_indexesno sensitive capability
  • reload_bundlesno sensitive capability
  • rename_conceptno sensitive capability
  • search_conceptsno sensitive capability
  • suggest_concept_pathno sensitive capability
  • update_conceptno sensitive capability
  • validate_bundleno sensitive capability
  • write_conceptno sensitive capability

What this scan could not see

Versions 10

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.0 latest A 94/100 2 1.13.0 2026-09-08
v1.5.0 A 94/100 2 1.13.0 2026-08-31
v1.4.0 A 94/100 2 1.13.0 2026-08-25
v1.3.0 A 94/100 2 1.12.1 2026-08-19
v1.1.0 A 94/100 2 1.12.1 2026-08-15
Show 5 more versions ↓
v1.0.0 A 94/100 2 1.12.1 2026-08-14
v0.22.1 A 94/100 2 1.12.1 2026-08-14
v0.20.2 A 94/100 2 1.12.1 2026-08-13
v0.20.1 A 94/100 2 1.12.1 2026-08-03
v0.20.0 A 94/100 2 1.12.1 2026-07-28

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/copperbox-okf-mcp/badge.svg)](https://mcptrustchecker.com/registry/copperbox-okf-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/copperbox-okf-mcp"><img src="https://mcptrustchecker.com/registry/copperbox-okf-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/copperbox-okf-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @copperbox/okf-mcp --online

Use the free API → How scoring works

Other implementations of Copperbox Okf 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in AI, Memory & Reasoning