Claude Pascal MCP Server

claude-pascal-mcp PyPI v0.13.6

Published by tina4stack — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Pascal/Delphi/Lazarus compilation and execution with Claude

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/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 = 93/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 − 7 = 93. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 6

high Shell/command execution in server code (src/pascal_mcp/adb.py)MTC-SRC-002

In the server's implementation (`src/pascal_mcp/adb.py:118`): 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: xtend(args) return subprocess.run( cmd, capture_output=True, text=not binary, timeo

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 src/pascal_mcp/adb.py

high Shell/command execution in server code (src/pascal_mcp/compiler.py)MTC-SRC-002

In the server's implementation (`src/pascal_mcp/compiler.py:74`): 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: result = subprocess.run( [fpc_path, "-iV"], capture_output=True, text=True, timeo

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 src/pascal_mcp/compiler.py

high Shell/command execution in server code (src/pascal_mcp/installer.py)MTC-SRC-002

In the server's implementation (`src/pascal_mcp/installer.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: try: result = subprocess.run( [fpc_exe, "-iV"], capture_output=True, text=True, timeou

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 src/pascal_mcp/installer.py

high Shell/command execution in server code (src/pascal_mcp/mac_ssh.py)MTC-SRC-002

In the server's implementation (`src/pascal_mcp/mac_ssh.py:197`): 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( args, capture_output=True, text=True, timeout=timeout, e

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 src/pascal_mcp/mac_ssh.py

high Shell/command execution in server code (src/pascal_mcp/paclient.py)MTC-SRC-002

In the server's implementation (`src/pascal_mcp/paclient.py:98`): 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: ient, *args] return subprocess.run( cmd, capture_output=True, text=True, timeout=timeout, encoding="

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 src/pascal_mcp/paclient.py

high Shell/command execution in server code (src/pascal_mcp/preview_bridge.py)MTC-SRC-002

In the server's implementation (`src/pascal_mcp/preview_bridge.py:109`): 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.Popen( [exe_path], stdout=subprocess.PIPE, stderr

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 src/pascal_mcp/preview_bridge.py

Tools 53

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

  • setup_fpcingests untrusted input
  • adb_device_infono sensitive capability
  • adb_devicesno sensitive capability
  • adb_installno sensitive capability
  • adb_keyno sensitive capability
  • adb_launch_appno sensitive capability
  • adb_list_packagesno sensitive capability
  • adb_pullno sensitive capability
  • adb_pushno sensitive capability
  • adb_screenshotno sensitive capability
Show 43 more tools ↓
  • adb_stop_appno sensitive capability
  • adb_swipeno sensitive capability
  • adb_tapno sensitive capability
  • adb_type_textno sensitive capability
  • app_clickno sensitive capability
  • app_keyno sensitive capability
  • app_typeno sensitive capability
  • build_dprojno sensitive capability
  • check_ios_deployno sensitive capability
  • check_syntaxno sensitive capability
  • compile_delphi_projectno sensitive capability
  • compile_pascalno sensitive capability
  • focus_ideno sensitive capability
  • get_compiler_infono sensitive capability
  • ios_codesignno sensitive capability
  • ios_create_ipano sensitive capability
  • ios_install_ipano sensitive capability
  • launch_appno sensitive capability
  • list_app_windowsno sensitive capability
  • list_project_filesno sensitive capability
  • list_remote_profilesno sensitive capability
  • mac_ssh_checkno sensitive capability
  • mac_ssh_runno sensitive capability
  • observe_ideno sensitive capability
  • parse_formno sensitive capability
  • paserver_check_connectionno sensitive capability
  • paserver_getno sensitive capability
  • paserver_infono sensitive capability
  • paserver_putno sensitive capability
  • paserver_removeno sensitive capability
  • paserver_scratch_dirno sensitive capability
  • read_ide_errorsno sensitive capability
  • run_pascalno sensitive capability
  • screenshot_appno sensitive capability
  • sim_bootno sensitive capability
  • sim_installno sensitive capability
  • sim_launchno sensitive capability
  • sim_listno sensitive capability
  • sim_open_urlno sensitive capability
  • sim_screenshotno sensitive capability
  • sim_shutdownno sensitive capability
  • sim_terminateno sensitive capability
  • sim_uninstallno sensitive capability

What this scan could not see

Versions 1

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.6 latest A 93/100 6 1.13.0 2026-08-25

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

Use the free API → How scoring works

More in Developer Tools