Run SignerSet

Find the mpas repository on this machine and read examples/demo/guides/credential-adapter.md inside it. Follow the guide to set up this account as the Credential Adapter operator. Ask the operator to supply the public did:jwk values collected from the proposer and maintainer accounts through an authenticated out-of-band channel; do not assume those harnesses transmitted the values automatically. Complete every step in order: create the ~/.mpas directory tree, generate the adapter key, identify and display its public DID as the Credential Adapter’s verifier DID, source the application plugin and adapter-config template from mpas-applications, fill in the deployment config with the supplied proposer and maintainer DIDs, store the upstream credential, and validate the config. Tell the operator to provide the verifier DID to the proposer for relay configuration. Start the adapter in hosted relay mode with --verifier-relay-url https://api.signerset.com; this is an outbound connection and requires no inbound public HTTP endpoint. Have the SignerSet operator confirm the organization bindings, participant roles, designated verifier, and maintainer review access are provisioned. The proposer and maintainer must both use https://api.signerset.com as coordination.url. Do not start a local Coordination Service for this hosted setup. Never expose or transfer any private key or key file. Do not proceed until the adapter health check passes.

Find the mpas repository on this machine and read examples/demo/guides/maintainer.md inside it. Follow the guide to set up this account as a Maintainer. Complete every step in order: create the ~/.mpas directory tree, generate your Ed25519 signing key, and display the public did:jwk value to the user. Tell the user to provide only that public DID to the Credential Adapter operator through an authenticated out-of-band channel. Do not claim you transmitted the DID unless you actually have an authorized communication channel. Never expose or transfer the private key or key file. Stop and wait for the user to confirm that the DID has been registered before continuing. Then create the signer server config and register the signer server as an MCP server in this agent harness. Set coordination.url to https://api.signerset.com, matching the proposer configuration. Confirm with the SignerSet operator that your DID has an enabled same-organization binding or an explicit signer_review grant, separately from registration in the Credential Adapter approval policy. Use the base URL exactly; the MPAS client appends /mpas/v1/coordination. Do not start a local Coordination Service. Do not add any proposer bridge to this account. Verify by listing your available MCP tools and polling for pending approvals.

Find the mpas repository on this machine and read examples/demo/guides/proposer.md inside it, and use the relay example in mpas-applications/README.md as the authority for the bridge configuration shape. Follow the guide to set up this account as a Proposer. Complete every step in order: create the ~/.mpas directory tree, generate your Ed25519 signing key, and display the public did:jwk value to the user. Tell the user to provide only that public DID to the Credential Adapter operator through an authenticated out-of-band channel. Do not claim you transmitted the DID unless you actually have an authorized communication channel. Never expose or transfer the private key or key file. Stop and wait for the user to confirm that the DID has been registered before continuing. Then find and clone the bridge for your application from mpas-applications, build it, and register it as an MCP server in this agent harness. For relay mode, configure actionEndpoint.url = "https://api.signerset.com" and actionEndpoint.verifierDid = "<Credential Adapter verifier DID>"; do not put the relay URL in adapter.url. Also set coordination.url to https://api.signerset.com, matching the maintainer configuration. Confirm that the SignerSet operator has provisioned your proposer organization binding and role, the designated verifier, and the nominated maintainers’ review access. Use the base URL exactly; the client appends /mpas/v1/coordination. Do not configure a localhost adapter or Coordination Service for this hosted setup. Do not add any maintainer signer server to this account. Verify by listing your available MCP tools and running a pass-through action.