From project files to questions worth answering.
A read-only command-line tool and local MCP server. Gather bounded technical hints and return a reviewable report in Arabic or English.
Local developer build · 0.1.0-beta.3
Start with a report you can inspect yourself
If you have a local copy of the tool, inspect it, list the files and generate a report before connecting a cloud assistant. You can start with the prompt without installing.
beta.3 is not publicly distributed
The package is built and tested locally and requires Node.js 22 or later. A public installation artifact requires a separate release decision; the prompt path is available now. Earlier beta archives remain for reference only.
The precise privacy boundary
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.
1. Install in a separate tool directory
These commands are for a local artifact you already have. Create a separate tool directory and compare its checksum with the supplied checksum. Replace the absolute paths and keep 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/local-artifact/azizme-saudi-hosting-review-0.1.0-beta.3.tgz"Installation retrieves pinned dependencies from npm. The installed scanner needs no network or AI-provider key.
2. List the scope, then inspect
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"
3. Connect your local assistant when needed
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 · Earlier beta.2 checks covered native Codex tool discovery, inspection and reporting without a model call, and Claude Code validated the skill structure. Native-client testing of beta.3 is not yet recorded; connection approval and model use remain user steps.
Six tools, explicit boundaries
- inspect_project
- Collects bounded hints from the selected root, with coverage limits.
- assess_applicability
- Maps declarations to separate frameworks and applicability questions; assigns no legal class.
- assess_proposed_scopes
- Reviews the service boundary against the four scopes with the shared proposal policy.
- get_source_evidence
- Returns an allowlisted bundled reference with excerpt, locator, and version.
- build_review_pack
- Assembles sanitized Markdown and JSON, a data journey, and provider questions.
- compare_review_snapshots
- Compares one project’s observations, rule versions, and remaining questions.
Assistant and plugin workflows, in the same journey
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.