A read-only command-line tool and local MCP server. Gather bounded technical hints and return a reviewable report in Arabic or English.
Developer beta · 0.1.0-beta.2
Inspect the local package, list the files, then generate a report before connecting a cloud assistant. You do not install the AzizMe website inside your application.
A versioned artifact in this edition, not an npm-registry release. Node.js 22 or later. See README for tested setup and support limits.
The scanner runs locally and does not upload your repository to azizme.com. Its outputs pass to your assistant; a cloud model may receive those outputs and other context under its provider’s settings. Local scanning does not mean an entirely offline conversation.
It executes no project code, reads no secret files, follows no URLs, and connects to no cloud service. It extracts allowlisted technical tokens and relative references, but cannot guarantee that every filename is non-sensitive. Inspect the output first.
Create a dedicated tool directory and open it in your terminal. Replace the paths below with your absolute paths, keeping the quotes. Do not target a drive root or your home directory.
node --version
npm init -y
npm install --ignore-scripts --no-audit --no-fund "/absolute/downloads/azizme-saudi-hosting-review-0.1.0-beta.2.tgz"Installation retrieves pinned dependencies from npm. The installed scanner needs no network or AI-provider key.
node "/absolute/tool/node_modules/@azizme/saudi-hosting-review/dist/cli.js" list --root "/absolute/project"
node "/absolute/tool/node_modules/@azizme/saudi-hosting-review/dist/cli.js" inspect --root "/absolute/project" --locale en --format markdownUse --format json for a sanitized report you can read in the viewer. README documents explicit safe saving, skips, and file limits. A scan does not prove production locations, backups, or contracts.
To supply component facts, copy examples/scope-input.unknown.json from the installed package into a private working folder outside the application project, then update the service description and inventory. Keep unsupported locations unknown; the starter is not evidence. Add this option to inspect: --scope-input "/private/review/scope-input.json"
In your selected trusted Codex project, merge the following block into .codex/config.toml after replacing the paths. Preserve existing settings. This connection is scoped to that project; the website does not edit client settings or launch a process.
[mcp_servers.saudi-hosting-review]
command = "node"
args = ["/absolute/tool/node_modules/@azizme/saudi-hosting-review/dist/server.js", "--root", "/absolute/project"]
startup_timeout_sec = 30
tool_timeout_sec = 20
enabled = trueCheck the connection with /mcp. If the client resolves a different Node version, replace node with the absolute path to Node.js 22 or later. The alternative codex mcp add command changes user-level configuration; use it only when you intend that scope.
For Claude Code, merge examples/claude.mcp.json into the project’s .mcp.json, then review the connection approval in the client. Installing the skill does not automatically connect MCP.
Official Codex MCP documentation · Native Codex tool discovery, inspection, and reporting were tested without a model call. Claude Code validated the skill structure and recognized the project configuration; connection approval and model use remain user steps. The guide records the test limits.
The package includes a reusable review skill and documented configuration templates. The skill supplies the workflow; the MCP connection supplies the scanner. Plugin files and client configuration are not installed automatically.