get_directory_stats
Get overall directory health and stats: total services, breakdown by protocol/health/source, and sync timestamps. Example: "How many services are in the directory?"
LABSCO SUMMARY
One URL can be payable through more than one rail, and the directory says so on every record rather than making you cross-reference.
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.
What it is
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.
What you get
- 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.
Requirements
Nothing — no account, no key.
Setup effort
One command — npx -y @402index/mcp-server
USE CASES
01
Finding a paid API under a price ceiling that is currently up
Price, protocol and health are all filters on the same search, so a result list does not need to be checked for availability afterwards.
02
Choosing between the payment rails a service supports
The sibling entries for the same URL come attached to both the search result and the detail record, so the comparison is one lookup.
03
Seeing what kinds of paid API exist at all
Category counts and the directory totals together say where the supply actually is before a search is worth narrowing.
4 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
get_service_detail
Get full details for a single service including health check history, pricing, and schema information. Includes related_services array with sibling payment rail details.
list_categories
List all service categories with counts. Example: "What categories of paid APIs are available?"
search_services
Search and filter paid API services in the 402 Index directory. Returns services with health status, pricing, and protocol info. Includes related_protocols array showing other payment rails for the same URL.
BEFORE YOU INSTALL
What to know first
Tools you get
4 tools when we connected.
Requires
- npx on PATH
- npm [@402
CONTEXT COST
Light Standing cost
Rated by the size of the 4 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"402index": {
"command": "npx",
"args": [
"-y",
"@402index/mcp-server"
]
}
}
}npx
TERMINAL
npx -y @402index/mcp-server
