io.github.Neo1228/swagger-mcp-bridge

Name: io.github.Neo1228/swagger-mcp-bridge
Rating: 60 (1 reviews)
Author: io.github.Neo1228

MCPcommunity

v0.1.0io.github.Neo1228UnknownUpdated 2mo agoGitHub

Spring Boot example that exposes SpringDoc OpenAPI operations as safe MCP tools.

Turn any SpringDoc-powered Spring Boot API into a production-ready MCP gateway. Swagger MCP Bridge discovers your OpenAPI operations, publishes them as safe MCP tools, and adds a smart gateway layer for API discovery, validation, response shaping, and multi-step workflow orchestration. This repository intentionally separates the public surfaces so each one reads naturally in its own ecosystem:…

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →

2mo agoLast update

Package

Authorio.github.Neo1228

LicenseUnknown

Version0.1.0

Sourcemcp-registry

GitHubNeo1228/spring-boot-starter-swagger-mcp

Trust Status

60/100Good

✓Listed in Forge index+10/10

—Publisher identity verified+0/25

→ Publisher: run `forge publish` from the package repo to claim ownership

—Ed25519 publish signature+0/10

→ Included automatically when the publisher runs `forge publish`

—Domain verification+0/5

→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }

—CVE scan · not run+0/30

→ Not yet scanned — package must be on npm

✓Static analysis · clean+20/20

—npm provenance (Sigstore)+0/5

→ Publish from GitHub Actions with the --provenance flag

Paste into Claude Code, Cursor, or any AI assistant to fix all gaps

StatusCommunity-indexed

PublisherUnverified

SignatureUnsigned

Domain—

Provenance—

DependenciesNot audited

Tool surface—

Security scan✓ CleanvHEAD · 19d ago

EvalsNone

IndexedJun 13, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts — it cannot prove the absence of malicious code.

About

Keywords

mcp