I am the author of PGPkeygenerator.com — a client-side PGP key generator that runs entirely in the browser (no server, no tracking, keys never leave your machine).
With Chrome's new WebMCP API (navigator.modelContext) landing in Canary, I added a generate_pgp_keys tool registration so AI agents can invoke it directly from the browser without any backend or API key.
How it works:
1. The page registers a generate_pgp_keys tool via navigator.modelContext.registerTool()
2. The tool accepts name, email, and optional parameters (type, keySize, passphrase, expirationTime)
3. It populates the form, calls the existing key generation logic (OpenPGP.js), and returns all three PGP blocks (private key, public key, revocation certificate) as the tool response
To try it:
1. Enable chrome://flags#webmcp-for-testing in Chrome Canary (146+)
2. Install the Model Context Tool Inspector extension
3. Open pgpkeygenerator.com. The generate_pgp_keys tool should appear in the inspector — invoke it with { "name": "Alice Smith", "email": "alice@example.com" }
athanasiosem•1h ago
With Chrome's new WebMCP API (navigator.modelContext) landing in Canary, I added a generate_pgp_keys tool registration so AI agents can invoke it directly from the browser without any backend or API key.
How it works:
1. The page registers a generate_pgp_keys tool via navigator.modelContext.registerTool() 2. The tool accepts name, email, and optional parameters (type, keySize, passphrase, expirationTime) 3. It populates the form, calls the existing key generation logic (OpenPGP.js), and returns all three PGP blocks (private key, public key, revocation certificate) as the tool response
To try it:
1. Enable chrome://flags#webmcp-for-testing in Chrome Canary (146+) 2. Install the Model Context Tool Inspector extension 3. Open pgpkeygenerator.com. The generate_pgp_keys tool should appear in the inspector — invoke it with { "name": "Alice Smith", "email": "alice@example.com" }
Source: github.com/athanasiosem/pgpkeygenerator.com