Bragproof

← Reports

@greenarmor/ges-mcp-server

Starts with no setup1.6.9npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Returns a result when called with no setup: 5 of 5 tools tried
Contacts while installing and starting: nothing

47tools listed
0hosts contacted
0files written
0.1 sto start
13dependencies

What it contacted

Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.

Starting it

npx -y @greenarmor/ges-mcp-server@1.6.9

Installing a package runs its code. Use a sandbox for anything you have not read.

Calling its tools

5 tools that take no input and look read-only were called once with nothing. 5 returned a result.

check_project_statusReturned a result under 0.1 s · 75 characters
list_missing_controlsReturned a result under 0.1 s · 8,274 characters
list_framework_controlsReturned a result under 0.1 s · 2,106 characters
get_scoreReturned a result under 0.1 s · 75 characters
policy_listReturned a result under 0.1 s · 4,874 characters

During the calls it contacted nothing it had not already contacted.

Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

check_compliance project_type
Check GDPR compliance status for a project. Returns compliance scores per framework (GDPR, OWASP, CIS, NIST) with grades and control breakdown.
check_project_status project_path
Read the actual project's .ges/ directory to get real-time compliance status, scores, config, and audit results. Use this when the project has already been initialized with 'ges init'.
list_missing_controls project_type, framework
Show missing or failed compliance controls for a given framework. Returns control ID, severity, name, and implementation guidance.
list_framework_controls framework, status_filter
List all controls for a given framework with their status, severity, category, and implementation guidance. Useful for understanding the full control landscape.
run_audit project_path
Run a full source code security audit on the project. Scans for secrets, weak cryptography, injection vulnerabilities, auth issues, config problems, and database anti-patterns. Returns findings with severity, file location, evidence, and fix guidance.
42 more tools
generate_compliance_report project_type, project_name, frameworks
Generate a full compliance report with executive summary, findings, framework scores, risk assessment, security controls, and actionable recommendations. The primary report tool for compliance status.
generate_audit_report project_path, project_name
Generate a report from actual source code audit findings. Combines audit results with compliance scoring and detailed recommendations for each finding. Requires a project path.
fix_recommendation control_id, finding_title
Get detailed step-by-step remediation guidance for a specific control or finding. Provides implementation steps, code examples, and verification steps. Use this to fix issues one by one.
generate_retention_policy project_name
Generate a data retention policy template
generate_incident_response project_name
Generate an incident response plan template
generate_risk_assessment project_name
Generate a risk assessment template
generate_dpa project_name
Generate a Data Processing Agreement template
generate_data_inventory project_name, project_type
Generate a data inventory document listing data categories, classifications, retention periods, and legal basis. Required for GDPR Article 30 compliance.
generate_processing_records project_name, controller_name
Generate Article 30 Records of Processing Activities (ROPA). Documents all processing activities, purposes, data categories, recipients, and retention periods.
auto_fix project_path, dry_run, rule_ids
Run an audit and automatically fix all fixable security/compliance issues in the project source code. Creates files, modifies source, generates security scaffolding. Returns a detailed report of what was fixed and what requires manual review.
apply_control_override project_path, control_id, status, reason
Mark a compliance control as not-applicable. AI assistants CANNOT mark controls as 'pass' — that must be verified by the GESF audit engine (run_audit). Use 'not-applicable' only when a control genuinely does not apply to the project. A detailed reason is required.
implement_control project_path, control_id
Generate and write actual implementation files for a compliance control into the target project. Creates source files, configuration, and middleware. Returns what was created and next steps.
generate_badge project_path, output, readme
Generate an SVG compliance score badge for a project's README. Reads the project's .ges/score.json and produces a shields.io-style SVG badge with the compliance score and grade. Optionally injects into README.md.
get_score project_path
Read and display the compliance score from a project's .ges/score.json. Shows per-framework scores, grades, and overall compliance percentage.
init_project project_path, project_name, project_type, frameworks, country, additional_packs, force
Initialize GESF in a project directory. Creates the .ges/ directory structure, compliance/security documentation, controls, CI/CD workflows, and configuration files. Automatically installs the privacy pack for the specified country of origin.
suggest_packs project_path, country, project_type
Analyze the project and recommend which privacy/compliance policy packs to install. Examines project type, country of origin, installed packs, codebase patterns (dependencies, file structure), and data processing indicators. Returns ranked recommendations with rationale. Does NOT install packs — use policy_install to act on suggestions.
run_scans project_path
Run security scanner integrations on a project. Detects the ecosystem (Node.js, Python, etc.) and runs available scanners (npm audit, Trivy, Gitleaks, Semgrep, etc.) plus SBOM generation.
doctor project_path
Diagnose GESF project health. Checks if the project is initialized, config files exist, score is available, required directories are present, and GitHub Actions are configured.
validate_project project_path
Validate GESF project configuration and controls. Checks config.json against the schema, validates control files, and verifies required directories exist.
policy_list
List all available policy packs with their IDs, names, control counts, and supported project types.
policy_install project_path, pack_id
Install a policy pack into a project. Writes the pack's controls as a JSON file in the controls/ directory.
policy_remove project_path, pack_id
Remove an installed policy pack from a project. Deletes the pack's directory from controls/.
update_check
Check the current GESF version and get update instructions.
install_hooks project_path, action
Install GESF git hooks (pre-commit) that run compliance checks before allowing commits. Also supports uninstalling hooks.
start_dashboard project_path, port, host
Get instructions and configuration for starting the GESF compliance web dashboard. The dashboard provides a browser-based view of compliance status, scores, and findings. Note: the actual server must be started via the CLI 'ges dashboard' command.
record_recommendation project_path, category, title, description, severity, affected_controls, affected_files, suggested_action
Record a recommendation or observation to .dev-logs/ai-recommendations/ for the GESF development team. Use this when you identify a potential improvement, weakness, or best-practice suggestion. Recommendations are NOT applied automatically — they are logged for human developers to review. This is the correct way to surface ideas instead of overriding controls.
create_governance_record project_path, system_name, system_type, system_description, system_version, risk_level, created_by, actor_name, actor_role
Create a new governance provenance record for an AI system, application, data process, or model. Establishes the root of the approval provenance chain (System → Risk → Policy → Approval → Evidence → Review). The record starts in 'draft' status — use approve_governance_record to record an approval decision and add_governance_evidence to attach supporting evidence.
approve_governance_record project_path, record_id, approver_name, approver_role, approver_email, approval_authority, decision, valid_from, valid_until, conditions, rationale, actor_name, actor_role
Record an approval decision on a governance record. Captures who approved the system, under what authority, when, the validity period, and any conditions. This is a critical link in the provenance chain — it answers 'Who approved this AI system? Under which authority? When? Is it still valid?'
add_governance_evidence project_path, record_id, title, type, source_system, reference, location_description, added_by, actor_name, actor_role
Add an evidence reference to a governance record. Evidence references point to supporting documentation in external systems (Jira, Confluence, ServiceNow, SharePoint, GRC platforms, etc.) WITHOUT duplicating their content. This maintains a single source of truth while providing a unified governance view. Each evidence entry answers 'What evidence exists to support the decision?'
list_governance_records project_path
List all governance provenance records in a project. Returns a summary of each record including system name, status, risk level, approval status, and evidence count. Use this to see all governed systems and their current compliance state.
get_governance_record project_path, record_id
Get the full provenance chain for a single governance record. Returns all linked dimensions: system identity, risk assessment, policy basis, approval decision, committee approval, evidence chain, review cycle, data inventory, and compliance links. This provides the complete 'single defensible answer' for auditors — the full chain from AI System → Risk Assessment → Policy → Approval → Evidence → Review Cycle.
verify_governance_record project_path, record_id
Verify the provenance chain completeness of a governance record. Checks all dimensions: approval exists and is not expired, risk assessment present, evidence attached, review cycle defined, data inventory complete. Returns a verification result with completeness checklist, blocking issues, warnings, and approval expiry status. This is the 'single defensible answer' function for auditors.
set_governance_risk_assessment project_path, record_id, assessor, methodology, risk_score, residual_risk, identified_risks, mitigation_measures, actor_name, actor_role
Link a risk assessment to a governance record. Captures assessor, methodology, risk score, identified risks, residual risk, and mitigation measures. This is a required dimension for provenance chain completeness — without it, verification will report a blocking issue.
set_governance_policy_basis project_path, record_id, policy_id, policy_name, version, standard, clauses, actor_name, actor_role
Document the policy or standard under which a system is approved. Captures policy ID, name, version, applicable clauses, and the standard reference. This provides the regulatory basis for the approval decision.
set_governance_review_cycle project_path, record_id, frequency, next_review, actor_name, actor_role
Set up a periodic review cycle for a governance record. Defines how often the approval must be re-reviewed and when the next review is due. Enables continuous compliance monitoring.
set_governance_data_inventory project_path, record_id, personal_data_categories, processing_purposes, data_subjects, cross_border_transfers, retention_period, actor_name, actor_role
Document the data inventory for a governance record. Captures personal data categories, processing purposes, data subjects, cross-border transfers, and retention period.
set_governance_committee project_path, record_id, committee_name, meeting_date, meeting_reference, attendees, decision_summary, actor_name, actor_role
Record committee approval details for a governance record. Captures committee name, meeting date, meeting reference, attendees, and decision summary.
set_governance_compliance_links project_path, record_id, frameworks, controls_satisfied, control_pack_ids, actor_name, actor_role
Map compliance frameworks and controls to a governance record. Links the record to GDPR, OWASP, CIS, NIST, etc., and references which controls are satisfied by this system's governance.
assign_fix_to_governance project_path, finding_key, finding_rule_id, finding_title, finding_file, finding_line, finding_severity, finding_control_ids, governance_record_id, assignee, assignee_role, notes, actor_name, actor_role
Assign a pending audit finding (fix) to an existing governance provenance record. Creates a traceable link between a specific security finding and the governance chain (who approved the system, under what policy, what risk assessment supports it). Requires a finding_key (ruleId:file:line), governance record ID, and assignee name.
list_fix_assignments project_path, governance_record_id
List all fix assignments linking pending audit findings to governance provenance records. Shows which fixes are assigned, to whom, linked to which governance record, and their status (assigned, in-progress, fixed, verified).
resolve_fix_assignment project_path, finding_key, resolved_by, resolved_by_role, method, resolution_notes, actor_name, actor_role
Resolve (mark as fixed) a fix assignment that was linked to a governance record. Records who resolved it, the method used (auto-fix, manual, not-applicable), and resolution notes. Updates the provenance chain to show the fix has been addressed.
run_inference project_path
Run AI-powered inference on GESF compliance data. Analyzes audit findings (clustering + deduplication), identifies root causes via graph analysis, detects score anomalies, and predicts compliance trends. Returns a comprehensive InferenceReport with actionable insights.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=20.0.0
Sourcegithub.com/greenarmor/gesf
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-EbSogkrB9XbKSf+ZnoxYciV1RKyAUV2L/NxjPp/S8IukK7LKr8tqygi3DTGCaG28D1xklVBgGFYaDHVl08mDCQ==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@greenarmor/ges-mcp-server.svg)](https://bragproof.smaverk.com/r/%40greenarmor/ges-mcp-server)

New version out? Ask for a fresh report.