Vaspera Hardening MCP server

Read from the package source without running it. The installed server may list more.

• agent_complete

  Signal that an agent has completed its validation run. Must include summary with findings count and confidence score.

• agent_cross_verify

  Cross-verify a finding from another agent. Increases or decreases confidence based on verification.

• agent_submit_findingwrite action

  Submit a finding from a validation agent during certification. Each finding must have a unique ID, severity, and evidence.

• autofix_apply

  Apply an automatic fix for a certification finding. Use autofix_preview first to see what will change.

• autofix_list_patterns

  List all available auto-fix patterns that can be applied to findings.

• autofix_preview

  Preview an automatic fix for a certification finding without applying it. Returns the before/after diff.

• certification_consensus

  Calculate consensus score and certification level from all agent findings. Requires all requested agents to have completed. Set auto_cross_verify: true (default) to automatically cross-verify critical findings if blocked.

• certification_cross_verify

  Batch cross-verify critical findings. In "auto" mode (default), automatically verifies all critical findings based on agent domain overlap. In "manual" mode, verifies only specified finding IDs. Run this after all agents complete to unblock consensus calculation.

• certification_dashboard

  Portfolio-wide view of enterprise certifications across all projects. Shows certification status, levels, and expiry.

• certification_export_sarif

  Export certification findings to SARIF format for GitHub Security, SonarQube, or other tools.

• certification_filter

  Filter certification findings by severity, agent, category, file, or confidence level.

• certification_finalize

  Finalize certification and generate CERTIFICATION.md and CERTIFICATION.json artifacts.

• certification_start

  Initialize an enterprise certification process for a project. Creates certification directory and metadata. Returns certification ID for tracking.

• certification_status

  Check the current status of a certification process including which agents have completed.

• certification_summary

  Get a progressive disclosure summary of certification findings grouped by severity, agent, file, and category.

• hardening_dashboard

  Compare production readiness across all Vaspera projects. Shows which projects have been audited, their readiness scores, issue counts, and what phases have been completed. Use to prioritize which project to harden next.

• hardening_get_command

  Retrieve the full prompt text for a specific hardening command. Use this to execute a hardening phase against a project. Available commands: audit, fix-critical, fix-high, fix-medium, fix-rls, add-tests, verify, harden.

• hardening_install

  Install the production hardening slash commands into a project's .claude/commands/ directory. After installation, Claude Code can use /audit, /fix-critical, /fix-high, /fix-medium, /fix-rls, /add-tests, /verify, and /harden in that project.

• hardening_install_all

  Install hardening slash commands into every discovered project in the workspace. Scans the base directory, finds all projects, and installs commands to each one. Defaults to dry-run mode for safety - set dry_run: false to apply changes.

• hardening_list_commands

  List all available production hardening commands with their descriptions. Use to understand what commands are available and what order to run them.

• hardening_list_projects

  Discover all projects in the Vaspera workspace directory. Returns project names, paths, and whether hardening commands are already installed. Set VASPERA_PROJECTS_DIR env var to override the default directory (~/Documents/GitHub).

• hardening_read_audit

  Read the AUDIT.md file from a project. Returns the full audit content including severity counts and readiness score. Use after running /audit in a project.

• hardening_read_report

  Read the HARDENING-REPORT.md from a project. Contains the before/after comparison and deployment checklist. Available after running /verify.

• redteam_challenge

  Red team challenges an area marked clean by another agent. Used to dispute false negatives.

• rules_check_filewrite action

  Run custom rules against a specific file and return matches.

• rules_generate_config

  Generate a sample .vaspera/hardening-rules.yaml configuration file.

• rules_load

  Load custom validation rules from .vaspera/hardening-rules.yaml or .json

• rules_templates

  List built-in rule templates that can be used in custom rule configuration.

• Code scan132 source files scanned20/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancerepository not readable: repo not found3/15
• Maintainer identityno repository or website to verify2/10

Vaspera Hardening: common questions

Is Vaspera Hardening MCP server safe?

With care: it is graded C, so read the findings first (57/100). Read the Vaspera Hardening safety report

How do I install Vaspera Hardening?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Vaspera Hardening need an API key?

No secret keys are declared. It reads 1 setting from the environment.

Is Vaspera Hardening maintained?

The latest release is v1.0.2.

What can I use instead of Vaspera Hardening?

Servers from other publishers that do the same job: Claude Prompts MCP server, Image MCP server and Shellward MCP server. Compare all Vaspera Hardening alternatives.