Attestable FAQs

Question 1

What does Attestable do?

Accepted Answer

Attestable verifies that an MCP server is running the intended, untampered code through hardware attestation, ensuring the integrity of the server environment.

Question 2

What are the key dependencies for running Attestable?

Accepted Answer

Key dependencies include Intel SGX hardware, Gramine, Python 3.13, Ubuntu 22.04, and the Intel SGX SDK & PSW.

Question 3

How does Attestable ensure code integrity?

Accepted Answer

It uses remote attestation with RA-TLS, SGX quotes embedded in X.509 certificates, and Trusted Execution Environments (TEEs) to generate signed attestations of the running code.

Question 4

Can I verify the code Attestable is running independently?

Accepted Answer

Yes, you can build and run the code locally, with or without secure hardware, and compare the generated values to those from a running Attestable server. The protocol used for client <-> server remote attestation is RA-TLS

Question 5

What is RA-TLS and how does Attestable use it?

Accepted Answer

RA-TLS is an extension to TLS that adds machine and code-specific measurements. Attestable uses it for client-server remote attestation, allowing MCP clients to verify the server's code before connecting.

Attestable

About

Key Features

Use Cases