git:20260308.e67cc2d to git:20261011.4243b1c

26 added, 16 removed. Audit A to A.

---

name: symbi-verify

- description: Verify MCP tool schemas using SchemaPin cryptographic verification. Use when adding new MCP servers, auditing existing tool integrations, or checking tool integrity.

+ description: Check local MCP configuration pins or separately verify a supplied schema signature.

---

- # SchemaPin Verification

+ # Verification

- Verify the cryptographic integrity of MCP tool schemas to ensure they haven't been tampered with.

+ First identify which evidence the user wants to verify.

- ## Verification Process

+ ## Configuration consistency

- 1. Identify the MCP server to verify (from .mcp.json or the user's request)

- 2. Use the `verify_schema` tool from the symbi MCP server to check the schema

- 3. Report the verification result:

- - **Verified**: Schema signature matches the publisher's key

- - **TOFU**: First-time use, key has been pinned for future verification

- - **Failed**: Schema has been modified since signing — DO NOT USE

- - **No signature**: Schema is unsigned — warn the user about risks

+ For a server in `.mcp.json`, run:

- ## When to Verify

+ ```sh

+ symbi schemapin verify --mcp-server NAME --config /absolute/path/.mcp.json

+ ```

- - Before first use of any new MCP tool

- - After updating MCP server configurations

- - When security audit is requested

- - When a tool returns unexpected results

+ A match only means the local server entry matches its recorded hash. It does not

+ verify remote schemas, publisher identity or server behavior. Report missing pins

+ and changed configurations separately using the CLI result. Do not silently pin

+ or overwrite a mismatch. SessionStart checks are advisory and bounded; explicitly

+ check additional servers if needed.

+ ## Schema signature

+ The `verify_schema` MCP tool accepts `schema` (the supplied schema document as a

+ string) and `public_key_url` (the publisher's key URL). Obtain the schema and key

+ location from a trusted source; a server name alone is insufficient. Call the tool

+ only when connected to the runtime MCP server. Inspect its `verified`, `message`,

+ `schema_hash` and signature details, including `valid` when present.

+ Report success only from successful verification. Missing signature material,

+ network errors, untrusted key provenance and failed signatures remain unresolved;

+ a matching configuration pin does not cure them. Never invent TOFU or publisher

+ verification from a successful local configuration check.