OpenLint MCP
Related Servers
Alternatives to OpenLint MCP
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to lint API artifacts (OpenAPI, AsyncAPI, Arazzo) and manage rulesets conversationally via the Model Context Protocol.4Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with OpenAPI documents for analysis, validation, and management through structured interfaces.1,070 npm3ISC
- AlicenseAqualityDmaintenanceEnables AI clients to validate OpenAPI specs, compare versions, detect breaking changes, and generate changelogs.4MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to browse, read, compare, and validate OpenAPI contracts for providers and consumers.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to lint and validate OpenAPI and Swagger specs and to diff two versions of a spec, classifying each change as breaking, potentially breaking, or non-breaking with request-vs-response context, JSON pointers and source lines. It also produces markdown changelogs, filters and describes endpoints, and checks example payloads against operation schemas, all offline within a sandboxed directory.MIT
- FlicenseAqualityBmaintenanceEnables LLMs to dereference and query OpenAPI/Swagger specifications, search endpoints and schemas, validate payloads, extract security schemes, and generate production-ready integration code in multiple languages.8-
TDQS
Scored across 2 tools
The two tools perform clearly distinct actions: listing configured rulesets versus validating a ruleset definition. Although both concern rulesets, the descriptions make the boundary unambiguous, so an agent can easily choose the right one.
Both names follow a consistent snake_case verb_noun pattern (list_rulesets, validate_ruleset). The convention is predictable and readable.
Two tools is borderline thin for a server whose apparent purpose is linting. The set covers only ruleset introspection, leaving the core linting action absent.
The description of validate_ruleset references lint_document, which is not exposed as a tool, so the central operation of an OpenLint server is missing. There is also no way to inspect individual rules within a ruleset, leaving significant gaps for agent workflows.