Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
An open protocol for discovering A2A-capable AI agents on local networks — the discovery & trust bootstrap layer beneath A2A (mDNS/DNS-SD, well-known endpoints, signed AgentCards).
| Date | Stars |
|---|---|
| 2026-07-31 | 262 |
| 2026-08-11 | 261 |
| 2026-08-18 | 259 |
| 2026-08-20 | 258 |
| 2026-08-26 | 257 |
| 2026-08-27 | 256 |
| 2026-08-28 | 255 |
| 2026-09-05 | 254 |
| 2026-09-10 | 253 |
| 2026-09-17 | 252 |
| 2026-09-20 | 253 |
| 2026-09-21 | 252 |
| 2026-09-23 | 251 |
| 2026-10-15 | 250 |
| 2026-10-24 | 245 |
| 2026-11-04 | 245 |
Today
— stars today
This week
— stars this week
This month
-6 stars this month
Momentum
0.0
growth rate 0.00%/day
<p align="center"> <img src="assets/logo.png" alt="LAD-A2A Logo" width="120"> </p> <h1 align="center">Local Agent Discovery for A2A (LAD-A2A)</h1> <p align="center"> <a href="LICENSE"><img src="https://img.shields.io/badge/License-Apache_2.0-blue.svg" alt="Apache License"></a> <a href="https://github.com/franzvill/lad/actions/workflows/tests.yml"><img src="https://github.com/franzvill/lad/actions/workflows/tests.yml/badge.svg" alt="Tests"></a> <a href="spec/spec.md"><img src="https://img.shields.io/badge/spec-draft-orange.svg" alt="Spec Version"></a> <a href="https://lad-a2a.org"><img src="https://img.shields.io/badge/docs-lad--a2a.org-blue.svg" alt="Documentation"></a> </p> <p align="center"><strong>An open protocol for discovering A2A-capable agents on local networks.</strong></p> LAD-A2A addresses a critical gap in the AI agent ecosystem: when a device joins a network—hotel Wi-Fi, office LAN, cruise ship, hospital campus—how does the user's AI assistant discover and connect to local agents? While [A2A](https://a2a-protocol.org) defines agent-to-agent communication and [MCP](https://modelcontextprotocol.io) defines agent-to-tool integration, **LAD-A2A defines agent discovery**. With LAD-A2A, agents can: - **Automatically discover** local A2A agents when joining a network - **Verify identity** through signed AgentCards and DIDs - **Obtain user consent** before establishing connections - **Negotiate capabilities** via standard A2A mechanisms ## See It In Action <div align="center"> https://github.com/user-attachments/assets/a6a06e95-729b-465a-857c-6a87da52b302 <em>Real mDNS discovery → LAD-A2A protocol → A2A JSON-RPC communication</em> </div> ## Why LAD-A2A? AI agents are increasingly capable, but they remain isolated from their physical environment. A guest's AI assistant has no way to discover the hotel's concierge agent. An employee's assistant can't find the building's room booking agent. A patient's assistant doesn't know the hospital offers a wayfinding agent. LAD-A2A solves this by providing: - **Zero-Configuration Discovery:** Agents find each other automatically via mDNS/DNS-SD (`_lad-a2a._tcp`) and well-known endpoints. - **An honest trust model:** Local networks are hostile by default. LAD-A2A carefully separates *channel authentication* (TLS proves you reached the host in the URL) from *identity verification* (domain/JWS/DID anchored to the org). TLS to an attacker-chosen host proves nothing about identity — see the **[Trust Model](https://lad-a2a.org/trust-model/)**. - **Explicit user consent:** Human approval before first contact, keyed to a verified identity — never auto-approved. - **Ecosystem Alignment:** LAD-A2A only handles discovery—once an agent is verified and approved, standard A2A communication takes over. ## How It Fits <p align="center"> <img src="assets/protocol-triangle.png" alt="Protocol Stack: LAD-A2A → A2A → MCP" width="350"> </p> | Protocol | Role | Specification | |----------|------|---------------| | **LAD-A2A** | Discovery & Trust Bootstrap | [lad-a2a.org](https://lad-a2a.org) | | **A2A** | Agent-to-Agent Communication | [a2a-protocol.org](https://a2a-protocol.org) | | **MCP** | Agent-to-Tools/Data | [modelcontextprotocol.io](https://modelcontextprotocol.io) | LAD-A2A is the **first handshake**. It answers "who's here?" so that A2A can answer "what can you do?" and MCP can answer "how do I do it?" ## Discovery Mechanisms LAD-A2A supports multiple discovery paths with automatic fallback: | Mechanism | Environment | Description | |-----------|-------------|-------------| | **mDNS/DNS-SD** | LAN, Consumer Wi-Fi | Zero-config discovery via the LAD-owned `_lad-a2a._tcp` service type | | **Well-Known Endpoint** | Captive Portals, Web | `/.well-known/lad/agents` on the network domain | | **DHCP Option** | Enterprise Networks | Custom option containing discovery URL | | **QR/NFC** | Physical Fallback | Direct link to AgentCard for restricted networks | ## Getting St
Excerpt of 8,172 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:2b0029ccce9dbd10, llm:Repository topics and description: 'agent-discovery, ai-agents, mcp, mdns, protocol-specification, service-discovery, zeroconf' and description: 'An open protocol for discovering A2A-capable AI agents on local networks — the discovery & trust bootstrap layer beneath A2A (mDNS/DNS-SD, well-known endpoints, signed AgentCards).'
matched fp:2b0029ccce9dbd10, llm:Repository topics and description: 'agent-discovery, ai-agents, mcp, mdns, protocol-specification, service-discovery, zeroconf' and description: 'An open protocol for discovering A2A-capable AI agents on local networks — the discovery & trust bootstrap layer beneath A2A (mDNS/DNS-SD, well-known endpoints, signed AgentCards).'