Registries & Distribution

Delx treats discovery as infrastructure. The goal is one canonical source of truth, then broad syndication across the directories and registries that matter to builders, orchestrators, and payment-aware agents.

Live now

• Official MCP Registry server ID: io.github.davidmosiah/delx-mcp-a2a
• MCP server card: https://api.delx.ai/.well-known/mcp/server-card.json
• Agent card: https://api.delx.ai/.well-known/agent-card.json
• Capabilities: https://api.delx.ai/.well-known/delx-capabilities.json
• Specs: https://api.delx.ai/spec/openapi.json, https://api.delx.ai/spec/a2a.json, https://api.delx.ai/spec/mcp.json

x402 Bazaar status

Delx already exposes Bazaar metadata in production, and Coinbase Bazaar already indexes the three HTTP premium endpoints for controller-brief, incident-rca, and fleet-summary. The newer 1-cent tools get_recovery_action_plan and get_session_summary do not appear in Bazaar because they are MCP-only today.

Next syndication targets

1. GitHub MCP Registry for one-click builder installs.
2. Docker MCP Registry / MCP Catalog for infra-native distribution.
3. Postman MCP Library for API-network discovery.
4. A2A Registry / Gemini Enterprise for controller-first multi-agent exposure.
5. Kong MCP Registry for governed enterprise environments.
6. Community directories as secondary SEO and builder-discovery channels.

Submission checklist

• Keep server-card.json, specs, and capabilities in sync with production.
• Prefer operational names in discovery surfaces; keep therapy-era names as aliases only.
• Ensure at least one live premium endpoint is verifiably payable over x402.
• Publish benchmark and controller-outcome pages so registry reviewers can see proof-of-value quickly.

Recommended builder path

1. Read Discovery
2. Use https://api.delx.ai/api/v1/discovery/lean
3. Call quick_operational_recovery first
4. Deepen only if the recovery loop proves useful