Back to Browse

Firmware Attestation MCP Server

Developer ToolsUse Caution3.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Firmware Attestation MCP — hardware trust layer for sovereign AI. Scan firmware, check

About

Firmware Attestation MCP — hardware trust layer for sovereign AI. Scan firmware, check

Security Report

3.2
Use Caution3.2High Risk

The MCP implements firmware attestation with reasonable security intent, but contains several actionable security and code quality issues. A hardcoded default signing key, use of subprocess without shell=False safeguards, broad exception handling, and exposed monetization/upsell infrastructure lower confidence. Permissions (file_read, system_info, network_http, env_vars) are appropriate for the stated purpose, but implementation practices introduce unnecessary risk. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

5 files analyzed · 14 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

File System Read

Reads files on your machine. Normal for tools that analyze or process local data.

system_info

Check that this permission is expected for this type of plugin.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-csoai-org-firmware-attestation-mcp": {
      "args": [
        "firmware-attestation-mcp"
      ],
      "command": "uvx"
    }
  }
}

Reviews

No reviews yet

Be the first to review this server!