World Model MCP Server

world-model-mcp PyPI v0.15.4

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Trust grade
A
92/100
Last scanned get badge →
Trust
A · 92/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 = 92/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 − 8 = 92. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 10

high Shell/command execution in server code (adapters/pi/index.ts)MTC-SRC-002

In the server's implementation (`adapters/pi/index.ts:22`): 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 { mkdirSync } from "node:fs"; import { homedir } from "node:os"; import {

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 adapters/pi/index.ts

high Shell/command execution in server code (hooks/src/world-model-inject.ts)MTC-SRC-002

In the server's implementation (`hooks/src/world-model-inject.ts:11`): 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: import { spawn } from 'child_process'; type EventName = 'PostCompact' | 'UserPromptSubmit' | 'SessionStart'; interfac

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 hooks/src/world-model-inject.ts

low Shell/command execution in packaging/dev tooling (benchmarks/repeat-mistake/agent_runner.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`benchmarks/repeat-mistake/agent_runner.py:184`): 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: try: proc = subprocess.run( cmd, cwd=str(checkout.repo_dir),

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 benchmarks/repeat-mistake/agent_runner.py

low Shell/command execution in packaging/dev tooling (benchmarks/repeat-mistake/claude_client.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`benchmarks/repeat-mistake/claude_client.py:86`): 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: proc = subprocess.run( [self.binary, "-p", "--output-format", "text"],

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 benchmarks/repeat-mistake/claude_client.py

low Shell/command execution in packaging/dev tooling (benchmarks/repeat-mistake/clone_repo.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`benchmarks/repeat-mistake/clone_repo.py:39`): 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: stderr).""" proc = subprocess.run( cmd, cwd=cwd, capture_output=True, text=True,

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 benchmarks/repeat-mistake/clone_repo.py

low Shell/command execution in packaging/dev tooling (benchmarks/repeat-mistake/score.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`benchmarks/repeat-mistake/score.py:56`): 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: join(cmd)}") proc = subprocess.run(cmd, env=os.environ.copy()) return proc.returncode def collect_results(

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 benchmarks/repeat-mistake/score.py

low Shell/command execution in packaging/dev tooling (examples/managed-agents-self-hosted/deploy_modal.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`examples/managed-agents-self-hosted/deploy_modal.py:54`): 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: Modal immediately. subprocess.Popen(["python", "-m", "world_model_server.server"])

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 examples/managed-agents-self-hosted/deploy_modal.py

low Shell/command execution in packaging/dev tooling (scripts/engagement_tracker.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/engagement_tracker.py:78`): 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: d JSON.""" result = subprocess.run( ["gh", "api", path], capture_output=True, text=True, timeout=15,

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 scripts/engagement_tracker.py

low Shell/command execution in packaging/dev tooling (tests/integration/test_buzz_acp_handshake.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/integration/test_buzz_acp_handshake.py:195`): 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: oot, }) proc = subprocess.Popen( [buzz_agent], stdin=subprocess.PIPE, stdout=subprocess

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 tests/integration/test_buzz_acp_handshake.py

low Shell/command execution in packaging/dev tooling (tests/test_etch_verify_subprocess_e2e.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`tests/test_etch_verify_subprocess_e2e.py:80`): 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: nts. """ return subprocess.run( [sys.executable, "-m", "world_model_server.etch_verify", *args],

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 tests/test_etch_verify_subprocess_e2e.py

Tools 31

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

  • export_claude_mdno sensitive capability
  • find_contradictionsno sensitive capability
  • get_agents_md_constraintsno sensitive capability
  • get_audit_log_headno sensitive capability
  • get_co_edit_suggestionsno sensitive capability
  • get_compaction_auditno sensitive capability
  • get_constraintsno sensitive capability
  • get_context_for_actionno sensitive capability
  • get_decision_logno sensitive capability
  • get_health_reportno sensitive capability
Show 21 more tools ↓
  • get_injection_contextno sensitive capability
  • get_related_bugsno sensitive capability
  • ingest_pr_reviewsno sensitive capability
  • pin_annotationno sensitive capability
  • predict_regressionno sensitive capability
  • predict_test_failuresno sensitive capability
  • promote_constraintno sensitive capability
  • prove_entry_inclusionno sensitive capability
  • query_factno sensitive capability
  • recall_transcript_rangeno sensitive capability
  • record_compaction_auditno sensitive capability
  • record_correctionno sensitive capability
  • record_decisionno sensitive capability
  • record_eventno sensitive capability
  • record_test_outcomeno sensitive capability
  • resolve_contradictionno sensitive capability
  • search_globalno sensitive capability
  • seed_projectno sensitive capability
  • simulate_changeno sensitive capability
  • validate_changeno sensitive capability
  • verify_retrievalno sensitive capability

What this scan could not see

Versions 2

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.15.4 latest A 92/100 10 1.9.0 2026-07-24
v0.15.1 A 92/100 10 1.9.0 2026-07-23

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 · 92/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/world-model-mcp/badge.svg)](https://mcptrustchecker.com/registry/world-model-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/world-model-mcp"><img src="https://mcptrustchecker.com/registry/world-model-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/world-model-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 world-model-mcp --online --registry pypi

Use the free API → How scoring works

More in Data Science & ML