Constitution Lint

dev.agentopskitPublished by agentopskit.devOfficial publisherv1.2.0Updated Oct 24, 2026

Static linter for CLAUDE.md-style agent constitution files: 10 operational-guardrail checks.

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

A static linter that checks CLAUDE.md-style agent constitution files against ten operational-guardrail rules.

What you can do
Constitution Lint is a remote MCP server that statically analyzes agent constitution files, such as CLAUDE.md-style documents, and reports on ten operational-guardrail checks. It is intended to flag missing or weak guardrails in an agent's written instructions rather than to run or modify the agent itself. No individual tool names are listed in the available registry data.
When to use it
Use it when you maintain an agent constitution or instruction file and want a quick, repeatable review of whether its operational guardrails are present and well formed. It suits teams that want lint-style feedback on agent policy documents before shipping them.
Requirements
It runs as a remote streamable HTTP endpoint at agentopskit.dev, so network access is required. The manifest declares no authentication, no environment variables, and no headers, and no local package or runtime is needed.
Before you install
The server is remote and the manifest declares no authentication, so consider whether the constitution file content you submit is sensitive before sending it to a third-party endpoint. The available data does not describe whether it stores or logs submitted content.

Installation

In SourceWeft

  1. Open Constitution Lint in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.agentopskit%2Fconstitution-lint/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "constitution-lint": {
      "type": "http",
      "url": "https://agentopskit.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

17% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.