Expose supported operations through MCP

Install and inspect

npm install @receiz/mcp-server@129.0.0

The package exposes the receiz-mcp command and programmatic runtime. Inspect the installed tool schemas instead of inventing operation names or assuming every client has every private capability. Public reads may omit a bearer where their underlying rail permits it; protected calls retain their registered-application and actual grant requirements.

Run credential-free packaged checks

// Packaged synthetic checks only: no production identity, money or external writes.
import {createReceizMcpRuntime,callReceizTool,parseReceizMcpToolResult} from '@receiz/mcp-server';
const runtime=createReceizMcpRuntime();
for(const name of ['receiz_conformance_run','receiz_release_verify']){
 const result=parseReceizMcpToolResult(await callReceizTool(runtime,name,{}));
 console.log(JSON.stringify({name,ok:result.report?.ok,checks:result.report?.summary,writesPerformed:result.writesPerformed},null,2));
}

• Download the exact MCP example ↗

The conformance and release checks use the packaged synthetic checks and report writesPerformed. This example does not open a private identity or perform a financial/publication action. Keep local checks separate from a live host’s availability and granted permissions.

Configure a compatible client

{
  "mcpServers": {
    "receiz": {
      "command": "npx",
      "args": [
        "-y",
        "@receiz/mcp-server@129.0.0"
      ],
      "env": {
        "RECEIZ_BASE_URL": "https://receiz.com",
        "RECEIZ_APPLICATION_ID": "<exact registered application ID>"
      }
    }
  }
}

Preserve every byte of the application ID, including rc_, case, underscores and hyphens. Keep delegated tokens, passphrases and private identity paths in trusted local/host configuration, outside public pages, logs and model prompts. A public client coordinate is not user consent.

Respect tool authority

Test the actual selected environment

Exercise the intended operation, its expected refusals and interrupted result against the selected runtime. Programmatic helpers include createReceizMcpRuntime, callReceizTool and parseReceizMcpToolResult. Device-held subjects use openReceizMcpDeviceRuntime with actual private custody inputs. Upstream workspace build commands in package documentation are not automatically scripts in the Bank repository. A connected MCP client does not acquire universal private context or an automatic spending mandate.

• Agent identity and continuity ↗
• Integration assessment ↗