Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Agent-native access to verifiable VAGP authority.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"authority": {
"command": "npx",
"args": [
"-y",
"@verimand/mcp-authority-server"
]
}
}
}Run this in your terminal
claude mcp add authority -- npx -y @verimand/mcp-authority-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"authority": {
"command": "npx",
"args": [
"-y",
"@verimand/mcp-authority-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"authority": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@verimand/mcp-authority-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain verimand.dev (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
MCP exposes capability. VAGP governs authority.
The Verimand MCP Authority Server gives MCP-compatible clients agent-native access to verifiable VAGP authority. It exposes a small stdio tool surface for asking whether a trusted registered agent currently has authority, inspecting trusted authority state, and verifying VAGP execution permits.
Tool availability does not itself grant authority. This server is not yet the enforcement gateway for protected tool execution.
@verimand/mcp-authority-serverdev.verimand/mcp-authority-server0.1.0@modelcontextprotocol/server 2.0.0, implementing the MCP 2026-07-28 spec with stdio legacy compatibilityverimand.resolve resolves whether a trusted registered agent is authorized for an action and returns a VAGP execution permit only when authority is confirmed.verimand.explain explains deterministic authority decision or permit-derived data. It is informational only.verimand.get_authority returns bounded authority relevant to an agent/action.verimand.get_mandate retrieves server-side trusted mandate metadata.verimand.get_agent_dna returns server-side trusted Agent DNA state and fingerprint information.verimand.verify_permit verifies a VAGP execution permit against current authority evidence.A local MCP client can start the published server with:
npx -y @verimand/mcp-authority-server@0.1.0
When running from this public repository:
npm ci
node dist/stdio.js
The process speaks MCP over stdio. stdout is reserved for MCP protocol messages; diagnostics go to stderr.
{
"mcpServers": { "verimand-authority": { "command": "npx", "args": ["-y", "@verimand/mcp-authority-server@0.1.0"] } } }
Do not place secrets, mandates, Agent DNA, revocation state or trusted context in agent-controlled MCP tool arguments. Production Verimand connection material must be supplied by the operator-controlled server environment, not by the agent using the MCP client.
{
"name": "verimand.resolve", "arguments": { "agentId": "agent:demo-support", "action": "ticket.read", "resourceId": "ticket:123", "requestId": "req-demo-1" } }
Expected structured content contains a deterministic authority decision, reason codes, selected mandate/path data and a permit only when VAGP resolves AUTHORITY_CONFIRMED.
All MCP input is untrusted. The server accepts only small closed tool arguments and maps them to server-side trusted VAGP state. An MCP caller cannot self-declare trusted identity, Agent DNA, mandates, attestations, revocation state or trusted context.
The MCP server delegates authority semantics to VAGP 0.3 authority services. It does not execute protected business actions and does not replace an enforcement gateway. Protected tool execution remains outside this package.
VAGP 0.3 is the public authority protocol: https://github.com/verimand/vagp. This MCP server is a Verimand interface for authority inspection and permit verification over MCP.
Version 0.1.0 is publicly available on npm and in the MCP Registry. The Verimand VAGP authority runtime required by this MCP server is bundled into dist/stdio.js; the installed package has no runtime dependency on unpublished @verimand/* workspace packages. The initial npm release was bootstrap-published without provenance. Future releases are configured for GitHub OIDC trusted staged publishing; this does not retroactively add provenance to 0.1.0.
From a clean clone, with Node.js 22 or newer:
npm ci
npm run build npm test npm run smoke:stdio
The public repository contains the audited bundled distribution, not the private TypeScript build source. Here npm run build checks the committed bundle's syntax and presence; it does not rebuild the bundle from source. The node:test suite starts the bundle over stdio, exercises all six public tools, checks a bounded permit and fail-closed cases, and verifies restart. The npm tarball remains restricted to the six published distribution files.
Report security issues to .