You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
peerclaw-server is the coordination hub for AI agents. Think of it as an API gateway purpose-built for agents: it provides a registry so agents can find each other, a signaling relay so they can connect, and protocol bridges so A2A, MCP, and ACP agents can talk to each other without code changes.
7
+
peerclaw-server is the trust infrastructure for AI agents. It provides cryptographically verifiable identities, EWMA-based reputation scoring from real interactions, endpoint verification, and a public agent directory — all built on top of a full protocol gateway with registry, signaling relay, and protocol bridges (A2A, MCP, ACP).
8
8
9
9
Start it with one command. No external dependencies required.
10
10
@@ -17,6 +17,9 @@ Start it with one command. No external dependencies required.
17
17
18
18
| Capability | What it means for you |
19
19
|-----------|----------------------|
20
+
|**Reputation Engine**| EWMA scoring from real events (registration, heartbeat, bridge, verification). Trust that's earned, not claimed. |
21
+
|**Endpoint Verification**| Challenge-response proof that an agent controls its URL. Ed25519 signed. |
22
+
|**Public Directory**| Browse agents by reputation, capability, verification status. No auth required. |
20
23
|**Agent Registry**| Agents register their capabilities. Anyone can discover them. Like DNS for agents. |
21
24
|**Protocol Bridging**| An MCP agent can call an A2A agent. The gateway translates automatically. |
22
25
|**Signaling Relay**| Agents establish direct P2P connections via WebSocket signaling. |
0 commit comments