meok-agents-md-lint-mcpofficial
A
licenseNot graded
qualityC
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 with GitHub, an HTTP challenge, or a DNS record. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 38 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
TDQS
A4.2/5.0
Scored across 1 tool
Disambiguation5/5
Only one tool exists, so there is no possibility of selecting the wrong tool. Its description clearly identifies it as a linter for constitution files, making its purpose unambiguous.
Naming Consistency5/5
The single tool name 'lint_constitution' follows a clear verb_noun pattern that is both descriptive and conventional. With only one tool, naming consistency is inherently flawless.
Tool Count5/5
The server has exactly one tool, which is perfectly suited to its singular purpose of linting constitution files. The single tool encapsulates all necessary functionality (10 checks), so the count is well-scoped rather than too thin.
Completeness5/5
The server's purpose is to lint CLAUDE.md-style constitutions, and the single tool covers 10 specific guardrail checks, appearing comprehensive for the domain. There are no obvious missing operations required to fulfill the stated linting niche.
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.
Research-backed linting + generation for agent context files (CLAUDE.md, AGENTS.md, Cursor rules).
MEOK AGENTS.md Linter MCP — validates the cross-vendor coding-agent spec (Cursor / Claude Code /
Lint a SKILL.md for frontmatter, structure, secrets and size. All 6 tools free.
Related MCP Servers
- 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.177 npm25MIT
@operstack/mcpofficial
AlicenseAqualityBmaintenanceEnables Claude, Cursor, and other MCP clients to audit public sites across six areas, check and follow llms.txt links, compare rival sites side by side, and run sixteen content gates on local Markdown or MDX using only free public signals.4239 npmMIT- AlicenseNot gradedqualityAmaintenanceEnables deterministic auditing of agent skills, system prompts, and downloaded file collections against eight malicious-skill supply-chain patterns, returning line-numbered findings and pass/flag verdicts without using an LLM or network calls.15 PyPIMIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.