Project Cpu MCP Server

project-cpu-mcp npm v0.13.0 Source verified

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

MCP server for Project CPU — AI agents interact with the game on behalf of players

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 1

high Shell/command execution in server code (dist/paybox/auth/browser-opener.js)MTC-SRC-002

In the server's implementation (`dist/paybox/auth/browser-opener.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: rt { spawn } from 'node:child_process'; import { browserLaunchCommand } from './browser-opener.utils.js'; export class S

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/paybox/auth/browser-opener.js

Tools 55

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

  • cpu_authenticateno sensitive capability
  • cpu_buildno sensitive capability
  • cpu_buy_lotno sensitive capability
  • cpu_claim_craftno sensitive capability
  • cpu_claim_miningno sensitive capability
  • cpu_craftno sensitive capability
  • cpu_create_lotno sensitive capability
  • cpu_create_syndicateno sensitive capability
  • cpu_demolishno sensitive capability
  • cpu_evict_lotno sensitive capability
Show 45 more tools ↓
  • cpu_finalize_deliveryno sensitive capability
  • cpu_find_buildingsno sensitive capability
  • cpu_fulfill_revealno sensitive capability
  • cpu_get_attentionno sensitive capability
  • cpu_get_balanceno sensitive capability
  • cpu_get_buildingno sensitive capability
  • cpu_get_cellno sensitive capability
  • cpu_get_changesno sensitive capability
  • cpu_get_craft_statusno sensitive capability
  • cpu_get_game_configno sensitive capability
  • cpu_get_lotno sensitive capability
  • cpu_get_lot_termsno sensitive capability
  • cpu_get_mapno sensitive capability
  • cpu_get_market_indexno sensitive capability
  • cpu_get_marketsno sensitive capability
  • cpu_get_mining_statusno sensitive capability
  • cpu_get_resourceno sensitive capability
  • cpu_get_syndicateno sensitive capability
  • cpu_get_syndicate_membershipno sensitive capability
  • cpu_get_syndicate_player_contentno sensitive capability
  • cpu_get_transport_statusno sensitive capability
  • cpu_join_syndicateno sensitive capability
  • cpu_leave_syndicateno sensitive capability
  • cpu_list_fillsno sensitive capability
  • cpu_list_lotsno sensitive capability
  • cpu_list_my_lotsno sensitive capability
  • cpu_list_my_transportsno sensitive capability
  • cpu_list_recipesno sensitive capability
  • cpu_list_syndicatesno sensitive capability
  • cpu_mint_cellno sensitive capability
  • cpu_next_hopsno sensitive capability
  • cpu_quote_buyno sensitive capability
  • cpu_quote_lot_returnno sensitive capability
  • cpu_quote_mintno sensitive capability
  • cpu_quote_swapno sensitive capability
  • cpu_quote_transportno sensitive capability
  • cpu_return_lotno sensitive capability
  • cpu_revealno sensitive capability
  • cpu_route_networkno sensitive capability
  • cpu_set_sale_feeno sensitive capability
  • cpu_set_syndicate_paramsno sensitive capability
  • cpu_start_miningno sensitive capability
  • cpu_swapno sensitive capability
  • cpu_transfer_syndicate_managerno sensitive capability
  • cpu_transportno 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
v0.13.0 latest A 94/100 1 1.13.0 2026-09-07
v0.12.5 A 94/100 1 1.13.0 2026-09-05
v0.12.4 A 94/100 1 1.13.0 2026-09-04
v0.12.1 A 94/100 1 1.13.0 2026-09-01
v0.10.0 A 100/100 0 1.13.0 2026-08-29
Show 5 more versions ↓
v0.9.1 A 100/100 0 1.12.1 2026-08-24
v0.8.1 A 100/100 0 1.12.1 2026-08-12
v0.7.1 A 100/100 0 1.12.1 2026-08-07
B 87/100 0 1.12.1 2026-07-29
v0.7.0 A 100/100 0 1.12.1 2026-07-27

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/project-cpu-mcp/badge.svg)](https://mcptrustchecker.com/registry/project-cpu-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/project-cpu-mcp"><img src="https://mcptrustchecker.com/registry/project-cpu-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/project-cpu-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 project-cpu-mcp --online

Use the free API → How scoring works

More in Finance & Commerce