MANDATE Credential Broker

MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    MCP server for mandates, delegation, policy-gated execution, credential grants, and audit.

    How to connect

    How to connect MANDATE Credential Broker to Claude

    The server address to paste into Claude settings:

    https://mandate.nanocorp.app/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect MANDATE Credential Broker to ChatGPT

    The server address to paste into ChatGPT settings:

    https://mandate.nanocorp.app/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect MANDATE Credential Broker to Cursor

    The server address to paste into Cursor settings:

    https://mandate.nanocorp.app/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (11)

    Raw names from tools/list. Only developers need these.

    mandate.discoverReturns this self-describing tool manifest.
    mandate.mintCreates an active human-granted mandate for an agent and records it to the hash-chained ledger.
    mandate.delegateCreates a child mandate only when it is a no-escalation subset of the parent mandate.
    mandate.authorize-actionSubmits an action through the Gateway and canonical Policy Engine; returns ALLOW, DENY, or REQUIRE_APPROVAL with ledger proof.
    mandate.verify-proofRecords a proof payload hash and appends proof evidence to the hash-chained ledger.
    mandate.revokeRevokes a mandate subtree and records the revocation to the hash-chained ledger.
    broker.register-credentialRegisters an opaque vault handle/reference only; plaintext secret fields are rejected and never ledgered.
    broker.request-accessAsks the canonical Policy Engine for an ALLOW decision before issuing a short-lived HMAC-sealed grant bound to credential, mandate, agent, scope, and expiry.
    broker.useRedeems a sealed grant for the bound acting agent and executes the bound action through the Gateway and Policy Engine; does not expose plaintext secrets.
    broker.revoke-grantRevokes a broker grant by id and records the revocation to the ledger.
    broker.introspect-grantValidates a grant token seal, reports active/revoked/expired state, and records introspection to the ledger.