osmp-mcp 1.0.22

OSMP MCP Server — Agentic AI instruction encoding. 86.8% byte reduction vs JSON. Inference-free decode. Any channel.

OSMP MCP Server

MCP server for the Octid Semantic Mesh Protocol (OSMP). Gives any MCP-compatible AI client native OSMP capability: encode, decode, validate, and resolve agentic instructions by table lookup. No inference at decode.

Install

pip install osmp-mcp

Or with uvx:

uvx osmp-mcp

What it does

• osmp_encode — Encode structured fields into a SAL instruction
• osmp_decode — Decode SAL to structured fields
• osmp_validate — Check composed SAL against composition rules before emission
• osmp_lookup — Search the opcode dictionary by namespace/keyword
• osmp_resolve — Resolve a domain code from D:PACK/BLK (ICD-10, ISO 20022, MITRE ATT&CK)
• osmp_discover — Search domain corpora by keyword
• osmp_benchmark — Run the canonical conformance suite
• osmp_compound_decode — Analyze DAG topology and loss tolerance
• osmp_batch_resolve — Multiple domain codes in one call

342 opcodes. 26 namespaces. Three MDR corpora (124,215 resolvable codes).

Composition Rules

SAL has a grammar (how to write a legal instruction) and a usage doctrine (which instruction to write). Both matter.

The taco test: K:ORD is financial order entry (ISO 20022). "Order me some tacos" is NL passthrough, not K:ORD[TACOS]. Read the ASD definition, not the mnemonic.

The lookup gate: Always call osmp_lookup before composing. If the opcode doesn't exist in the dictionary, it doesn't exist in the protocol.

Validation: Call osmp_validate after composing and before emitting. It catches hallucinated opcodes, missing consequence classes, namespace-as-target errors, byte inflation, and other structural violations.

Full composition doctrine: SAL-usage-doctrine-v1.md

octid.io | GitHub