-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Description
Summary
We've built an MCP (Model Context Protocol) server that gives AI agents like Claude Desktop their own decentralized identity. This enables AI-to-AI encrypted communication, verifiable credentials, and cryptographic proof of identity — all with local wallet storage.
The Problem
AI agents are proliferating across every platform, but they lack identity infrastructure:
- API keys leak (Moltbook, Feb 2026: 1.5M keys exposed)
- No way to verify who an agent is or who controls it
- No encrypted communication between agents
- No credential-based authorization for agent actions
The Solution
The Archon MCP Server provides:
| Capability | Description |
|---|---|
| 🔐 DID Creation | Each agent gets a unique decentralized identifier |
| 📬 Encrypted Messaging | DMail between agents (end-to-end encrypted) |
| 🎫 Verifiable Credentials | Issue, hold, and present credentials |
| 🔑 Local Wallet | Private keys never leave the user's machine |
| ✅ Challenge/Response | Prove identity and verify others |
Architecture
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Claude Desktop │────▶│ Archon MCP │────▶│ Gatekeeper API │
│ (or any MCP │ │ (local process) │ │ (DID resolution)│
│ client) │ └────────┬─────────┘ └─────────────────┘
└─────────────────┘ │
▼
┌──────────────────┐
│ ~/.archon-mcp/ │
│ wallet.json │
│ (local storage) │
└──────────────────┘
Key architectural decisions:
"mcp-server-proposal.md" 126L, 4510B
create_id,list_ids,get_current_id,set_current_idresolve_didsend_dmail,list_dmail,read_dmailcreate_challenge,create_response,verify_responselist_credentials,get_credential,accept_credentialwallet_status,create_wallet
Configuration
| Variable | Default | Description |
|---|---|---|
ARCHON_PASSPHRASE |
changeme |
Wallet encryption |
ARCHON_GATEKEEPER_URL |
https://archon.technology |
Gatekeeper endpoint |
ARCHON_WALLET_DIR |
~/.archon-mcp |
Wallet location |
ARCHON_REGISTRY |
hyperswarm |
Default registry |
Benefits
For AI Agent Developers
- Drop-in identity for any MCP-compatible agent
- No infrastructure to run — just
npxand configure - Works with existing Archon ecosystem
For Enterprise
- Agents can prove authorization via credentials
- Audit trail via DID operations
- Self-hosted gatekeeper option
For the Ecosystem
- Standard identity layer for AI agents
- Interoperable with SSI/DID standards
- Positions Archon as infrastructure for AI identity
Next Steps
- Create
archetech/archon-mcp-serverrepository - Publish to npm as
@archon-protocol/mcp-server - Add to archon.technology website
- Register in MCP server directories
- Announce to community
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels