Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Live cross-domain authority-state resolution for delegated agents through MCP.
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.
GATE_URL, GATE_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
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": {
"gate-authority-network": {
"command": "npx",
"args": [
"-y",
"@gate-avn/mcp"
],
"env": {
"GATE_URL": "your-value",
"GATE_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add gate-authority-network --env GATE_URL=your-value --env GATE_API_KEY=your-value -- npx -y @gate-avn/mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"gate-authority-network": {
"command": "npx",
"args": [
"-y",
"@gate-avn/mcp"
],
"env": {
"GATE_URL": "your-value",
"GATE_API_KEY": "your-value"
}
}
}
}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": {
"gate-authority-network": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gate-avn/mcp"
],
"env": {
"GATE_URL": "your-value",
"GATE_API_KEY": "your-value"
}
}
}
}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 with the GitHub account Projetxana, which owns the repo
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.
You need to fill in: GATE_URL, GATE_API_KEY
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-dev.8) reached the registry 10 days 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, Foliosio
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.
Read your support inbox, tag conversations and save draft replies from your AI agent. Never sends.
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.
Stage 17 Developer Preview · Live public adoption
Does a live delegation path from this principal to this actor still exist right now?
GATE is the live authority-state resolver for delegated agents across trust domains.
It resolves whether a currently valid authority path still exists at effect time using live authority state from external trust domains. GATE does not mint a proprietary delegation token, replace OAuth, replace your policy engine, or require MCP.
Current operational boundary: one Canadian primary database, no production regional replicas, and no independent third-party issuer propagation SLA.
maxStalenessMsmeasures primary snapshot age only. The Developer Preview is not enterprise GA.
Stage 17 has validated real Free onboarding, independent CAEP/SSF revocation interoperability, external problem validation, and Free-to-paid entitlement continuity. GATE remains a Developer Preview: independent adoption and enterprise-scale operation are the next validation targets.
Identity / credentials / policy / issuer systems
| | authority state + trust signals v +-------------------+ | GATE | | live authority | | state resolver | +-------------------+ | gate.verify() | v trusted effect boundary
GATE complements identity, credential, policy and gateway systems. MCP is one integration surface, not GATE's definition.
The differentiator is not multi-hop alone. It is the combination of live upstream revocation, alternate-path preservation, federated issuer state, freshness semantics and protocol-neutral effect-time resolution.
Read: docs/POSITIONING.md, docs/INTEGRATION-MODEL.md, docs/RELEASE-BOUNDARY.md.
GATE exposes two separate onboarding paths.
Use the hosted sandbox to learn GATE semantics on a synthetic authority graph:
https://gate-phi-eosin.vercel.app/quickstart.html
Temporary key: 7 days. Quota: 500 verifications/project/day.
Canonical endpoint:
https://ufqtoyakmrddqytrkcje.supabase.co/functions/v1/gate-network
Current Free Developer Preview: 50,000 verifications/month, 1 authority issuer, bounded consistency. Strict consistency is not included.
Use GateClient from @gate-avn/sdk. See docs/QUICKSTART.md for the complete live-network flow.
Requirements: Node.js 20+.
npm install
npm test npm run demo
The demo calls the public SDK shape:
import { GateClient } from './packages/sdk/dist/index.js';
const gate = new GateClient({ endpoint: process.env.GATE_URL });
const result = await gate.verify({ principal: 'user:jerome', actor: 'agent:C@company-c', action: { protocol: 'mcp', name: 'delete_customer_data', resource: 'customer:3456' }, consistency: 'bounded', maxStalenessMs: 200 });
if (result.decision !== 'ALLOW') throw new Error(result.reason);
GATE answers a deliberately narrow question: whether the actor still has at least one live delegation path from the principal, according to sufficiently fresh external authority state.
The public contract separates authority state from application policy. A credential can remain syntactically valid while GATE returns INVALID or UNKNOWN because the authority behind it is no longer live or cannot be established with the requested freshness.
It can return:
VALID / ALLOW — at least one live authority path exists.INVALID / DENY — the known paths are revoked/invalid.UNKNOWN / DENY — freshness or availability is insufficient for the requested consistency contract.GATE is not your business-policy PDP. The action object is carried for integration/audit context in this preview; policy such as "may this principal delete customer 3456?" belongs in AuthZEN, Cedar, OPA, Permit, Cerbos, OpenFGA, or your existing authorization system.
GATE is also not trying to replace OAuth, MCP, A2A, OpenID Federation, Security Event Tokens, Shared Signals, an IdP, or an API/AI gateway. The intended role is to sit underneath/alongside them as a live authority-state resolver.
The Developer Preview does not claim a portable cryptographically signed authority proof. It returns a live resolution result; a signed GATE receipt is a possible future layer, not a current release promise.
A local verifier can validate signatures, expiry, scopes and token chains. It cannot independently know every external issuer's current revocation state, trust changes, alternate delegation paths, or freshness across domains. GATE's hypothesis is that the defensible value is the shared, low-latency state network — not a secret verification algorithm.
bounded: live verification from the canonical primary on v7, with a bounded primary-read snapshot age; regional replicas are not yet deployed.strict: canonical primary-read verification available only to eligible plans; not synchronous confirmation of external issuer systems.packages/sdk/ public developer-facing client
examples/ minimal SDK demonstration services/ experimental control plane / edge / trust services src/ PoC verification primitives mcp/ MCP enforcement harness test/ SDK + distributed consistency tests docs/ architecture, integration contract, due diligence
npm install @gate-avn/sdk@0.1.0-dev.4
Repository Stage 16 baseline: 0.1.0-dev.4
Published SDK version used by the trial: 0.1.0-dev.4.
npm install @gate-avn/mcp@0.1.0-dev.9
Repository Stage 16 baseline: 0.1.0-dev.8
Published npm @dev: 0.1.0-dev.9; @latest remains 0.1.0-dev.2 (public registry checked 2026-11-02). Pin the trial version explicitly.
The current repository CLI descriptions differ from the published dev.9 archive after PR #24. The trial installs from npm and does not substitute workspace code. Glama indexing and npm publication are separate: discovery is not proof of an independent successful integration.
Official MCP Registry:
io.github.Projetxana/gate-authority-network
GATE is publicly available as a Developer Preview on npm and in the Official MCP Registry.
The SDK and MCP server are currently installable from the public npm registry. The MCP server is also discoverable through the Official MCP Registry.
The HTTP, x402, AuthZEN, A2A, AP2 and SSF adapters exist in the Stage 16 repository baseline but are not yet published as public npm packages.
This remains experimental Developer Preview software and is not production-ready.
Read next: docs/STAGE17D-EXTERNAL-VALIDATION.md, docs/STAGE17E-FREE-PAID-CONTINUITY.md, docs/DUE-DILIGENCE-2026-10-02.md and docs/PUBLIC-VALIDATION-PLAN.md.
Apache-2.0. This repository is intended to make the verification logic easy to inspect and challenge; the long-term product hypothesis is the shared live authority network, not proprietary verifier code.