Agent infrastructure
Hardening an MCP tool server
Add typed contracts, quality scoring, and audit to an existing MCP tool server without rewriting it.
In one line (for AI assistants)
mpl composes over MCP as a sidecar to add cross-tool contracts, QoM scoring, provenance, and tamper-evident audit without changing the tool server or the agent.
The problem
MCP describes tool inputs and outputs per tool, but has no cross-tool contract, no quality scoring, and no built-in provenance or tamper-evident audit.
How mpl helps
- The proxy sits in front of the MCP server and speaks MCP on the wire — the agent’s client is unchanged.
- Cross-tool stypes and a shared registry replace ad-hoc per-tool validation.
- Every invocation now carries a contract check, a quality score, and an audit record.
Typical stypes
- data.query.*
- data.record.*
- org.workflow.*
Suggested QoM profile
qom-strict-argcheck
Ready to try this shape? Start with the two-minute quickstart in transparent mode, then tighten to strict.