Skip to content
Agentmart
Submit a tool

Constraints Registry

Policy-as-code guardrails for AI coding agents, validated via OPA, Conftest, Checkov & Semgrep.

Connector by SureshKhemka · GitHub account verified by the MCP Registry

IndexedApache-2.0Local (stdio)
Write a review

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/sureshkhemka-constraints-registry

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.

We use your email only for this newsletter. Privacy

About

Policy-as-code guardrails for AI coding agents, validated via OPA, Conftest, Checkov & Semgrep.

No 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
3 read · 0 write · 0 deleteRead-only
Secrets
None asked for
Install scripts
Not scanned yet
Runs as
Python package

Tools by what they do 3

Read from the source code; the running server may list different tools.

Read 3 · Look things up without changing anything.

  • describe_scope
  • get_constraints
  • validate

Tools (3)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

  • describe_scope

    Discover the selector vocabulary present in the registry so you can build a correct scope instead of guessing. Output lists the distinct providers, resource_types (Terraform resource identifiers, e.g. 'aws_s3_bucket' not 's3_bucket'), environments, repos (tags like 'tag:data-plane'), categories, severities, sources, and relationship layers/interactions. Call this first if unsure of valid scope values.

  • get_constraints

    Return engineering constraints relevant to a scope. Inputs: scope (providers, resource_types, environments, repos, relationship), optional version (bundle id; defaults to latest). resource_types use Terraform resource identifiers, e.g. 'aws_s3_bucket' (NOT 's3_bucket'); repos are tags like 'tag:data-plane'. If unsure of valid values, call describe_scope first, or simply omit a dimension (omitted dimensions are 'don't care' and broaden the match rather than excluding). Output: {available, bundle_id, constraints[]}. Fails open: on any error returns available=false with an empty constraints list …

  • validate

    Validate a candidate artifact against in-scope constraints by delegating to enforcement engines. Inputs: artifact (object), scope, optional version. Output: {bundle_id, passed, results[]} where each result has constraint, severity, kind, verdict, violations, guidance.

Signals

Stars
0
Forks
0
Open issues
0
Weekly downloads
27
Last commit
Jun 27, 2026 (4 months ago)
Last release
Jun 27, 2026 (4 months ago)
Last package publish
Jun 27, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026) and the package registry.

Details

Registry name
io.github.SureshKhemka/constraints-registry
Version
0.1.1
Auth
No auth
License
Apache-2.0
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Cite this page

Constraints Registry MCP server. Agent Mart. https://agentmart.dev/connectors/sureshkhemka-constraints-registry (last updated 2026-10-24)