# VOUCH context MCP 0.1.2: fictional first use This is a standalone download candidate, not evidence of public availability or accepted host/model use. It requires Node 24+ and npm, but no Gen C account, private repository, Portal build, cloud credential or paid service. Gen C supplies this snapshot tool at no charge for personal and internal business use and retains ownership. Separately installed dependencies retain their own notices. This is not an open-source or redistribution grant, a paid entitlement or a support commitment. Read GUIDE.md for the full scope and privacy limits. Version0.1.2 has offline packaged-CLI evidence only. The earlier0.1.1 fictional Codex task is historical evidence, not a new0.1.2 installation or host proof. No installation, host configuration, protocol/model call or sharing is performed by this kit. Follow the explicit steps below only in your intended local setup. ## 1. Verify before installing First compare the ZIP's SHA-256 with Gen C's trusted release record. The digest for the ZIP belongs outside it; neither the filename nor this kit authenticates itself. Extract a verified ZIP into a fresh directory, then run from that folder: ```sh shasum -a 256 -c SHA256SUMS # On systems with sha256sum instead: sha256sum -c SHA256SUMS ``` All five listed files must pass. manifest.json records the source commit/tree, package digest, inventory and qualification. The tarball in this kit is exactly: - File: genc-project-handoff-mcp-0.1.2.tgz - Bytes: 71277 - SHA-256: 66d7e586dac53b1d2b11b826112b9ce8c24aae47c0dd68970b5b5f2d1b63fc7c Stop on a mismatch. Do not repair/repack an unverified input. Checksums detect changed bytes, not who produced them or whether you may share private data. ## 2. Install this local archive Keep the verified kit and use a separate fresh project. This command downloads only the archive's locked dependencies from npm if they are not cached; it does not publish anything. Empty local npmrc files avoid normal user/global settings; explicit environment-level npm settings still apply. Do not supply unrelated credentials. Review GUIDE.md's offline-cache alternative if offline use is needed. ```sh node --version npm --version # Continue only with Node 24 or newer, from the verified extracted kit folder. MCP_KIT="$PWD" MCP_ARCHIVE="$MCP_KIT/genc-project-handoff-mcp-0.1.2.tgz" MCP_EXAMPLE="$MCP_KIT/fictional-profile.json" MCP_PROJECT="$(mktemp -d "${TMPDIR:-/tmp}/genc-mcp-local.XXXXXX")" cd "$MCP_PROJECT" printf '%s\n' '{"name":"private-vouch-context","version":"1.0.0","private":true}' > package.json touch user.npmrc global.npmrc npm install --registry https://registry.npmjs.org \ --userconfig "$MCP_PROJECT/user.npmrc" --globalconfig "$MCP_PROJECT/global.npmrc" \ --engine-strict --ignore-scripts --no-audit --no-fund "$MCP_ARCHIVE" ./node_modules/.bin/genc-project-handoff-doctor --profile "$MCP_EXAMPLE" ``` Continue only when installation succeeds and the doctor exits 0. No host has been configured and no model has received context yet. The included JSON is a made-up single goal, copied unchanged from the reviewed synthetic fixture. ## 3. Add the fictional snapshot to Codex deliberately Use your existing supported Codex CLI, whose `codex mcp add --help` documents `NAME -- COMMAND...`. Inspect `codex mcp list` locally first. Use the name below only if it is unused; never overwrite/retarget an existing private entry. These commands change Codex MCP configuration and are not performed by this kit: ```sh codex mcp add vouch-fictional-snapshot-012 -- "$(command -v node)" \ "$MCP_PROJECT/node_modules/genc-project-handoff-mcp/mcp/server.mjs" \ --profile "$MCP_EXAMPLE" codex mcp get vouch-fictional-snapshot-012 --json ``` Keep the project and example paths in place. The saved entry is not proof of a connection. In your intended Codex session, confirm this server's `get_personal_profile` and `list_profile_entries` tools are exposed. If absent, follow that installed host's supported entry/session controls; do not toggle an already-enabled private entry or restart the whole app as a speculative fix. Record configured/tools-not-exposed instead of claiming success. Package version is 0.1.2; the unchanged protocol server still reports 0.1.0. Once its tool is available, ask: > Call get_personal_profile on vouch-fictional-snapshot-012 once with {}. Using only > that returned fictional snapshot, state the goal, say whether a constraint was > supplied, and suggest one practical next step. Identify the snapshot date and > lack of synchronization. Do not read a local file as a fallback, call another > server, save, send or change anything. Expected grounding: “Build a fictional colour study.” No constraint was supplied. The sample was captured 2026-10-17T05:26:53.776Z, is unsaved/unverified and is not synchronized. A palette-comparison suggestion is a new suggestion, not a stored fact. Tool exposure, actual returned data and use in the answer are separate acceptance observations, none asserted by this candidate's static checks. ## 4. Your own context is a separate choice Only explicitly selected, reviewed files belong in a later configuration. The 0.1.2 profile tool boundary uses the current canonical AI projection: it accepts reviewed current another-ai JSON and context-free legacy exports, preserves context area and UNVERIFIED_IMPORT labels, and omits original quotes, references, hashes and dates. Those labels verify no fact or authority. TXT and personal-backup JSON stay refused by --profile. The basic read-only tool is separate from the human-selection companion UI. Read GUIDE.md before using real data. A declined review/share request stays declined; never bypass it with a direct file read, CLI printout or another server. Existing private host registrations are untouched. There is no account sync, OAuth connection, writeback or permission to act. When finished, remove only the fictional entry through your host's supported controls before removing its files. Local npm uninstall does not remove host configuration. GUIDE.md covers optional modes, failure codes, offline install and maintainer-only source/CI routes; those routes are not prerequisites here.