Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

OpenAPI Lint

OCI · GHCR.IO/BASITALISANDHU/MCP-OPENAPI-LINT

Lint OpenAPI 3.x documents for missing security, responses, descriptions and versioning.

49 Trust /100

Last scanned (4 hours ago)

Scores higher than 74% of OCI servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to basitalisandhu/dev-mcp-servers). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 3 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability58
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 794 tokens (~198/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 57% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Oct 26 +2
    • Stability: unverified → 0.10 ▲ functional
  • 14 Oct 26 +27
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 57 functional
    • First check of Schema quality: good functional
  • 13 Oct 26 0
    • Package version: 0.2.0 → 0.2.1 functional
  • 12 Oct 26 20

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Oct 2026 · Analysed oci/ghcr.io/basitalisandhu/mcp-openapi-lint@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem oci
Reason Verified
Discovered via OCI referrers API
Source repo basitalisandhu/dev-mcp-servers
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/basitalisandhu/dev-mcp-servers/.github/workflows/publish-github-packages.yml@refs/tags/v0.2.1
Rekor log index 3244679618
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha256:68f92eeb91c3eedffa81e9d64896a23474d89073c1dbae60f0630b113430e78d

Background: How many MCP packages publish verified provenance →

MCP tools · 4 exposed · ~610 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
explain_rule ~133

Describe one lint rule: its default severity, what it detects and how to fix it. Rules: openapi-version, info-description, server-http, no-security-schemes, operation-no-security, operation-public, security-scheme-undefined, unused-security-scheme, operation-no-responses, operation-no-success-response, response-no-description, operation-no-description, operation-no-operation-id, duplicate-operation-id, path-unversioned, path-parameter-undefined, path-parameter-not-required, parameter-no-description, parameter-no-schema, request-body-no-content, deprecated-operation, tag-undefined.

NameTypeReqDescription
rulestringyes–

No output schema declared.

No examples provided.

get_operation ~137

Return the full definition of one operation, selected by operation_id or by method and path, with path-level parameters merged in and local $ref values resolved one level. Useful for reading a single endpoint out of a large document.

NameTypeReqDescription
document––The document itself, as JSON or YAML text or as an object. Alternative to path.
methodstring––
operation_idstring––
operation_pathstring–Path template as written in the document, for example /users/{id}.
pathstring–Path to a local OpenAPI JSON or YAML file (up to 5242880 bytes).

No output schema declared.

No examples provided.

lint_openapi ~189

Check an OpenAPI 3.x document and return findings sorted by severity (error, warning, info), each with a rule id, a JSON Pointer path into the document and a message. Rules cover: openapi version, http server URLs, missing or unused security schemes, operations with no security requirement (and explicitly public ones), undefined schemes, operations without responses or without a success response, responses and parameters without descriptions, path parameters not declared or not required, missing operationId and duplicates, unversioned paths, request bodies without content, deprecated operations and undeclared tags. Pass ignore to silence rule ids.

NameTypeReqDescription
document––The document itself, as JSON or YAML text or as an object. Alternative to path.
ignorearray–Rule ids to skip.
pathstring–Path to a local OpenAPI JSON or YAML file (up to 5242880 bytes).

No output schema declared.

No examples provided.

list_operations ~151

Return every operation (method and path) with operationId, summary, tags, deprecated flag, effective security (the operation's own requirement, the global one, 'public' for security: [], or 'inherited-none' when nothing applies), parameters with location and required flag, request body media types and response codes. Optional filters: tag, method, path_prefix.

NameTypeReqDescription
document––The document itself, as JSON or YAML text or as an object. Alternative to path.
methodstring––
pathstring–Path to a local OpenAPI JSON or YAML file (up to 5242880 bytes).
path_prefixstring––
tagstring––

No output schema declared.

No examples provided.

Install

How do I install the OpenAPI Lint MCP server?

OpenAPI Lint runs locally as a container image, launched with docker run --rm -i ghcr.io/basitalisandhu/mcp-openapi-lint:0.2.1. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/basitalisandhu/mcp-openapi-lint

# add to Claude Code
claude mcp add basitalisandhu-mcp-openapi-lint -- docker run --rm -i ghcr.io/basitalisandhu/mcp-openapi-lint:0.2.1
Common questions

What is the OpenAPI Lint MCP server?

OpenAPI Lint is an MCP server listed in the public MCP registry as io.github.basitalisandhu/mcp-openapi-lint. Lint OpenAPI 3.x documents for missing security, responses, descriptions and versioning. This page covers its container image (ghcr.io/basitalisandhu/mcp-openapi-lint).

Is the OpenAPI Lint MCP server safe to use?

OpenAPI Lint scores 49 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the OpenAPI Lint MCP server expose?

OpenAPI Lint exposes 4 tools: lint_openapi, list_operations, get_operation, explain_rule. Their descriptions and schemas cost roughly 610 tokens of context every time the server is loaded.

Is the OpenAPI Lint MCP server still maintained?

OpenAPI Lint is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the OpenAPI Lint MCP server under?

OpenAPI Lint declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.