Repository navigation
Integrity Check
Minibridge can generate an SBOM file for an MCP server that contains hashes of various parts interpreted by an LLM. This SBOM file can be used to check that the MCP Server did not change, either offline or online by passing it to the backend, which will inspect each relevant MCP call dynamically.
To generate an SBOM file:
minibridge scan sbom -- uvx mcp-server-fetch > server.sbomThis will create server.sbom, which contains all the hashes of the relevant parts.
To verify that an MCP server still matches a previously generated SBOM file:
minibridge scan check server.sbom -- uvx mcp-server-fetchThe SBOM file can be passed to Minibridge to dynamically ensure no LLM-interpreted parts have changed since the SBOM file was generated.
For instance, it can ensure a tool that reads a file does not suddenly change to a tool that sends all your credentials to some shady place.
First, generate an SBOM file for your MCP Server:
minibridge scan sbom -- uvx mcp-server-fetch > server.sbomThis will create server.sbom, which contains all the hashes of the relevant parts.
Then, start Minibridge with live SBOM validation in your Client:
{
"mcpServers": {
"fetch": {
"command": "minibridge",
"args": ["aio", "--sbom", "server.sbom", "--", "uvx", "mcp-server-fetch"]
}
}
}You can try to alter server.sbom, and for the fetch hash, if you restart your client and ask for the list of tools, it will not list fetch. In your client logs, you will see:
2025-04-19T21:03:54.255Z [info] [fetch] Message from server: {"jsonrpc":"2.0","id":2,"error":{"code":451,"message":"'fetch': hash mismatch"}}
Dump all the tools, prompts, resources and resource templates of a particular MCP Server.
For example:
minibridge scan dump -- npx @modelcontextprotocol/server-everything