Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Descripción del creador (original en inglés)
Live cross-domain authority-state resolution for delegated agents through MCP.
Estos tres nunca se combinan en una sola puntuación: las opiniones, las mediciones y la popularidad son cosas distintas.
Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.
Elige la app de IA que usas y copia la configuración.
GATE_URL, GATE_API_KEYLos valores marcados como secretos son llaves de tu cuenta. Nunca los compartas ni los pegues en un chat.
Necesitas
¿Qué app usas?
Elige tu app arriba. La recordamos, así que la próxima vez el botón dirá “Instalar en …”.
Abre Claude Desktop → Settings → Developer → Edit Config y pega esto en 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"
}
}
}
}Ejecuta esto en tu terminal
claude mcp add gate-authority-network --env GATE_URL=your-value --env GATE_API_KEY=your-value -- npx -y @gate-avn/mcpCompleta los valores vacíos antes de ejecutarlo.
Pégalo en .cursor/mcp.json de tu proyecto, o en ~/.cursor/mcp.json
{
"mcpServers": {
"gate-authority-network": {
"command": "npx",
"args": [
"-y",
"@gate-avn/mcp"
],
"env": {
"GATE_URL": "your-value",
"GATE_API_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Pégalo en .vscode/mcp.json de tu proyecto
{
"servers": {
"gate-authority-network": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@gate-avn/mcp"
],
"env": {
"GATE_URL": "your-value",
"GATE_API_KEY": "your-value"
}
}
}
}Tu navegador te pide permiso para abrir la app; luego la app muestra la configuración y te pide confirmar. Los valores de las claves quedan vacíos para que los completes tú.
Este se ejecuta en tu computadora, y ChatGPT solo puede conectarse a servidores en internet. Elige otra app.
Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.
Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.
Se ejecuta en tu computadora; la lista de herramientas aparece en tu app de IA después de instalarlo.
Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 7 nov 2026
El nombre en el registro se verificó con la cuenta de GitHub Projetxana, dueña del repo
Todavía no hemos leído este repo en GitHub
Todavía no hemos leído este repo en GitHub
Este se ejecuta en tu computadora; no hay endpoint en internet
Se ejecuta en tu computadora y usa ajustes locales en su lugar
Se ejecuta en tu computadora; solo podemos leer listas de herramientas de endpoints en internet
Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.
Superó 1 de 1 revisiones básicas aplicables. No hemos leído el código. Antes de agregar una clave o un token, revisa qué acceso pide el servidor y usa una clave que tenga solo los permisos que necesitas.
Debes completar: GATE_URL, GATE_API_KEY
Se ejecuta en tu computadora. Tu app de IA lo inicia cuando hace falta, y los datos no pasan por los servidores del creador (a menos que el propio servidor llame a un servicio en línea).
El repo de GitHub cambió por última vez –, y la última versión (0.1.0-dev.8) llegó al registro hace 10 días.
Las apps compatibles con MCP, como Claude Desktop, Claude Code, Cursor y VS Code. También necesitas Node.js en tu computadora.
En la misma categoría: Spec Driven Development, Remote Desktop Commander, Dialyne
Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.
Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi
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.
Real phone calls in France for AI agents: dial +33 numbers, menus, hold, AI disclosure.
Copiado tal cual del repo del creador. PopNx MCP no lo ha revisado ni lo respalda. Se quitaron HTML, imágenes y scripts. Los enlaces llevan fuera de este sitio.
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.