Identity Layer for Model Context Protocol
Replace API keys in AI agent communication with cryptographic identity. JSON-RPC 2.0 transport with policy enforcement, audit logging, and zero configuration for Model Context Protocol.
Zero-Config Identity Transport
Connect AI agents using cryptographic identity in two steps. No API key management, no token rotation, no configuration files.
import { MCPClientAdapter } from '@private.me/mcp-transport'; import { generateIdentity } from '@private.me/xlink'; const client = new MCPClientAdapter({ implementation: { name: 'my-agent', version: '1.0' }, capabilities: { tools: {} }, transport: { identity: await generateIdentity(), peerDid: 'did:key:z6Mk...', policy: { maxCallsPerHour: 100 } } }); await client.connect(); const tools = await client.listTools(); const result = await client.callTool('payment', { to: 'alice', amount: 100 });
import { MCPServerAdapter } from '@private.me/mcp-transport'; import { generateIdentity } from '@private.me/xlink'; const server = new MCPServerAdapter({ implementation: { name: 'payment-server', version: '1.0' }, capabilities: { tools: { listChanged: true } }, transport: { identity: await generateIdentity(), peerDid: 'did:key:z6Mk...' } }); server.registerTool({ name: 'payment', description: 'Send payment', inputSchema: { /* ... */ } }, async (args) => { // Process payment return { success: true }; }); await server.start();
API Keys Fail at Agent Scale
Traditional API key authentication breaks down when orchestrating AI agents. A single expired token can cascade across 500 agents simultaneously. Shared credentials eliminate attribution. Monthly rotation requires coordinated downtime.
| Approach | Failure Mode |
|---|---|
| API Keys | Shared secrets → One leak = system-wide compromise → Rotation requires coordinated shutdown |
| OAuth Tokens | Expiry at hour 3 of 4-hour workflow → Restart from zero → Tripled compute cost |
| MCP Transport | Per-message signatures → Non-reusable by design → Failure mode eliminated architecturally |
Example: Cascading Failure
// Every agent uses the same API key const agents = await Promise.all( Array.from({ length: 500 }, (_, i) => createAgent({ id: `agent-${i}`, apiKey: process.env.API_KEY // Same key for all 500 }) ) ); // Problems: // One compromised agent → rotate key → 500 agents offline // Can't identify which agent made which request // Can't rate-limit per-agent (all share quota)
// Each agent generates unique cryptographic identity const agents = await Promise.all( Array.from({ length: 500 }, async (_, i) => { const client = new MCPClientAdapter({ implementation: { name: `agent-${i}`, version: '1.0' }, capabilities: { tools: {} }, transport: { identity: await generateIdentity(), peerDid: serverDid } }); return client; }) ); // Benefits: // One compromised agent → remove from trust registry → 499 continue // Cryptographic attribution per message // Per-agent rate limits enforced independently
Identity vs API Keys
No Token Rotation
Each message uses a fresh Ed25519 signature that cannot be replayed. Private keys never leave the device. No long-lived credentials to rotate. Auditors care about risk reduction, not specific mechanisms.
Isolated Failures
One compromised agent does not affect 499 others. Remove the compromised identity from trust registry. No system-wide shutdown. No coordinated rotation. Failures stay isolated.
Cryptographic Attribution
Every message is signed with the sender's private key. Verify exactly which agent sent which request. Enforce per-agent rate limits. Audit trail with cryptographic proof.
Where MCP Transport Fits
Purchase & Subscription
All Private.Me ACIs follow the same subscription model: 3-month trial, then tier-based pricing. Purchase programmatically via API or through the web interface.
Pricing
Standard pricing: $5/month Basic • $10/month Middle • $15/month Enterprise
| Tier | Price | Features |
|---|---|---|
| Basic | $5/month | MCP transport, identity auth, connection pooling |
| Middle | $10/month | Everything in Basic + advanced policies, custom registries |
| Enterprise | $15/month | Everything in Middle + air-gapped deployment + white-label |
Subscribe via Web
Visit the subscription page with the product parameter:
https://private.me/subscribe?product=mcp-transport
Purchase via API
Programmatic subscription via REST API. Requires customer account token.
POST /api/purchase Content-Type: application/json { "product": "mcp-transport", "tier": "basic", "email": "customer@example.com", "customerId": "cus_abc123" }
{
"subscriptionId": "sub_xyz789",
"status": "active",
"trialEnd": "2026-07-28T00:00:00Z",
"product": "mcp-transport",
"tier": "basic"
}
Error Handling
All errors follow RFC 7807 (Problem Details for HTTP APIs) with structured field validation.
{
"type": "https://private.me/errors/validation-failed",
"title": "Validation Failed",
"status": 400,
"detail": "Request validation failed",
"instance": "/api/purchase",
"fields": {
"email": "Invalid email format",
"tier": "Must be one of: basic, middle, enterprise"
}
}
X-Idempotency-Key header for safe retries. Duplicate requests return X-Idempotency-Replay: true with original response. Keys expire after 24 hours.
Core Classes
Policy Enforcement
Control agent behavior with declarative policies. Enforce method allowlists, rate limits, and custom validation.
const transport = new XLinkTransport({ identity: myIdentity, peerDid: serverDid, policy: { allow: ['tools/call', 'tools/list'], deny: ['admin/*'], maxCallsPerHour: 100, maxCallsPerDay: 1000, customValidator: async (message) => { // Custom business logic return ok(undefined); } } });
Adding to Existing Projects
npm install @private.me/mcp-transport
MCP Transport works with any JSON-RPC 2.0 compatible system. Drop-in replacement for HTTP/WebSocket transports.
const client = new MCPClient({ transport: new HttpTransport('https://api.example.com') });
const client = new MCPClientAdapter({ implementation: { name: 'my-client', version: '1.0' }, capabilities: { tools: {} }, transport: { identity: await generateIdentity(), peerDid: 'did:key:z6Mk...' } });
Cryptographic Design
| Algorithm | Ed25519 (FIPS 186-5) |
| Key Derivation | PBKDF2-HMAC-SHA256 (600K iterations) |
| Message Signing | Detached signatures, tamper-evident |
| Replay Protection | Nonce-based, time-windowed |
| Shared Secrets | None (each agent has unique identity) |
Threat Model
MCP Transport protects against credential theft, replay attacks, and cascading failures. Does NOT protect against compromised endpoints or malicious tool implementations.
Benchmarks
Benchmarks measured on 2024 Apple M3 Pro. Ed25519 signature verification adds 0.36ms overhead per call. Connection pooling and health checks are automatic.