Openapi Lint

io.github.CedricKoumaPublished by GitHub account CedricKoumav0.1.0Updated Oct 24, 2026

MCP server (stdio): lint OpenAPI specs with Spectral via the AgentForge API

VerifiedStreamable HTTPWeb executableDeveloper Tools

Overview

AI-generated overview

MCP server that lets an assistant lint OpenAPI specifications with Spectral through the AgentForge API, run locally over stdio or as a remote endpoint.

What you can do
  • Lint OpenAPI specifications with Spectral through the AgentForge API.
  • No individual tools are listed in the manifest, so the exact operations are not documented here.
  • Available both as a local npm package over stdio and as a remote streamable HTTP endpoint.
When to use it
Useful when you want an assistant to check OpenAPI or API specification files for style and validity problems without setting up Spectral yourself.
Requirements
Either the remote endpoint or the local npm package agentforge-openapi-lint-mcp (Node.js). An AgentForge APIM subscription key, supplied as the Ocp-Apim-Subscription-Key header or the AGENTFORGE_API_KEY environment variable; the free tier is said to work for smoke tests. AGENTFORGE_BASE_URL optionally sets the gateway base URL. Network access to the AgentForge gateway.
Before you install
A subscription key is required and is sent to the AgentForge gateway; keep it out of shared configuration. Your OpenAPI specifications are sent to that third-party API for linting, so avoid confidential specs unless that is acceptable. The manifest lists no tools, so verify behavior before relying on it.

Installation

In SourceWeft

  1. Open Openapi Lint in the dashboard and add it to a workspace.
  2. Connect Ocp-Apim-Subscription-Key credentials. They are stored privately and never shown on public pages.
  3. 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/io.github.CedricKouma%2Fopenapi-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": {
    "openapi-lint": {
      "type": "http",
      "url": "https://apim-agentforge-6lfm33.azure-api.net/openapi-lint/mcp",
      "headers": {
        "Ocp-Apim-Subscription-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% 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
  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.