Vaspera Hardening

io.github.RCOLKITTPublished by GitHub account RCOLKITTv1.0.2Updated Oct 24, 2026

Enterprise certification for codebases with multi-agent security, reliability, and quality audits

The publisher's own server: Accountingqb

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local MCP server that runs multi-agent security, reliability and quality audits to certify codebases.

What you can do
  • Run multi-agent audits over a codebase covering security, reliability and quality.
  • Produce certification-style findings for the projects it scans.
  • Scan projects found under a configured base directory.
  • The listing gives no individual tool names, so exact operations are not documented.
When to use it
Consider it when you want an assistant to review local projects for security, reliability and quality issues and report certification-style results, rather than for day-to-day coding or Git tasks.
Requirements
Runs as a local stdio process installed from the npm package vaspera-hardening-mcp-server, so Node.js is needed. The environment variable VASPERA_PROJECTS_DIR sets the base directory to scan and defaults to ~/Documents/GitHub. Desktop client only; no authentication is declared.
Before you install
It reads project source code from the configured directory, so point VASPERA_PROJECTS_DIR only at folders you are comfortable exposing to the assistant. The listing does not say whether findings or code leave the machine, and no tool list is published, so review what it actually does before running it on sensitive repositories.

Installation

In SourceWeft

  1. Open Vaspera Hardening in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Accountingqb integrations