Does Trustcard make an MCP server safe?

No. Trustcard verifies identity, approved tool contracts, expiry, drift, and proxy enforcement. Those controls reduce unauthorized change and access, but they do not prove that a publisher or runtime is benign.

When is renewal safe?

Renewal is safe only when the complete observed contract still matches the approved contract. Any tool, schema, description, capability, or policy drift requires review and explicit reapproval.

Will it change my MCP configuration automatically?

Audits and previews are read-only. Gate, renew, and reapprove operations write files only after explicit authorization, preserve existing transports and environment references, and must never print or embed credential values.

Trustcard Operations

Trustcard fleet audit

I inspected the selected MCP client configuration and preserved its existing transports, environment references, and credentials. No business tools were invoked.

Server	Route	Manifest	Result
filesystem	stdio proxy	Valid, expires in 11 days	Renewal preview is safe
linear	direct HTTP	None	Ungated route found
internal-search	stdio proxy	Contract changed	Reapproval required

Recommended actions

Renew

filesystem because its complete observed contract still matches the approved contract. The preview preserves its deny rules and required scopes.
2. Gate linear through the loopback HTTP proxy. I prepared the command and config diff, but did not apply it.
3. Review

internal-search manually: one tool description and input schema changed. Renewal is refused because this is contract drift, not expiry maintenance.

Evidence and limits

Publisher signatures establish key and content binding; they do not prove safe runtime behavior. The behavioral harness isolates the working directory and environment, but it is not an OS sandbox and does not block filesystem or network access. A successful manifest write also does not prove that a running client reloaded it.

No files were changed. Next step: approve the filesystem renewal and the proposed Linear gate separately.

About this skill

Set up, inspect, renew, and troubleshoot Trustcard enforcement for MCP servers without exposing credentials or weakening policy. The skill guides agents through fleet status checks, manifest expiry and drift handling, HTTP and stdio gating, scoped authorization, signed evidence, safe reapproval, and runtime verification. It clearly separates local proxy policy from publisher attestation and documents the limits of process isolation.

Trustcard Operations