related_protocols on a search hit and related_services on a detail record both point at the sibling entries for the same URL, which is the difference between finding a paid API and finding a way you can actually pay it. Health is a filter here rather than a footnote — search_services takes it directly and get_service_detail returns the check history behind it — and get_directory_stats carries the sync timestamps, so how current that health picture is can be checked instead of assumed.
A client for the 402 Index directory with four tools: search paid API services with filters, read one service's full detail, list the categories with their counts, and read the directory's own health and sync statistics.
- search_services filters by category, protocol, health, max_price_usd, source, verified and featured, with sorting, ordering, field selection, output format and paging; each result carries a related_protocols array naming other payment rails for the same URL.
- get_service_detail returns one service's health check history, pricing and schema information, plus a related_services array with the sibling rails in full.
- list_categories returns every category with its count, optionally summarised.
- get_directory_stats returns totals broken down by protocol, health and source, together with the sync timestamps behind them.
Nothing — no account, no key.
One command — npx -y @402index/mcp-server