Skip to main content
Glama
cloudcwfranck

@cloudcraftwithfranck/govcloud-mcp

signing_config

Create artifact signing and verification configuration using Sigstore, Notary v2, or DoD PKI. Returns pipeline integration code, Kubernetes admission webhook config, and verification commands.

Instructions

Generate complete artifact signing and verification configuration using Sigstore/Cosign, Notary v2, or DoD PKI. Returns pipeline integration code, Kubernetes admission webhook config, and verification commands.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
signingMethodYesSigning method to configure
pipelineTypeYesPipeline type to generate signing steps for
registryNoContainer registry URL (default: registry1.dso.mil)
enforceInClusterNoGenerate Kubernetes admission controller config to enforce signed images (default: true)

Implementation Reference

  • The main implementation file for the signing_config tool. Contains the tool definition (signingConfigTool with name, description, inputSchema), the Zod validation schema, and the handleSigningConfig async function that calls the Anthropic API with a detailed prompt to generate artifact signing configuration (Cosign, Notary v2, DoD PKI) for various pipeline types (GitLab CI, GitHub Actions, Tekton, Jenkins).
    import { z } from 'zod';
    import { anthropic, MODEL } from '../../client.js';
    import { PIPELINE_SYSTEM } from '../../prompts/system-prompts.js';
    import { runTool, getTokenBudget } from '../../utils/tool-runner.js';
    
    export const signingConfigTool = {
      name: 'signing_config',
      description:
        'Generate complete artifact signing and verification configuration using Sigstore/Cosign, Notary v2, or DoD PKI. Returns pipeline integration code, Kubernetes admission webhook config, and verification commands.',
      inputSchema: {
        type: 'object' as const,
        properties: {
          signingMethod: {
            type: 'string',
            enum: ['cosign-keyless', 'cosign-key', 'notary-v2', 'dod-pki'],
            description: 'Signing method to configure',
          },
          pipelineType: {
            type: 'string',
            enum: ['gitlab-ci', 'github-actions', 'tekton', 'jenkins'],
            description: 'Pipeline type to generate signing steps for',
          },
          registry: {
            type: 'string',
            description: 'Container registry URL (default: registry1.dso.mil)',
          },
          enforceInCluster: {
            type: 'boolean',
            description: 'Generate Kubernetes admission controller config to enforce signed images (default: true)',
          },
        },
        required: ['signingMethod', 'pipelineType'],
      },
    };
    
    const Schema = z.object({
      signingMethod: z.enum(['cosign-keyless', 'cosign-key', 'notary-v2', 'dod-pki']),
      pipelineType: z.enum(['gitlab-ci', 'github-actions', 'tekton', 'jenkins']),
      registry: z.string().max(500).default('registry1.dso.mil'),
      enforceInCluster: z.boolean().default(true),
    });
    
    export async function handleSigningConfig(args: unknown): Promise<string> {
      return runTool('signing_config', args, Schema, async ({ signingMethod, pipelineType, registry, enforceInCluster }) => {
        const response = await anthropic.messages.create({
          model: MODEL,
          max_tokens: getTokenBudget('signing_config'),
          system: PIPELINE_SYSTEM,
          messages: [
            {
              role: 'user',
              content: `Generate complete artifact signing configuration using **${signingMethod}** for **${pipelineType}** pipelines targeting registry **${registry}**.
    ${enforceInCluster ? '\nAlso generate Kubernetes admission controller configuration to enforce signed images cluster-wide.' : ''}
    
    Provide:
    1. **Setup Instructions** — one-time configuration steps:
       - Key generation (for key-based methods)
       - Fulcio/Rekor integration (for keyless)
       - DoD PKI certificate configuration (if dod-pki)
       - Kubernetes Secret for signing keys
    
    2. **Pipeline Signing Stage** — complete ${pipelineType} YAML block to add:
       \`\`\`yaml
       # Sign image after push
       sign-image:
         ...
       \`\`\`
    
    3. **SBOM Generation** — integrate Syft SBOM generation and signing:
       - Generate SBOM in SPDX/CycloneDX format
       - Attach signed SBOM as OCI artifact
    
    4. **Verification Commands**:
       \`\`\`bash
       # Verify image signature
       cosign verify ...
       # Verify SBOM
       cosign verify-attestation ...
       \`\`\`
    
    ${enforceInCluster ? `5. **Kubernetes Admission Enforcement**:
       - Kyverno ClusterPolicy to require signed images from ${registry}
       - OR Gatekeeper OPA constraint
       - Test admission policy with signed vs unsigned image
       - Exemptions for system namespaces` : ''}
    
    6. **Transparency Log** — how signatures are recorded in Rekor and how to query:
       \`\`\`bash
       rekor-cli search --email ...
       \`\`\`
    
    7. **DoD Compliance Rationale** — which NIST 800-53 / CISA controls this satisfies (SA-10, SI-7, CM-14)
    
    8. **Iron Bank Verification** — how to verify Iron Bank images specifically with their Cosign public key
    
    Use production-ready commands with actual Sigstore endpoints and realistic key formats.`,
            },
          ],
        });
    
        return response.content[0].type === 'text' ? response.content[0].text : '';
      });
    }
  • Import of signingConfigTool and handleSigningConfig from the signing-config module.
    import { signingConfigTool, handleSigningConfig } from './pipeline/signing-config.js';
  • Registration of signingConfigTool in the allTools array for MCP tool discovery.
    signingConfigTool,
  • Routing in handleToolCall switch-case that dispatches 'signing_config' to handleSigningConfig.
    case 'signing_config':        return handleSigningConfig(args);
  • Token budget configuration: signing_config is allocated 2048 max_tokens.
    signing_config: 2048,
  • Timeout configuration: signing_config has a 20-second (20000ms) execution timeout.
    signing_config: 20000,
  • Minimum response length validation: signing_config requires at least 300 characters in the response.
    signing_config: 300,
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It describes the output (pipeline code, webhook config, commands) but does not disclose side effects, permissions required, or whether the tool is read-only (non-destructive). For a generation tool, this is adequate but could be clearer.

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

Conciseness4/5

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

The description is a single sentence that lists what it does and what it returns. It is concise and front-loaded, though the list of output items could be slightly restructured for clarity.

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 4 parameters (all described), no output schema, and no annotations, the description explains output types but lacks context on return format (e.g., JSON object), authentication requirements for the registry, or handling of default values. Improvements in these areas would raise the score.

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% with descriptions for all 4 parameters. The description adds value by explaining the overall output types but does not add specific meaning to param fields beyond the schema. Baseline 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool generates signing/verification configuration for multiple methods (Sigstore/Cosign, Notary v2, DoD PKI) and returns pipeline code, webhook config, and commands. This is a specific verb+resource that distinguishes it from sibling config tools like addon_configurator or bicep_analyze.

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

Usage Guidelines3/5

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

The description implies usage for generating signing config but provides no explicit guidance on when to use versus alternatives, prerequisites (e.g., having a registry or signing keys), or when not to use. Only the purpose is clear.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/cloudcwfranck/govcloud-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server