mpl

About

A protocol layer for trustworthy agent comms

mpl — the Meaning Protocol Layer — is infrastructure for teams running multi-agent systems where “it worked in testing” is not an acceptable answer.

The premise

Agent-to-agent and agent-to-tool calls are usually a JSON blob over HTTP. The receiver hopes the shape is right, the values are sane, the call was made by who it says, and that someone, somewhere, wrote it down. In a single-agent prototype that’s fine. Across a chain of agents in a regulated environment, it isn’t.

mpl inserts a thin protocol layer in front of your existing MCP or A2A transport. It does four jobs at every hop:

What’s in the repo

The open-source distribution at github.com/Skelf-Research/mpl includes:

Status

Phase 1 (core protocol, Python SDK, sidecar proxy, schema registry) and Phase 2 (TypeScript SDK, registry API, Helm chart, policy engine) are complete. Phase 3 (conformance suite, A2A hardening, production readiness) is in progress. Test suite: 144 passing as of the README. License: MIT.

Who it’s for

Teams running multi-agent systems where a regulator, an auditor, or an internal risk committee is going to ask “show me what the agent did and prove it wasn’t tampered with.” That includes regulated AI ops (finance, healthcare), platform teams shipping internal agent fabrics, and anyone who’d rather catch a malformed tool call at the boundary than in a post-mortem.

Who’s behind it

mpl is a Skelf Research project. Skelf Research builds protocol-layer and observability infrastructure for AI systems, all open source. See the full project list.