Nexus – Agent economy protocol built on A2A and MCP
A2A + MCP agent marketplace, but the whole category is pre-revenue speculation.

SSL Labs for AI agents, but tied to Google's early-stage A2A protocol.
AI agent developers building on Google's A2A protocol
SSL Labs · SecurityHeaders.com
I built A2Apex (https://a2apex.io) — a testing and reputation platform for AI agents built on Google's A2A protocol.
The problem: AI agents are everywhere, but there's no way to verify they actually work. No standard testing. No directory of trusted agents. No reputation system.
What A2Apex does:
- Test — Point it at any A2A agent URL. We run 50+ automated compliance checks: agent card validation, live endpoint testing, state machine verification, streaming, auth, error handling.
- Certify — Get a 0-100 trust score with Gold/Silver/Bronze badges you can embed in your README or docs.
- Get Listed — Every tested agent gets a public profile page in the Agent Directory with trust scores, skills, test history, and embeddable badges.
Think of it as SSL Labs (testing) + npm (directory) + LinkedIn (profiles) — for AI agents.
Stack: Python/FastAPI, vanilla JS, SQLite. No frameworks, no build tools. Runs on a Mac mini in Wyoming.
Free: 5 tests/month. Pro: $29/mo. Startup: $99/mo. Try it at https://app.a2apex.io
I'm a dragline operator at a coal mine — built this on nights and weekends using Claude. Would love feedback from anyone building A2A agents or thinking about agent interoperability.
A2A + MCP agent marketplace, but the whole category is pre-revenue speculation.
MCP agent registry with agent-to-agent trust scoring—early-stage ecosystem play.
Finds shadow IT subdomains via CT logs without needing DNS access.
EigenTrust propagation for HN expert ranking beats black-box relevance scores.
Agent demo on Base L2 but demo page is static mockup—no live agent execution visible, unclear differentiation.
Git worktree isolation lets agents test instruction changes without breaking other sites—clever regression prevention.