Client Identity
Create a cryptographic identity for this playground. When you connect to MCP-I servers, this identity proves who the client is—enabling tamper-evident audit trails.
Note: This identity belongs to the playground (the client software), not to you personally. You, as the human, are the principal who authorizes the playground to act on your behalf.
Identity Generator
Self-Certifying Identity
MCP-I uses W3C Decentralized Identifiers that require no central authority. The verification key is embedded directly in the identifier—anyone can verify signatures without external lookups.
Learn more about identity in MCP-I →Portable Credentials
The did:key format works across systems and platforms. Based on the W3C standard, these identities are recognized by any compliant implementation.
Build Your First Tamper-Evident Proof
Now that you have a verifiable identity, see how MCP-I uses it to create audit-ready signatures that anyone can verify.
See How Proofs Work