Safeguard
sh.safeguardPublished by safeguard.shOfficial publisherv1.0.0Updated Oct 27, 2026
Software supply chain security: SBOMs, vulnerabilities, fixes, policies and compliance data.
Overview
Remote MCP server from Safeguard that gives an assistant access to software supply chain security data: SBOMs, vulnerabilities, fixes, policies and compliance.
- What you can do
- Work with software supply chain security data: SBOMs, vulnerabilities, available fixes, policies and compliance information.
- No tool list is published, so the exact operations an assistant can perform are not documented here.
- Access is through a hosted remote endpoint with OAuth sign-in rather than a local package.
- When to use it
- Consider it when you want an assistant to look into dependency and supply chain risk, such as reviewing SBOMs, checking known vulnerabilities and fixes, or consulting policy and compliance data during development or review work.
- Requirements
- A remote MCP client that supports streamable HTTP, pointed at the Safeguard hosted endpoint. OAuth authentication is required, so a Safeguard account with the appropriate access. No environment variables or headers are declared.
Installation
In SourceWeft
- Open Safeguard in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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/sh.safeguard%2Fsafeguard/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.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"safeguard": {
"type": "http",
"url": "https://mcp.safeguard.sh/mcp"
}
}
}Tools
0Version history
1- v1.0.0LatestOct 26, 2026
Score
83% 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
- LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.