
Openapi Security Contract Lint
io.github.jmshinhwaPublished by GitHub account jmshinhwav1.0.2Updated Oct 24, 2026
Finds the lines in an OpenAPI file that publish an endpoint with no authentication, an API key in th
Overview
Local stdio MCP server that scans an OpenAPI file and points out lines where endpoints are published without authentication or with weak API key placement.
- What you can do
- Inspect an OpenAPI specification for endpoints published with no authentication
- Flag API keys placed in the wrong location, such as query strings or headers
- Report the specific lines in the file where each problem occurs
- No tool list is published, so the exact operations are not documented; the description only covers this linting purpose.
- When to use it
- Useful when reviewing or auditing an OpenAPI spec before release and you want an assistant to locate endpoints that lack authentication or expose API keys in insecure positions.
- Requirements
- Runs as a local process over stdio, started with npx from the npm package @readystack/openapi-security-contract-lint, so Node.js and network access for the package download are needed. No authentication, environment variables or headers are declared.
Installation
In SourceWeft
- Open Openapi Security Contract Lint in the dashboard and add it to a workspace.
- 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
readystack-themes
Made by ReadyStack · free calculators and templates at getreadystack.com VS Code themes by ReadyStack
Source: README.md at commit ee1c884
Tools
0Version history
2- v1.0.2LatestSep 19, 2026
- v1.0.1Sep 18, 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.