Eviduct — Independent MCP Discovery

Each tool occupies a distinct layer: aggregate network status, single-server metadata retrieval, and registry-wide search. There is no overlap — one is global/statistical, one is per-entity lookup, one is query-based discovery — and the descriptions explicitly delineate what each does not do.

All three follow a clean verb_noun snake_case pattern (get_* , get_*, search_*), with the entity clearly embedded in the name. No mixed conventions or vague verbs.

Three tools is a tight, well-earned surface for a discovery/index server: find (search), inspect (metadata), and orient (status). Nothing feels padded or redundant, and each covers a necessary step in the discovery workflow.

The core discovery loop — search, then fetch metadata, with a status/health reference point — is fully covered, and the tools are carefully scoped to avoid implying verification. Minor gaps exist: no way to enumerate categories/provider listings or to retrieve per-server observed-check detail beyond the aggregate.