convez.ai
MCP ServerSegurançaIntermediário
fipsign

FIPSign MCP — Assinatura Pós-Quântica

fipsign/fipsign-mcp

Assinatura digital pós-quântica conforme NIST FIPS 204 para Claude

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que integra assinatura digital pós-quântica via ML-DSA-65 (NIST FIPS 204) ao Claude e agentes compatíveis. Permite assinar payloads, verificar tokens, emitir e revogar certificados, e gerenciar uso sem escrever código.

Instalação

$npx convez-ai fipsign/fipsign-mcp

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
50%
Último commit
há 4 meses
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Assinar documentos e payloads com criptografia resistente a computadores quânticos
  • Emitir e revogar certificados digitais pós-quânticos
  • Verificar integridade e autenticidade de tokens assinados

Veredito

MCP bem estruturado e maduro para casos reais de criptografia pós-quântica. Documentação clara com três níveis de teste (Inspector, local, produção) reduz atrito. Ideal para quem precisa de assinatura FIPS 204 integrada a workflows com Claude.

README

A tradução para o português deste README ainda está na fila.

@fipsign/mcp

npm License: MIT NIST FIPS 204

MCP server for FIPSign — post-quantum digital signing via ML-DSA-65 (NIST FIPS 204).

Gives Claude Desktop, Claude Code, and any MCP-compatible AI agent full access to the FIPSign API without writing code: sign payloads, verify tokens, issue and revoke post-quantum certificates, and monitor usage.


Tools

ToolDescriptionToken cost
fipsign_healthCheck service statusfree
fipsign_public_keyGet the server's ML-DSA-65 public keyfree
fipsign_signSign any payload1 token
fipsign_verifyVerify a signed token1 token
fipsign_revokePermanently revoke a token1 token
fipsign_usageGet token balance and usage historyfree
fipsign_generate_key_pairGenerate an ML-DSA-65 key pair locallyfree
fipsign_ca_issueIssue a post-quantum certificate1 token
fipsign_ca_revoke_certRevoke a certificate1 token
fipsign_ca_get_certGet certificate status by IDfree
fipsign_ca_get_crlGet the Certificate Revocation Listfree

Prerequisites

  1. Node.js 18 or later
  2. A FIPSign account and API key — create one free at app.fipsign.dev
  3. For CA tools: a CA created inside your project from the dashboard

Local testing before publishing

Level 1 — MCP Inspector (no Claude Desktop required)

The Inspector opens a browser UI where you can call each tool manually and inspect responses without Claude Desktop.

git clone https://github.com/fipsign/fipsign-mcp
cd fipsign-mcp
npm install
npm run build
export FIPSIGN_API_KEY=pqa_your_real_key
npx @modelcontextprotocol/inspector node dist/index.js

Open the URL shown in the terminal (typically http://localhost:5173). Select a tool, fill in the parameters, and run it.

Level 2 — Claude Desktop with local code (without publishing to npm)

Build first, then point Claude Desktop at the local dist/index.js:

npm run build

Add to your claude_desktop_config.json (see path below):

{
  "mcpServers": {
    "fipsign": {
      "command": "node",
      "args": ["/absolute/path/to/fipsign-mcp/dist/index.js"],
      "env": {
        "FIPSIGN_API_KEY": "pqa_your_real_key"
      }
    }
  }
}

Level 3 — Claude Desktop with published package (production)

{
  "mcpServers": {
    "fipsign": {
      "command": "npx",
      "args": ["-y", "@fipsign/mcp"],
      "env": {
        "FIPSIGN_API_KEY": "pqa_your_real_key"
      }
    }
  }
}

Installation for Claude Desktop

claude_desktop_config.json is located at:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
  • Linux: ~/.config/Claude/claude_desktop_config.json

Add the fipsign entry inside mcpServers (create the file if it doesn't exist):

{
  "mcpServers": {
    "fipsign": {
      "command": "npx",
      "args": ["-y", "@fipsign/mcp"],
      "env": {
        "FIPSIGN_API_KEY": "pqa_your_real_key"
      }
    }
  }
}

Restart Claude Desktop after editing the config. You should see the FIPSign tools available in the tools panel.


Installation for Claude Code

claude mcp add fipsign -- env FIPSIGN_API_KEY=pqa_your_real_key npx -y @fipsign/mcp

Or manually in your project's .claude/mcp.json:

{
  "mcpServers": {
    "fipsign": {
      "command": "npx",
      "args": ["-y", "@fipsign/mcp"],
      "env": {
        "FIPSIGN_API_KEY": "pqa_your_real_key"
      }
    }
  }
}

Environment variables

VariableRequiredDefaultDescription
FIPSIGN_API_KEYYes (for most tools)—Your FIPSign API key. Format: pqa_ + 64 lowercase hex chars. Get one at app.fipsign.dev.
FIPSIGN_BASE_URLNohttps://api.fipsign.devOverride API base URL (useful for self-hosted instances or local dev).

fipsign_health, fipsign_public_key, and fipsign_generate_key_pair work without an API key.


Usage examples

Once configured, you can ask Claude:

Signing:

  • "Sign a token for user_123 with role admin that expires in 1 hour"
  • "Verify this token: { payload: '...', signature: '...', algorithm: 'ML-DSA-65', issuedAt: 123 }"
  • "Revoke this token because the user logged out"

Certificates:

  • "Generate a key pair for a new IoT device"
  • "Issue a certificate for device-serial-00123 using the public key I just generated, valid for 1 year"
  • "Check the revocation status of cert_abc123"
  • "Get the full CRL for our CA"
  • "Revoke certificate cert_abc123 — device was reported stolen"

Monitoring:

  • "How many tokens do I have left this month?"

Publishing to npm

npm run build
npm publish --access public

Requires an npm account with publish rights to the @fipsign scope.


Links

Ver o original no GitHub

Bom para

Relacionados