Developer · Remote MCP server
SBOMApp - SBOM Generator & Vulnerability Scanner
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mcpsbom/sbom-mcp- Version
- 1.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-02-23
- Updated
- 2026-02-23
- Publisher
- mcpsbom (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mcpsbom) · how
- Repository
- github.com/mcpsbom/sbomapp-mcp-server
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.sbomapp.com/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 301)
- Handshake
- HTTP 301
- Checked on
- 2026-10-05
How to connect SBOMApp - SBOM Generator & Vulnerability Scanner
SBOMApp - SBOM Generator & Vulnerability Scanner is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.sbomapp.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| sapiom MCPLocal Sapiom developer MCP for authoring, testing, deploying, and inspecting agents. | Local · stdio |
| SAS ViyaExecute SAS code and query Compute, CAS, and model APIs on SAS Viya via OAuth 2.0. | Local · stdio |
| SaSame MCP Observatory + Gold Rush TownNo-key MCP: audit/certify MCPs, signed trust history; join Gold Rush Town & build with your LLM. | Remote · HTTPLive check: ✓ handshake |
| SavantoAI MCP-SERVERManage your Savanto store from your AI: catalog, content, prompts, and analytics, by chat. | Remote & Local · HTTP, stdioLive check: sign-in required |
| ScalingoManage Scalingo PaaS apps, deployments, containers, logs and env vars from your AI assistant. | Remote · HTTPLive check: ✓ handshake |
| Scalix CloudThe agent-native cloud: database, functions, AI, storage, computers. 50 tools, one API key. | Remote · HTTPLive check: ✓ handshake |
| ScanduroRemote MCP server for Scanduro QR codes, scan analytics and controlled code actions. | Remote · HTTPLive check: sign-in required |
| ScanLabsAI Security ScannerScan a website for vulnerabilities: OWASP Top 10, CVEs, SSL, headers - with plain-English fixes. | Remote & Local · HTTP, stdioLive check: ✓ handshake |