Categories › AI & Agents › Models, LLM APIs, routing, serving, training & GPUs
Agent-native registry to discover APIs, MCP servers and CLIs, with live health checks.
Remote server: your requests and data go to agentnexus.app. Claude Code: claude mcp add --transport http agent-nexus https://agentnexus.app/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
discover_capabilities — Call this first whenever a task needs an external service (email, payments, search, storage, LLMs, data...) or when a service you use is faisearch_registry — Keyword lookup in the Agent Nexus registry when you already know what to look for: a product name, vendor, slug or endpoint fragment, optionget_entry — Fetches the full record of ONE approved registry entry whose exact slug you already have, e.g. from a previous discover_capabilities, searchlist_categories — Return the fixed taxonomy of Agent Nexus: the three interface layers it indexes ('api', 'mcp', 'cli'), each with a label, a one-line definitlist_entries — Enumerate the whole approved catalogue in deterministic slug order, page by page — use this when you want everything (mirroring, auditing, bsubmit_entry — Register a new interface (HTTP API, MCP server or CLI) in the Agent Nexus catalogue. Callers authenticate either as a signed-in member or wiNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.