Skip to main content
Glama
fort-gate

Fortgate MCP

by fort-gate
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Fortgate MCP

Identidad y KYC de Fortgate en cualquier agente, en menos de 5 minutos.

Fortgate MCP es un servidor MCP que expone la identidad reusable y el KYC de Fortgate como herramientas que un agente (Claude, Cursor, etc.) puede consumir directamente: iniciar un flujo KYC, consultar su estado y verificar una credencial — sin construir la integración a mano.

Este repo es parte del ecosistema GrantFox en Stellar: las tareas se abren como issues, y el trabajo mergeado se recompensa con bounties transparentes.

Quickstart

Requisitos: Node.js 20+ y una API key de Fortgate (sandbox para desarrollo).

npx @fortgate/mcp

Configuralo en tu cliente MCP (ejemplo para Claude Desktop / Cursor):

{
  "mcpServers": {
    "fortgate": {
      "command": "npx",
      "args": ["-y", "@fortgate/mcp"],
      "env": {
        "FORTGATE_API_KEY": "tu-api-key-de-sandbox"
      }
    }
  }
}

Variables de entorno disponibles en .env.example.

Related MCP server: QuickContract MCP

Estructura del repo

.
├── .github/
│   ├── ISSUE_TEMPLATE/     ← formularios de issue (Frontend, Fullstack, QA)
│   ├── PULL_REQUEST_TEMPLATE.md
│   └── workflows/          ← ci.yml (PRs) y release.yml (publish a npm)
├── src/
│   ├── index.ts            ← entrypoint del server
│   ├── server.ts           ← registro de tools
│   ├── config.ts           ← carga y valida env vars
│   ├── types.ts            ← tipos compartidos
│   └── tools/              ← una herramienta por archivo
├── test/                   ← tests con Vitest
├── PLAN.md                 ← plan de producto y arquitectura
├── CONTRIBUTING.md         ← cómo tomar una issue y abrir un PR
└── SETUP-CICD.md           ← setup del repo, CI/CD y branch protection

Contribuir

Leé CONTRIBUTING.md. En resumen: elegí una issue ready, hacé fork, trabajá en una rama tipo/issue-descripcion, y abrí un PR contra main. El CI corre lint, typecheck, test y build automáticamente; tienen que estar en verde (más una review) para mergear.

Regla de oro: una herramienta por archivo en src/tools/.

Desarrollo local

npm ci
npm run lint        # ESLint + Prettier
npm run typecheck   # tsc --noEmit
npm test            # Vitest
npm run build       # compila a build/

Licencia

MIT — ver LICENSE.

Available Tools

1 tool
pingB

Comprueba que el server de Fortgate responde.

ParametersJSON Schema
NameRequiredDescriptionDefault
messageNoMensaje opcional a devolver.

TDQS

B3.1/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description must disclose behavioral traits. It only states the basic function without mentioning side effects, error handling, performance implications, or the nature of the response (e.g., success/failure indicators).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of one sentence that front-loads the core purpose. No unnecessary words or details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's simplicity (single optional parameter, no output schema, no siblings), the description provides a minimal but acceptable overview. However, it lacks details on return format, timeout behavior, or what constitutes a failed check, which could hinder an agent's understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds the context that the parameter 'message' is optional and will be returned. This adds some value beyond the schema, though it doesn't explain purpose or constraints of the message.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific action ('Comprueba') and a clear resource ('el server de Fortgate responde'), clearly indicating it checks server responsiveness. No sibling tools exist, so differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool or any alternatives. There is no mention of prerequisites, frequency, or context for invocation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.0
    • First observedping
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

Solo hay una herramienta, por lo que no existe posibilidad de confusión entre herramientas.

Naming Consistency5/5

El nombre 'ping' sigue una convención simple y consistente al ser la única herramienta.

Tool Count1/5

Con solo 1 herramienta, el servidor es extremadamente limitado para el propósito sugerido por el nombre 'Fortgate', que implica un conjunto más amplio de funcionalidades.

Completeness1/5

El servidor carece de cualquier herramienta para interactuar con las funcionalidades reales de Fortgate, ofreciendo solo un ping de verificación de conectividad.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers