Firmware Attestation MCP
Hardware trust layer for sovereign AI. Persistence implants live below the OS (BIOS/UEFI, SMM, network boot ROMs, HDD HPA) and survive OS reinstalls and disk wipes. This MCP attests a host's firmware trust state and gates inference on a verified result.
Tools
| Tool | What |
|---|---|
scan_firmware |
read-only host evidence (Secure Boot, TPM, SIP, BIOS, HPA) |
check_ant_signatures |
match to NSA-ANT-class persistence preconditions + defenses |
attest_firmware |
HMAC-signed attestation, verifiable at proofof.ai/api/verify |
gate_inference |
ALLOW/BLOCK AI on this host (strict by default) |
list_threat_model |
the attack surface this defends against |
Honest by design
Reports indicators (preconditions implants rely on), never "clean". A BLOCK means "lacks confirmed trust anchors," not "hacked." Harden per the listed defenses, then re-gate.
pip install firmware-attestation-mcp
© CSOAI LTD (trading as MEOK AI Labs) · MIT
Configuration
Add to your claude_desktop_config.json (Claude Desktop) or your MCP client config:
{
"mcpServers": {
"firmware-attestation-mcp": {
"command": "uvx",
"args": ["firmware-attestation-mcp"]
}
}
}
Or: pip install firmware-attestation-mcp then run the firmware-attestation-mcp command (stdio transport).
Examples
Once configured, ask your assistant, for example:
- "Use
scan_firmwareto …" - "Use
check_ant_signaturesto …" - "Use
attest_firmwareto …"
Part of the MEOK constellation
This MCP is one node in a connected ecosystem built by MEOK AI LABS around a single sovereign AI core — governed agents with a hash-chained audit trail, mapped to the CSOAI compliance charter.
- 🌐 The whole map: https://meok.ai/constellation
- 🛡️ AI governance & certification: https://councilof.ai · https://csoai.org
- ✅ Verify any signed report: https://meok.ai/verify
Metadata
Release files for firmware-attestation-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| firmware_attestation_mcp-1.0.3.tar.gz | 10.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| firmware_attestation_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.8 kB
Release files / firmware_attestation_mcp-1.0.3.tar.gz
| Download URL | firmware_attestation_mcp-1.0.3.tar.gz |
|---|---|
| Size | 10.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f4d4c26a236cbeceecf5ea98a0f9a6bb0459fecdc6c03c138732a8e4ffb98801
|
|
BLAKE2b-256 checksum How to use checksums |
4a5fd66282cef9c060d548cb1d69c479ecd5b6c63b564c3c8465c401a47f21ef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Release files / firmware_attestation_mcp-1.0.3-py3-none-any.whl
| Download URL | firmware_attestation_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 7.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f3e7daaf571e4a0f8ec5ae2644a2e7824ab3b798293735ec2d95cdbe6ee96f97
|
|
BLAKE2b-256 checksum How to use checksums |
922ab8f366da7bd90d7478ad417165a3b09b826ece2610e07f3a52fa5ce9f54c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.5
|
Security for firmware-attestation-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.