MCP reference

link to this sectionMCP reference

The @evimesh/mcp server exposes protocol tools and resources over the Model Context Protocol so an agent can read context and draft under explicit scopes.

link to this sectionTools

• create_claim: requires explicit actor attribution; validates the draft

against the protocol schema before returning it.

• record_run: requires source code, an immutable container reference,

environment, hardware, actor id, and signature.

• attach_evidence: links evidence to a claim under a confirm scope.

Draft validation enforces the protocol schema (actor attribution, full run metadata) before anything is returned; publication happens through the signed API with a human signature.

link to this sectionResources

Resources expose read-only protocol context (objects, states, and event chains) for an agent to ground its work.

link to this sectionSafety model

• Write actions require confirm or confirm-plus-sign scopes.
• Attribution is mandatory: the acting actor and the owning human are part

of the record.

• The canonical tool list lives in the source registry; the package README

mirrors it for install-time reading.