meok-agents-md-lint-mcpofficial
A
licenseNot graded
qualityD
maintenanceValidates AGENTS.md files against the cross-vendor coding-agent spec, detecting security smells and consistency issues.
MIT
constitution-lint
Server Details
Static linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 64 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
A4.3/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap. The tool's purpose is clearly distinct.
Naming Consistency5/5
The single tool name 'lint_constitution' follows a clear verb_noun pattern in snake_case, consistent with best practices. No inconsistency exists.
Tool Count4/5
A single tool for a narrow, focused purpose (linting constitution files) is slightly below the ideal range but still appropriate. Adding complementary tools (e.g., explanation of rules) might be beneficial but not necessary.
Completeness5/5
The tool covers 10 distinct heuristic checks that comprehensively address the domain of autonomous-agent constitution linting. No obvious gaps remain for its stated purpose.
Available Tools
1 toollint_constitutionAInspect
Heuristic checker for CLAUDE.md-style autonomous-agent constitution files — 10 checks against operational-guardrail patterns (authority order, spend limit, injection defense, secrets handling, escalation, ledger discipline, self-modification guard, honest reporting, session ritual, referenced-state-files). Pattern-matching, not comprehension.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| content | Yes | The full markdown text of a CLAUDE.md-style constitution file |
TDQS
A4.1/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description carries the full burden. It discloses the heuristic, pattern-matching nature and lists all 10 checks, providing good transparency into what the tool does and its limitations. No mention of side effects, but it is a read-only linter.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence that front-loads the purpose and efficiently lists the ten checks. Every part adds value; no extraneous words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness3/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the tool's purpose and scope but does not describe the return format or output. Given no output schema, some guidance on what the agent can expect would be helpful.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100% with the single parameter well-described. The description does not add new details about the parameter format beyond what the schema provides, but it explains the context of the check. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool is a heuristic checker for CLAUDE.md-style constitution files, specifies 10 specific checks, and differentiates itself from comprehension tools. It is a specific verb+resource combination with no ambiguity.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies when to use the tool (for linting constitution files) and includes a limitation ('pattern-matching, not comprehension'), which guides expectations. However, no explicit when-not or alternatives are given, though there are no sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
lint_constitution
Related MCP Connectors
Static linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.
Checks CLAUDE.md, AGENTS.md or a system prompt for 12 safeguards unattended agents need.
Research-backed lint + generation for agent context files (CLAUDE.md, AGENTS.md) + prompt enhancer.
MEOK AGENTS.md Linter MCP — validates the cross-vendor coding-agent spec (Cursor / Claude Code /
Related MCP Servers
- AlicenseAqualityAmaintenanceChecks the context files a coding agent reads (CLAUDE.md, AGENTS.md, SKILL.md, .cursor/rules) against the git index of a repository, and reports wrong letter case, broken links, missing paths, commands nothing defines and agent configuration that points at nothing. Two more tools report which sections drifted from the code and what each file costs; zero dependencies, stdio, Node 18 or newer.5374 npm5MIT
- FlicenseNot gradedqualityAmaintenanceScores prose from 0 to 100 for formulaic AI writing patterns using purely programmatic rules, with no LLM judge or API calls. Enables agents to lint text or files and receive a score, band label, specific violations with surrounding context, and concrete advice for each hit.-
- AlicenseNot gradedqualityAmaintenanceAI Constraint Engine that enforces CLAUDE.md, .cursorrules, and AGENTS.md rules as laws. 51 MCP tools for semantic conflict detection, patch review, drift scoring, pre-commit hooks, and Guardian Mode. Catches euphemisms, temporal evasion, and hidden violations that keyword matching misses.112 npm25MIT
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd
Glama MCP Gateway
Add one secure layer between your agents and this server.