Mandare
NPM · @MANDARELABS/MCP-SERVER · SCANNED OCT 4
Verify an agent fleet's tamper-evident ledger, check budgets, kill a runaway agent. Local-first.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 49 of 197 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mandarelabs/mandare). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 807 tokens (~100/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 35% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mandare_kill" implies "kill" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Mandare MCP server?
Mandare runs locally as an npm package, launched with npx -y @mandarelabs/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mandarelabs/mcp-server
claude mcp add com-mandarelabs-mandare -- npx -y @mandarelabs/mcp-server
{
"mcpServers": {
"com-mandarelabs-mandare": {
"command": "npx",
"args": [
"-y",
"@mandarelabs/mcp-server"
]
}
}
} {
"servers": {
"com-mandarelabs-mandare": {
"command": "npx",
"args": [
"-y",
"@mandarelabs/mcp-server"
]
}
}
} codex mcp add com-mandarelabs-mandare -- npx -y @mandarelabs/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mandarelabs-mandare": {
"type": "local",
"command": [
"npx",
"-y",
"@mandarelabs/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add com-mandarelabs-mandare --command npx --arg -y --arg @mandarelabs/mcp-server
mcp_servers:
com-mandarelabs-mandare:
command: "npx"
args: ["-y", "@mandarelabs/mcp-server"] {
"McpServers": {
"com-mandarelabs-mandare": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mandarelabs/mcp-server"
]
}
}
} assistant mcp add com-mandarelabs-mandare -t stdio -c npx -a -y @mandarelabs/mcp-server
{
"mcpServers": {
"com-mandarelabs-mandare": {
"command": "npx",
"args": [
"-y",
"@mandarelabs/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 1 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Analysed npm/@mandarelabs/mcp-server@0.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | mandarelabs/mandare |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mandarelabs/mandare/.github/workflows/release.yml@refs/tags/v0.1.0 |
| Rekor log index | 3030043311 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c9d3c481535b72fa0152b0285d0d847c924c8f07c37387095de5e06839b2cd7f9b970506c9e785ef4d83de08cd04054b60fc0c9389b657fe0163b6d16 |
Background: How many MCP packages publish verified provenance →
Dependencies 197 packages
| Packages resolved | 197 |
|---|---|
| Deprecated | 3 |
| Stale | 46 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
mandare_budget_status Budget status ~62
Per-mandate spend from the ledger: settled and reserved amounts (integer micro-units of the ledger currency), intent counts, refusal count, and whether the live budget counters equal a fresh replay of the ledger. Use before starting expensive work. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mandare_certify Export an integrity certificate ~63
Build the selective-disclosure integrity certificate (chain valid · witnessed · anchored) a third party can verify WITHOUT ledger access. Optionally disclose specific entries by seq; undisclosed entries stay salted hashes. Requires a configured witness.
| Name | Type | Req | Description |
|---|---|---|---|
| disclose_seqs | array | – | – |
No output schema declared.
No examples provided.
mandare_gateway_health Gateway health ~45
Read the running gateway door /healthz (halted state, card rail, witness gating). Requires MANDARE_GATEWAY_URL in the MCP server environment. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mandare_issue_mandate Issue a mandate ~178
Issue an owner-signed mandate (SD-JWT VC) for an agent: spend caps in WHOLE currency units (per transaction / day / task / total), optional human-approval threshold, validity window. The mandate file path is returned; point the gateway at it (MANDARE_MANDATE_PATH).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | yes | The agent's did:key (from mandare_issue_passport) |
| approval_above | number | – | Spends above this wait for an async human approval |
| currency | string | – | – |
| per_day | number | – | – |
| per_task | number | – | – |
| per_tx | number | – | Max per single call/transaction, whole currency units |
| purpose | string | – | – |
| total | number | – | – |
| valid_hours | number | – | – |
No output schema declared.
No examples provided.
mandare_issue_passport Issue an agent passport ~108
Issue an Agent Delegation Credential (SD-JWT VC) for a NEW agent: owner + local attestation authority keys from the vault, fresh agent did:key, revocation slot registered on the ledger. The credential and the agent private key are written to the operator-configured home directory; the result references them by path and never contains key material.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | Label for the new agent (also the artifact file prefix) |
| valid_days | integer | – | – |
No output schema declared.
No examples provided.
mandare_issue_token Issue a scoped access token ~123
Mint a short-lived proof-of-possession token an agent presents to the gateway (TTL ≤ 30 minutes). The grant INCLUDING ITS ONE-TIME SECRET is written 0600 to the operator-configured home directory; the result references it by path only — hand the FILE to the agent process (e.g. @mandarelabs/sdk tokenCredentialsFromIssueJson), never paste its contents into chat.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_did | string | yes | The agent DID the token is scoped to |
| mandate_id | string | yes | – |
| ttl_seconds | integer | – | – |
No output schema declared.
No examples provided.
mandare_kill Kill switch ~129
The LOCAL, offline, fail-closed kill: revoke ONE agent, ONE mandate (the agent survives, the permission slip dies), or --all (halts the whole door). Writes the revocation to the ledger; the gateway refuses the subject on its very next request. Bound virtual cards are revoked too. Kills only CLOSE doors — reversing one requires the operator (mandare reinstate).
| Name | Type | Req | Description |
|---|---|---|---|
| agent_did | string | – | – |
| all | boolean | – | Revoke the whole door (every subject it governs) |
| mandate_id | string | – | – |
| reason | string | – | – |
No output schema declared.
No examples provided.
mandare_verify Verify the Mandare ledger ~99
Verify the local ledger: hash chain, door signatures, RFC 6962 tree head, spend trail and budget-counter replay, approval trail, and revocation state. With check_witness=true also checks the chain against the externally witnessed head history (catches truncation and rewrites). Returns the machine-readable verification report. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| check_witness | boolean | – | Also verify against the configured witness (detects truncation/rewrites) |
No output schema declared.
No examples provided.
What is the Mandare MCP server?
Mandare is an MCP server listed in the public MCP registry as com.mandarelabs/mandare. Verify an agent fleet's tamper-evident ledger, check budgets, kill a runaway agent. Local-first. This page covers its npm package (@mandarelabs/mcp-server).
Is the Mandare MCP server safe to use?
Mandare scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mandare MCP server expose?
Mandare exposes 8 tools: mandare_verify, mandare_budget_status, mandare_issue_passport, mandare_issue_mandate, mandare_issue_token, and 3 more. Their descriptions and schemas cost roughly 807 tokens of context every time the server is loaded.
Is the Mandare MCP server still maintained?
Mandare is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Mandare MCP server under?
Mandare declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.