Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
codeinspectus_scanA

Run a full local security scan of a path: managed engines (Opengrep SAST, Gitleaks secrets, Trivy SCA/IaC/license), CodeInspectus's offline native Pub SCA, plus AI-code-specific checks (client-side secret exposure, Supabase RLS/inverted-auth, prompt-injection sinks, API-boundary failures, and explicit runtime-control misconfiguration). Returns CWE-keyed findings with fix recommendations, detected repository technologies, explicit native-pack execution counts, compliance tags, and three-state repository evidence for supported runtime controls. Also returns the V3 repository-trust contract with deterministic V3.1 source-integrity evidence for bidi controls, hidden/default-ignorable characters, Unicode tag and variation-selector payloads, and bounded mixed-script confusables. V3.2 additionally audits explicit AI attribution in source/git/media metadata and validates supported local C2PA assets with the official optional Content Authenticity Initiative library. Remote manifests and revocation endpoints are never fetched. Statistical-watermark detection remains explicitly unavailable. Fully offline — zero network egress at scan time. Never writes to your code or repo.

codeinspectus_setupA

Inspect external-engine health and exact platform download sizes, save declined choices, or install selected Opengrep/Gitleaks/Trivy components after explicit confirmation. Plan is offline. Install writes only to ~/.codeinspectus, verifies immutable pins/publisher provenance, and never modifies the target repository.

codeinspectus_rescanA

Re-run a scan after fixes were applied and diff against a prior scan_id (or the most recent scan of the same path). Reports which findings are resolved, which remain, and which were newly introduced, plus fresh technology and native-pack execution coverage. Repository-trust artifacts are diffed separately with fail-closed resolved, remaining, introduced and not-rechecked states. Use this to verify approved fixes. Never writes to your code or repo.

codeinspectus_plan_cleanupA

Create a fresh, read-only V3.3 cleanup plan for exact verified repository-trust artifact IDs. The plan reproduces current evidence, rejects protected, ambiguous, or unsupported records, hashes every preimage, and discloses exact text edits or copy-only media metadata transformations. It never changes the repository.

codeinspectus_apply_cleanupA

Apply one exact ready V3.3 cleanup plan after explicit approval. Requires an exact artifact-ID match and confirmation, creates managed content backups, uses atomic bounded edits, creates new media copies, reruns the same repository-trust validators, and writes a content-free audit log. This modifies selected source files and/or creates named cleaned copies.

codeinspectus_rollback_cleanupA

Restore an applied V3.3 cleanup from its managed checkpoint after explicit confirmation. Rollback refuses to overwrite files or cleaned copies that changed after cleanup.

codeinspectus_compliance_reportA

Produce a per-framework code-level control-coverage view for a prior scan (NIST CSF 2.0, ISO 27001:2022, SOC 2, CIS v8.1, Essential Eight, OWASP Web/LLM). Reports 'X of N code-visible controls have findings' with the code-visible subset as the explicit denominator. This is NOT a compliance audit, certification, or attestation — code-level evidence only.

codeinspectus_explain_findingA

Return a deep explanation and full remediation plan for a single finding id from a prior scan: what the weakness is, why it matters, concrete fix steps, and references.

codeinspectus_generate_sbomA

Generate a CycloneDX or SPDX SBOM for the target project using Trivy plus the first-party offline Pub lockfile inventory, with native Pub fallback when Trivy is unavailable. Writes the SBOM file to the chosen output path and returns its location and component count. Offline.

codeinspectus_list_rulesA

List the active detectors and engine versions, the CodeInspectus detection-database version and date, Trivy vulnerability-DB freshness, bundled Pub advisory-database provenance/freshness, and the custom CodeInspectus AI-code rules and native detector packs currently shipped.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: scan/rescan differ by diff-vs-fresh, cleanup tools form a plan/apply/rollback lifecycle, and the remaining tools target specific outputs (SBOM, compliance, explanation, rules, setup). No two tools overlap in a way that would cause misselection.

Naming Consistency4/5

All names use snake_case with a consistent codeinspectus_ prefix, which is predictable. Minor deviation from a pure verb_noun pattern in compliance_report and setup, but still readable and cohesive.

Tool Count5/5

Ten tools is well-scoped for a security scanning and remediation suite. Each tool earns its place: core scanning, diffing, cleanup lifecycle, SBOM generation, compliance mapping, explanation, rules inspection, and setup.

Completeness4/5

The surface covers the main scan-fix-rescan-cleanup workflow plus SBOM and compliance outputs. Minor gaps exist, such as no explicit tool to list or retrieve past scan metadata beyond rescan diffs, but agents can work around this.

Maintenance

ActivityActive
ResponsivenessResponsive