We built a searchable registry for AI agents and MCP servers, powered by an open protocol called ADP (Agent Discovery Protocol).
The problem: AI agents are proliferating but there's no standardized way to discover them. You can't search for "agents that can query PostgreSQL" or "payment processing agents" and get ranked results with trust metrics.
What we built:
Semantic search using vector embeddings (all-MiniLM-L6-v2) to find agents by capability
Trust infrastructure: verification badges, health monitoring, security scoring (0-100), user reviews
Open protocol: ADP v2.0 defines a standardized manifest format (like package.json for npm, but for agents)
Multi-protocol support: REST, MCP, gRPC, GraphQL, WebSocket
How it works:
Agents publish ADP manifests at /.well-known/agent.json:
json{
"aid": "aid://example.com/my-agent@1.0.0",
"name": "My Agent",
"capabilities": [{
"name": "query_database",
"description": "Execute SQL queries",
"input_schema": {...},
"output_schema": {...}
}],
"security": {
"certifications": ["SOC2"],
"data_policy": "zero_retention"
}
}
Registry crawls these manifests (or accepts direct registration), generates embeddings, and makes them searchable.
Tech stack:
Backend: FastAPI + PostgreSQL with pgvector
Frontend: Next.js 14
Search: Sentence transformers for embedding generation
Deployment: Nginx + PM2
Current status:
51 agents indexed (ChatGPT, Claude Code, Gemini, major MCP servers)
API at /v1/agents, /v1/search, /v1/register
Open source ADP spec
What's interesting technically:
Federation design: Any organization can run an ADP-compliant registry. Agents aren't locked to our platform.
Trust without centralization: Security scores aggregate multiple signals (certs, uptime, reviews) but agents control their own manifests.
Semantic search on capabilities: Not just keyword matching—understanding what agents can actually do.
Known limitations:
Health monitoring is on-demand, not continuous (working on background jobs)
Security scoring is relatively basic (need more sophisticated threat modeling)
Federation protocol is planned but not implemented yet
Limited to agents that publish manifests (can't auto-discover arbitrary APIs)
cjohnsonpr•2mo ago
Semantic search using vector embeddings (all-MiniLM-L6-v2) to find agents by capability Trust infrastructure: verification badges, health monitoring, security scoring (0-100), user reviews Open protocol: ADP v2.0 defines a standardized manifest format (like package.json for npm, but for agents) Multi-protocol support: REST, MCP, gRPC, GraphQL, WebSocket
How it works: Agents publish ADP manifests at /.well-known/agent.json: json{ "aid": "aid://example.com/my-agent@1.0.0", "name": "My Agent", "capabilities": [{ "name": "query_database", "description": "Execute SQL queries", "input_schema": {...}, "output_schema": {...} }], "security": { "certifications": ["SOC2"], "data_policy": "zero_retention" } } Registry crawls these manifests (or accepts direct registration), generates embeddings, and makes them searchable. Tech stack:
Backend: FastAPI + PostgreSQL with pgvector Frontend: Next.js 14 Search: Sentence transformers for embedding generation Deployment: Nginx + PM2
Current status:
51 agents indexed (ChatGPT, Claude Code, Gemini, major MCP servers) API at /v1/agents, /v1/search, /v1/register Open source ADP spec
What's interesting technically:
Federation design: Any organization can run an ADP-compliant registry. Agents aren't locked to our platform. Trust without centralization: Security scores aggregate multiple signals (certs, uptime, reviews) but agents control their own manifests. Semantic search on capabilities: Not just keyword matching—understanding what agents can actually do.
Known limitations:
Health monitoring is on-demand, not continuous (working on background jobs) Security scoring is relatively basic (need more sophisticated threat modeling) Federation protocol is planned but not implemented yet Limited to agents that publish manifests (can't auto-discover arbitrary APIs)
Why this matters: As agentic AI becomes more common, we need discovery infrastructure. Right now, finding agents requires GitHub searches or word-of-mouth. This is like trying to find websites before search engines existed. Live demo: https://agentic-exchange.metisos.co ADP spec: https://github.com/metisos/adp-protocol API docs: https://agentic-exchange.metisos.co/develop