Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Verimand MCP Authority Server

NPM · @VERIMAND/MCP-AUTHORITY-SERVER · SCANNED SEP 26

Agent-native access to verifiable VAGP authority.

65 Trust /100
Trust breakdown (7 categories)

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 Security100
  • 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
  • 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (Apache-2.0).Pass
  • Actively maintained (last published 5 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability54
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 343 tokens (~57/item across 6 items; 6 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 Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (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.

Install

How do I install the Verimand MCP Authority Server server?

Verimand MCP Authority Server runs locally as an npm package, launched with npx -y @verimand/mcp-authority-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 · @verimand/mcp-authority-server

# add to Claude Code
claude mcp add dev-verimand-mcp-authority-server -- npx -y @verimand/mcp-authority-server
// .cursor/mcp.json
{
  "mcpServers": {
    "dev-verimand-mcp-authority-server": {
      "command": "npx",
      "args": [
        "-y",
        "@verimand/mcp-authority-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dev-verimand-mcp-authority-server": {
      "command": "npx",
      "args": [
        "-y",
        "@verimand/mcp-authority-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dev-verimand-mcp-authority-server -- npx -y @verimand/mcp-authority-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-verimand-mcp-authority-server": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@verimand/mcp-authority-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dev-verimand-mcp-authority-server --command npx --arg -y --arg @verimand/mcp-authority-server
# ~/.hermes/config.yaml
mcp_servers:
  dev-verimand-mcp-authority-server:
    command: "npx"
    args: ["-y", "@verimand/mcp-authority-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dev-verimand-mcp-authority-server": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@verimand/mcp-authority-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dev-verimand-mcp-authority-server -t stdio -c npx -a -y @verimand/mcp-authority-server
// mcp.json
{
  "mcpServers": {
    "dev-verimand-mcp-authority-server": {
      "command": "npx",
      "args": [
        "-y",
        "@verimand/mcp-authority-server"
      ]
    }
  }
}
Changelog

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.

  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 65

    First indexed and scored.

Diagnostics

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 26 Sept 2026 · Analysed npm/@verimand/mcp-authority-server@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 3 packages
Packages resolved 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~317 tokens

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 →

Tool Tokens
verimand.explain ~47

Explain a deterministic VAGP authority decision or permit. Informational only; it cannot create or modify authority.

NameTypeReqDescription
decisionobject––
permitobject––

No output schema declared.

No examples provided.

verimand.get_agent_dna ~38

Return trusted Agent DNA state and fingerprint information from server-side trusted state. Read-only.

NameTypeReqDescription
agentIdstringyes–

No output schema declared.

No examples provided.

verimand.get_authority ~58

Return current bounded authority relevant to a trusted registered agent/action. Read-only.

NameTypeReqDescription
actionstring––
agentIdstringyes–
evaluationTimestring––
resourceIdstring––

No output schema declared.

No examples provided.

verimand.get_mandate ~39

Retrieve server-side trusted mandate information. Read-only.

NameTypeReqDescription
agentIdstring––
mandateIdstring––

No output schema declared.

No examples provided.

verimand.resolve ~79

Determine whether a trusted registered agent is currently authorized for a specific action. Calling this tool does not execute the protected action.

NameTypeReqDescription
actionstringyes–
agentIdstringyes–
evaluationTimestring––
parametersDigest–––
requestIdstring––
resourceIdstringyes–

No output schema declared.

No examples provided.

verimand.verify_permit ~56

Verify an existing VAGP execution permit against current authority evidence. Does not execute protected actions.

NameTypeReqDescription
evaluationTimestring––
idempotencyKeystring––
permitobjectyes–

No output schema declared.

No examples provided.

Common questions

What is the Verimand MCP Authority Server server?

Verimand MCP Authority Server is listed in the public MCP registry as dev.verimand/mcp-authority-server. Agent-native access to verifiable VAGP authority. This page covers its npm package (@verimand/mcp-authority-server).

Is the Verimand MCP Authority Server server safe to use?

Verimand MCP Authority Server scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 26 September 2026. It declares no install or post-install scripts. 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 Verimand MCP Authority Server server expose?

Verimand MCP Authority Server exposes 6 tools: verimand.resolve, verimand.explain, verimand.get_authority, verimand.get_mandate, verimand.get_agent_dna, verimand.verify_permit. Their descriptions and schemas cost roughly 317 tokens of context every time the server is loaded.

Is the Verimand MCP Authority Server server still maintained?

Verimand MCP Authority Server is still listed as active in the MCP registry. We last reached this channel on 26 September 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 Verimand MCP Authority Server server under?

Verimand MCP Authority Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.