mcpdirectory.dev
9,129 servers · updated 23 Sept

Norma MCP server

official from Qualityclouds Active last commit 23 d
{
  "mcpServers": {
    "qualityclouds-norma": {
      "type": "http",
      "url": "https://api.qualityclouds.ai/mcp"
    }
  }
}
file .mcp.json (in your project root)version 1.0.0

What it does

Norma is a remote MCP server that performs deterministic, stack-aware code review by fetching applicable rulesets for a detected tech stack, checking individual files against those rules, and recording outcomes in a compliance audit trail. It is aimed at developers and teams using AI coding agents who need reproducible, auditable code quality enforcement rather than variable AI suggestions.

  • Automatically fetch security, performance, and maintainability rules for your detected stack (TypeScript, Python, Supabase, etc.) before an agent writes or modifies code.
  • Run a deterministic check on each file after it is created or changed, getting the same verdict every time for the same file and rules.
  • Record which rules were verified, which violations were fixed or prevented, and which model did the work, producing a structured compliance audit trail.

Tools this server exposes

ToolDoes
link_repositoryLinks the current workspace to Norma; must be called once before any other tool in a new workspace.
get_rulesetsDetects the repository's tech stack and returns the applicable rulesets, one per language or framework.
get_rules_for_rulesetReturns all rules in a given ruleset, including each rule's ID, name, severity, impact area, description, and fix guidance.
live_checkChecks one file against the organization's rules deterministically; stores nothing and returns the same verdict for the same inputs.
get_open_issuesReturns open issues from the last full scan of the linked repository, each with context needed to fix it.
register_applied_actionsRecords the outcome of a coding task in the compliance audit trail, including rules verified, violations fixed or prevented, and the model used.

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.