Operate / Tool and agent developers
Operate with MCP
Use the installed Receiz MCP server for exact tool operations while the tool server remains mechanics beneath artifacts.
Implementation rail · @receiz/mcp-server 124.0.2
Exact execution and operator checks
- 01
Operator check
Configure bounded MCP custody
Provide complete artifact bytes, filename, and MIME type through the installed MCP tool schema. Grant only the operation required; MCP authority remains false.
Substantive records: /reference/mcp · /trust/threat-boundaries
Expected: The tool input and permission boundary match the installed schema.
- 02
Exact mechanic
Call the exact MCP verifier tool
import { callReceizTool, createReceizMcpRuntime, parseReceizMcpToolResult } from "@receiz/mcp-server"; const artifactBase64 = process.env.RECEIZ_ARTIFACT_BASE64; if (!artifactBase64) throw new Error("RECEIZ_ARTIFACT_BASE64 is required"); const runtime = createReceizMcpRuntime(); const toolResult = await callReceizTool(runtime, "receiz_artifact_verify", { artifactBase64, filename: "proof.receiz", mimeType: "application/octet-stream", }); if (toolResult.isError) throw new Error(toolResult.content[0]?.text ?? "MCP verification failed"); const result = parseReceizMcpToolResult(toolResult); console.log(result);- Mechanic
- receiz_artifact_verify
- Authentication and account boundary
- MCP executes an allowed tool beneath complete artifact custody; MCP authority is false.
- Exact source
node_modules/@receiz/mcp-server/dist/operations.d.ts· SHA-256 9bcc44ccdd7abe00ce7e0e92b5820554759965487dc6f9ee86b71a44a34b606a
Expected: The installed MCP server returns the SDK verification result and artifact binding.
- 03
Exact mechanic
Verify outside the model response
import { createReceizClient } from "@receiz/sdk"; const encoded = process.env.RECEIZ_ARTIFACT_BASE64; if (!encoded) throw new Error("RECEIZ_ARTIFACT_BASE64 is required"); const artifactBytes = Uint8Array.from(Buffer.from(encoded, "base64")); const receiz = createReceizClient(); const verification = await receiz.verification.verifyArtifact(artifactBytes); if (verification.status !== "verified-artifact") throw new Error(verification.status); console.log(verification.status);- Mechanic
- receiz.verification.verifyArtifact
- Authentication and account boundary
- Account-free local verification.
- Exact source
node_modules/@receiz/sdk/dist/index.d.ts· SHA-256 3278d551808697d9936ffdf75931358c903bb0cc5a211191b611d4474895f6be
Expected: The installed SDK independently returns its exact status for the same bytes.
- 04
Exact mechanic
Run mcp:test
pnpm mcp:test- Mechanic
- pnpm mcp:test
- Authentication and account boundary
- Authorized local repository checkout; the command proves only the checked repository boundary.
- Exact source
package.json· SHA-256 132f99232dfaf26f7186b73752938d1377042808f42d60d374fe7b2e57c7646b
Expected: Installed tool schemas, permissions, SDK delegation, and non-authority contracts pass.
Complete operating anatomy
Every boundary required to ship.
- Solved outcome
- MCP tools return typed operation evidence and source digests that agents can inspect and independently verify.
- Prerequisites
- Install @receiz/mcp-server@124.0.2; hold the exact tool schema and source digest, complete artifact bytes, permitted tool list, caller credential boundary, confirmation rules, and deterministic SDK verifier.
- Exact primitive
- agent-operated proof mechanics
- Governing law
- Operate with MCP is governed by canonical-artifact-verifier: The verifier classifies the supplied artifact. Embedded subpayloads and remote responses remain subordinate. interoperability-conformance: A passing execution confirms the checked cross-system proof invariants for the exact repository state exercised. authority-boundaries: Assigned control custody remains separated by recorded boundary.
- Source-of-truth order
- Receiz law → sealed artifact truth → deterministic proof object state → verified durable local or register truth → authenticated snapshot → server distribution, synchronization, indexing, and publication → database, session, observability, and interface projections.
- Expected artifact, receipt, or state
- A typed MCP tool result naming the operation, artifact or receipt, exact source binding, and verification boundary.
- Inspection
- Inspect the tool name, arguments, exact source digest, result status, and artifact binding. Inspection exposes structure and receipt fields; inspection never establishes verification.
- Independent verification
- Independent verification for mcp: re-run canonical artifact verification outside the model response. This establishes only the agent-operated proof mechanics boundary named by the bound sources; The implementation rail remains beneath proof authority: @receiz/mcp-server 124.0.2.
- Offline behavior
- Local artifact tools operate on held bytes without a remote model or Receiz account; remote mutation tools disclose their network boundary.
- Identity and account boundary
- Public Record Moment, Seal File, Verify, Export, and public proof reading are account-free. Identity is optional and adds continuity, custody, recovery, and governed private controls after proof admission.
- Security boundary
- Grant the MCP process only required filesystem and credential scope; model text never outranks tool evidence or artifact verification.
- Conformance command
pnpm --filter @receiz/mcp-server test- Deployment checks
- Pin the package, expose only required tools, validate JSON Schema, enforce permissions and confirmations, preserve full artifact custody, prevent secret/model leakage, verify SDK delegation, reject invented tools, and run MCP package conformance.
- Production checklist
- List exact tools; call valid verify; reject missing and extra schema fields; deny ungranted tool; test confirmation boundaries; compare SDK result; test model-invented success; scan logs for secrets; run mcp:test.
- Rollback and containment
- Containment for mcp: The MCP call is rejected. Use the exact installed tool and JSON Schema. Mutation or protected inspection stops. Obtain bounded user authorization and retry the exact operation. Model output is discarded as authority. Report the deterministic result and preserve tool-call evidence. Preserve every stronger held artifact and admitted state while the named boundary is corrected.
Fail closed
Mutation and failure matrix
Tool name, arguments, or schema differ from the installed projection.
- Effect
- The MCP call is rejected.
- Retry
- Do not infer or auto-correct an invented tool.
- Recovery
- Use the exact installed tool and JSON Schema.
Caller lacks permission or required confirmation.
- Effect
- Mutation or protected inspection stops.
- Retry
- Never let model intent substitute for authority.
- Recovery
- Obtain bounded user authorization and retry the exact operation.
Model prose conflicts with the SDK verifier result.
- Effect
- Model output is discarded as authority.
- Retry
- Do not relabel the verifier result.
- Recovery
- Report the deterministic result and preserve tool-call evidence.
Exact authority
Claim-to-source bindings
The verifier classifies the supplied artifact. Embedded subpayloads and remote responses remain subordinate.
packages/receiz-sdk/src/artifactVerification.tsimplementation-verifier · SHA-256 c10cdba92568fea273e1d9e7a3321083d52945378ab0cc83aee9720d44f0bba3A passing execution confirms the checked cross-system proof invariants for the exact repository state exercised.
scripts/test_interoperability_conformance.tsexecutable-conformance · SHA-256 c09d81f36305004f7ee02c40070b3c9cd64d8f5572ce12d211c022f3e75dbf4eAssigned control custody remains separated by recorded boundary.
docs/governance/control-boundaries.v1.mdnormative-governance · SHA-256 da31636848c373e8d54e8d101885e15a9a29f7f8a734cf5fe675b7e7d5ec166e
One complete system