INDIVIDUAL MCP TOOL
mandate.delegate
Creates a child mandate only when it is a no-escalation subset of the parent mandate.
LIVE ENDPOINT
https://mandate.nanocorp.app/mcp
Connect to this endpoint to inspect the live schema for mandate.delegate and invoke it with your own arguments.
Indexed input schema
{}Risk classification
Inferred read-only · medium confidence · heuristic, not a guarantee.
- No write-capable action terms were found; this is not proof that invocation has no side effects.
Parent server
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.mandate]
url = "https://mandate.nanocorp.app/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"mandate": {
"type": "http",
"url": "https://mandate.nanocorp.app/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: mandate
Remote MCP URL: https://mandate.nanocorp.app/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"mandate": {
"url": "https://mandate.nanocorp.app/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"mandate": {
"type": "http",
"url": "https://mandate.nanocorp.app/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "mandate",
"transport": "streamable-http",
"url": "https://mandate.nanocorp.app/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
mandate.discover— Returns this self-describing tool manifest.mandate.mint— Creates an active human-granted mandate for an agent and records it to the hash-chained ledger.mandate.authorize-action— Submits an action through the Gateway and canonical Policy Engine; returns ALLOW, DENY, or REQUIRE_APPROVAL with ledger proof.mandate.verify-proof— Records a proof payload hash and appends proof evidence to the hash-chained ledger.mandate.revoke— Revokes a mandate subtree and records the revocation to the hash-chained ledger.broker.register-credential— Registers an opaque vault handle/reference only; plaintext secret fields are rejected and never ledgered.broker.request-access— Asks 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.use— Redeems a sealed grant for the bound acting agent and executes the bound action through the Gateway and Policy Engine; does not expose plaintext secrets.