feat: add GateTest — 91-module code quality MCP server

[ccantynz-alt]

Summary

Adds GateTest to the registry — an MCP server that exposes a 91-module static-analysis engine directly to Claude Code and any MCP-compatible AI.

npm package: @gatetest/mcp-server@1.0.0
Homepage: https://gatetest.ai
Repository: https://github.com/crclabs-hq/gatetest

Install

claude mcp add gatetest -- npx -y @gatetest/mcp-server

Tools (9 total)

Tool	Description
scan_local	Scan a local directory with GateTest's 91-module engine
run_module	Run a single named module (e.g. secrets, tlsSecurity)
list_modules	Enumerate all 91 modules with descriptions
check_health	Verify engine is loaded and operational
fix_issue	AI-driven auto-fix for a single finding (needs ANTHROPIC_API_KEY)
compose_pr	Render PR body markdown for a batch of fixes
explain_finding	Nuclear-tier per-finding Claude diagnosis (needs ANTHROPIC_API_KEY)
audit_log	Query local scan history from the memory store
compare_repos	Pattern summary across scan history

What GateTest covers

91 modules across security (secrets, TLS bypass, SSRF, SQL injection, cookie security), reliability (race conditions, resource leaks, retry hygiene, async iteration bugs), code quality (import cycles, dead code, money-float, datetime bugs), infrastructure (Terraform, Kubernetes, Dockerfile, CI security), and AI safety (prompt injection, bundled API keys, deprecated models).

Notes

• Transport: stdio
• ANTHROPIC_API_KEY is optional — all scan/list/health tools work without it; fix and diagnosis tools require it
• The mcpName field (io.github.ccantynz-alt/gatetest) is set in package.json for ownership verification

[rdimitrov]

Hi @ccantynz-alt 👋 — thanks for your interest in the MCP Registry!

It looks like this PR is trying to publish an MCP server by adding or editing files in this repository (under servers/ or in data/seed.json). That isn't how servers get published, so I'm closing this PR automatically.

Servers are published with the mcp-publisher CLI, not by opening a pull request against this repo. The CLI verifies that you own your namespace and submits your server.json directly to the live registry API.

To publish your server, follow the Publishing Quickstart. In short:

# Build the publisher CLI
make publisher

# Authenticate (e.g. via GitHub) and publish your server.json
./bin/mcp-publisher login github
./bin/mcp-publisher publish

Note: data/seed.json is seed data for local development only — adding entries there does not publish anything to the registry.

If you believe this was closed in error, please leave a comment and a maintainer will take a look. 🙇

This is an automated message.