Trust & Verification v1 MCP server for CommandLayer.
This server exposes MCP tools and bridges runtime-backed operations to the CommandLayer runtime over HTTP.
discover_action— list available trust-verification actions and their schemasget_action_schema— return CLAS request and receipt schema for a given verbverify_receipt— forward receipt to the runtime verifier and return resultresolve_agent— resolve ENS agent name to metadataget_protocol_version— return current protocol version and signing specvalidate_receipt_schema— validate a receipt object against the v1.1.0 schema locally
verify_receipt forwards { receipt } to the runtime verify endpoint and returns the runtime response directly. Trust comes from verifiable CLAS receipts (canonical JSON → SHA-256 → Ed25519), not from the MCP server itself.
COMMANDLAYER_RUNTIME_URL(optional, default:https://runtime.commandlayer.org)COMMANDLAYER_VERIFY_PATH(optional, default:/verify)ETHEREUM_RPC_URL(optional, used for ENS text record lookups, default:https://eth.llamarpc.com)PORT(optional, default:3000)
verify, authenticate, authorize, attest, sign, permit, grant, approve, reject, endorse. Only verify is connected to the runtime verifier in v1; all verbs are schema-discoverable via get_action_schema.
npm install
npm startDeploy with Railway using railway.toml, then point mcp.commandlayer.org to the deployment.
The following ENS TXT record keys are defined by the CLAS ens-discovery spec:
cl.schema— URI for the CLAS schema setcl.openapi— URI for the OpenAPI descriptorcl.mcp— URI for this MCP servercl.receipt.schema— URI for the receipt schemacl.verifier— verifier endpoint URIcl.capability— capability declarationcl.version— CLAS profile versioncl.family— schema family identifier (e.g.trust-verification)cl.verb— supported verb(s)cl.proof— supported proof primitive(s) (e.g.Ed25519)cl.signer— expected signer identifier(s)