Coding Standards
AI coding standards that enforce production-grade code with DDD, SOLID, TDD guardrails.
Connector by corbat-tech · GitHub account verified by the MCP Registry
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/corbat-tech-coding-standards
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 7 read · 0 write · 0 deleteRead-only
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Node.js package
Tools by what they do 7
Read from the source code; the running server may list different tools.
Read 7 · Look things up without changing anything.
get_contexthealthinitprofilessearchvalidateverify
Tools (7)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
get_contextReturns coding standards, guardrails, and workflow for implementing a task. WHEN TO USE: - ALWAYS call this FIRST before writing any code - When starting a new feature, bugfix, or refactor - When unsure about project conventions RETURNS: - Detected stack (Java/Python/TypeScript/Go/Rust/etc) - Task type classification (feature/bugfix/refactor/test/security/performance) - MUST rules (mandatory guidelines) - AVOID rules (anti-patterns to prevent) - Code quality thresholds (max lines, coverage %) - Naming conventions (classes, methods, files) - Recommended TDD workflow EXAMPLE: get_context({ ta…
healthCheck server status, loaded profiles, and usage metrics. RETURNS: - Server status (OK/ERROR) - Version - Load time - Profiles loaded - Standards documents count - Usage metrics (tool calls, most used profile)
initSuggest a .corbat.json configuration for a project. WHEN TO USE: - Setting up Corbat for a new project - Want to customize coding standards for a project - Need to see available profiles and options Analyzes the project directory and suggests optimal configuration based on detected stack. RETURNS: - Detected stack information - Suggested .corbat.json content - Available profiles list - Setup instructions
profilesList all available coding standards profiles. RETURNS: List of profiles with ID and description. Profiles include: - java-spring-backend: Enterprise Java with Hexagonal Architecture - nodejs: Node.js/TypeScript with Clean Architecture - react, vue, angular: Frontend frameworks - python: FastAPI/Django - go, rust: Systems programming - And more... Use profile ID in .corbat.json or get_context will auto-detect.
searchSearch standards documentation for specific topics. WHEN TO USE: - Looking for specific technology guidance (kafka, docker, kubernetes) - Need detailed information on a pattern or practice - Exploring available standards EXAMPLE QUERIES: "kafka", "testing", "docker", "logging", "metrics", "archunit", "flyway" RETURNS: Up to 5 matching results with excerpts from documentation.
validateAnalyze code against coding standards with language-aware checks and heuristic fallback. WHEN TO USE: - After writing code, to check for issues - During iterative development - Before calling verify for final approval PERFORMS ANALYSIS: - Detects anti-patterns (empty catch, hardcoded secrets, etc.) - Measures method/class lengths where supported - Checks for interfaces and tests - Calculates quality score RETURNS: - Score (0-100) - CRITICAL issues (must fix) - WARNINGS (should fix) - Metrics (lines, methods, tests, etc.) - PASSED/NEEDS WORK verdict EXAMPLE: validate({ code: "public class U…
verifyVerify generated code before handoff. WHEN TO USE: - After generating code - Before review, handoff, or final response - As a final quality gate in agent workflows WHAT IT CHECKS: - Tests are provided (TDD compliance) - Interfaces exist (DI compliance) - No critical code issues - Quality score >= 50 RETURNS: - PASS: No blocking issues detected by configured checks - FAIL: Issues to fix, iterate and verify again WORKFLOW: 1. Generate code following get_context guidelines 2. Call verify({ code, tests, interfaces }) 3. If FAIL: fix issues and call verify again 4. If PASS: proceed to the next …
Signals
- Stars
- 5
- Forks
- 0
- Open issues
- 7
- Weekly downloads
- 13
- Last commit
- Jul 3, 2026 (3 months ago)
- Last release
- Jan 21, 2026 (9 months ago)
- Last package publish
- Feb 3, 2026 (8 months ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.corbat-tech/coding-standards- Version
- 1.0.3
- Auth
- No auth
- Packages
- npm @corbat-tech/coding-standards-mcp
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 25, 2026
Cite this page
Coding Standards MCP server. Agent Mart. https://agentmart.dev/connectors/corbat-tech-coding-standards (last updated 2026-10-25)