# MANDATE Credential Broker (remote · mandate.nanocorp.app)

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

- Trust score: 67/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-29

## Components

- remote · `mandate.nanocorp.app`: 67/100 (this document), [markdown](https://verifymcp.io/servers/projetnanocorp-mandate/mandate.md), [page](https://verifymcp.io/servers/projetnanocorp-mandate/mandate)

## Channel facts

- Endpoint: `https://mandate.nanocorp.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-29.

- **Endpoint Security**: 51/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 380 tokens (~34/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 83/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 50% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mandate.revoke" implies "revoke" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the MANDATE Credential Broker MCP server?

MANDATE Credential Broker is a hosted endpoint at https://mandate.nanocorp.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http projetnanocorp-mandate 'https://mandate.nanocorp.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "projetnanocorp-mandate": {
      "url": "https://mandate.nanocorp.app/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "projetnanocorp-mandate": {
      "type": "http",
      "url": "https://mandate.nanocorp.app/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.projetnanocorp-mandate]
url = "https://mandate.nanocorp.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "projetnanocorp-mandate": {
      "type": "remote",
      "url": "https://mandate.nanocorp.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add projetnanocorp-mandate --url 'https://mandate.nanocorp.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  projetnanocorp-mandate:
    url: "https://mandate.nanocorp.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "projetnanocorp-mandate": {
      "Transport": "http",
      "Url": "https://mandate.nanocorp.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add projetnanocorp-mandate -t streamable-http -u 'https://mandate.nanocorp.app/mcp'
```

### Other

```json
{
  "mcpServers": {
    "projetnanocorp-mandate": {
      "type": "http",
      "url": "https://mandate.nanocorp.app/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-26 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 65, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (11)

### `mandate.discover` (~17 tokens)

Discover MANDATE agent tools

Returns this self-describing tool manifest.

### `mandate.mint` (~29 tokens)

Mint root mandate

Creates an active human-granted mandate for an agent and records it to the hash-chained ledger.

### `mandate.delegate` (~27 tokens)

Delegate mandate

Creates a child mandate only when it is a no-escalation subset of the parent mandate.

### `mandate.authorize-action` (~37 tokens)

Authorize gateway action

Submits an action through the Gateway and canonical Policy Engine; returns ALLOW, DENY, or REQUIRE_APPROVAL with ledger proof.

### `mandate.verify-proof` (~26 tokens)

Record or verify proof

Records a proof payload hash and appends proof evidence to the hash-chained ledger.

### `mandate.revoke` (~26 tokens)

Revoke mandate

Revokes a mandate subtree and records the revocation to the hash-chained ledger.

### `broker.register-credential` (~58 tokens)

Register credential handle

Registers an opaque vault handle/reference only; plaintext secret fields are rejected and never ledgered.

Input parameters:

- `metadata` (object)
- `vault_handle` (string, required): Opaque vault reference such as vault://provider/path; never a plaintext secret.

### `broker.request-access` (~43 tokens)

Request short-lived credential grant

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` (~36 tokens)

Use credential grant

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.

### `broker.revoke-grant` (~27 tokens)

Revoke credential grant

Revokes a broker grant by id and records the revocation to the ledger.

### `broker.introspect-grant` (~36 tokens)

Introspect credential grant

Validates a grant token seal, reports active/revoked/expired state, and records introspection to the ledger.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/projetnanocorp-mandate/mandate#diagnostics

## Score history

- 2026-09-29: 67
- 2026-09-28: 67
- 2026-09-27: 66
- 2026-09-26: 66
- 2026-09-25: 65
- 2026-09-24: 65
- 2026-09-23: 64
- 2026-09-22: 64
- 2026-09-21: 63
- 2026-09-20: 63
- 2026-09-19: 62
- 2026-09-18: 62
- 2026-09-17: 61
- 2026-09-16: 61
- 2026-09-15: 60
- 2026-09-14: 60
- 2026-09-13: 60
- 2026-09-12: 59
- 2026-09-11: 59
- 2026-09-10: 58
- 2026-09-09: 58
- 2026-09-08: 57
- 2026-09-07: 57
- 2026-09-06: 56
- 2026-09-05: 56

## Common questions

### What is the MANDATE Credential Broker MCP server?

MANDATE Credential Broker is an MCP server listed in the public MCP registry as io.github.projetnanocorp/mandate. MCP server for mandates, delegation, policy-gated execution, credential grants, and audit. This page covers its hosted endpoint (https://mandate.nanocorp.app/mcp).

### Is the MANDATE Credential Broker MCP server safe to use?

MANDATE Credential Broker scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the MANDATE Credential Broker MCP server expose?

MANDATE Credential Broker exposes 11 tools: mandate.discover, mandate.mint, mandate.delegate, mandate.authorize-action, mandate.verify-proof, and 6 more. Their descriptions and schemas cost roughly 362 tokens of context every time the server is loaded.

### Does the MANDATE Credential Broker MCP server require authentication?

No. We connected to MANDATE Credential Broker without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the MANDATE Credential Broker MCP server still maintained?

MANDATE Credential Broker is still listed as active in the MCP registry. We last reached this channel on 29 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mandate.nanocorp.app/mcp
- Repository: https://github.com/projetnanocorp/mandate
- Website: https://mandate.nanocorp.app/.well-known/mandate
- Changelog RSS feed: https://verifymcp.io/servers/projetnanocorp-mandate/mandate.xml
- Changelog JSON feed: https://verifymcp.io/servers/projetnanocorp-mandate/mandate.json
- HTML version of this page: https://verifymcp.io/servers/projetnanocorp-mandate/mandate