Openapi Scout Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.2Updated Nov 1, 2026

Local read-only OpenAPI and Swagger inspection with secret-safe schema summaries. Tools include...

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Local, read-only MCP server that summarizes local OpenAPI or Swagger JSON files so an assistant can explain an API contract before coding.

What you can do
  • Summarize a spec's version, title, servers and operations
  • Look up a single operation by its operationId
  • List component schemas or Swagger definitions
  • Redact examples, defaults, security schemes and credential-like keys in results
When to use it
Useful when you have an OpenAPI or Swagger JSON file on disk and want an assistant to explain its endpoints and schemas before writing clients, tests, mocks or documentation.
Requirements
Runs as a local stdio process installed from the npm package openapi-scout-mcp (Node.js; build and run locally). The spec must be a local JSON file of at most 2 MB; no network access, accounts or API keys are used.
Before you install
Read-only inspection only: it is not a full OpenAPI validator or security scanner, and YAML is not parsed, so convert to JSON first. It accepts only local JSON files and does not fetch URLs. Sensitive fields are redacted in output, but the spec file itself is still read from your machine.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

openapi-scout-mcp

A local-only MCP tool for quickly understanding an OpenAPI or Swagger JSON contract before writing clients, tests, mocks, or documentation.

Tools

  • inspect_spec: summarize version, title, servers, and operations.
  • find_operation: inspect one operation by operationId.
  • list_schemas: list component schemas or Swagger definitions.

Safety boundaries:

  • Only local JSON files are accepted. URLs and network fetches are not supported.
  • Files are capped at 2 MB and results are bounded.
  • Examples, defaults, security schemes, and credential-like keys are redacted.
  • YAML is not parsed in this release. Convert it to JSON first.

This is an inspection aid, not a complete OpenAPI validator or security scanner.

Run

bash
npm installnpm run buildnode dist/index.js

Source: README.md at commit 375a358

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestOct 2, 2026
  2. v1.0.0Sep 22, 2026

Score

40% 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 days25 pts

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

  • Auth declared10 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
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.