MCP Yellow Pages

Step 1 of the MCPYP selection funnel (broad search). Returns a broad pool of candidate servers for a task (default 20, paged with offset) plus the total match count. Use this first to see the shape of the pool, then narrow with refine. Pass the same journey_id across explore, refine, and pick so the journey is logged as one funnel. Optional no_key_required narrows the pool to servers usable without a publisher API key. Most callers can skip the funnel and use find_mcp + get_mcp instead.

Search the MCP Yellow Pages measured catalog — the entry point for finding an MCP server. Give a plain task description ('send email', 'stock prices', 'github issues') and get servers ranked by content match, then by independently measured quality (liveness, deep-test results, tool counts). Every result was actually probed by MCPYP. Usual flow: find_mcp to discover candidates, then get_mcp to inspect one, then get_config to connect. requires_key tells you whether the server needs a publisher API key before use. Set no_key_required=true to return only servers verified usable without a publisher API key (a successful keyless call on record).

Get a ready-to-paste client configuration for one MCP server: an mcpServers entry for your MCP client config, plus a docs link to the full 6-tool reference (https://mcpyp.com/#/find, For machines tab). If the server requires a publisher API key, the config contains a <YOUR_API_KEY> placeholder plus where to obtain the key; MCPYP never issues, stores, or brokers keys. Pass the same journey_id as the pick step so the funnel conversion is logged.

Get the full measured profile of one MCP server: description, measured tool list with parameters, liveness and deep-test outcomes, key status, endpoint and region. Call after find_mcp, with the name or slug from a find_mcp result, to inspect a candidate before connecting. The profile also carries profile_url (the public evidence page). MCPYP never proxies calls — use get_config to connect to the server yourself.

Step 3 of the MCPYP selection funnel (final selection). Commits to exactly ONE server: either the top-ranked server for a further-improved query, or the named server from the refine step. Keep improving the query: each step's query should be sharper than the last, so the journey shows how the choice narrowed. After pick, call get_config to connect. This is the funnel's conversion point. Optional no_key_required constrains the query pick to servers usable without a publisher API key; it does not apply when a server is picked by name (an explicit choice is picked as-is).

Step 2 of the MCPYP selection funnel (refined search). Narrows a task to exactly 5 candidates. IMPORTANT: improve the query at each step - use what explore returned (candidate names, tool names, categories) to write a sharper, more specific query here than the explore query. Optionally constrain to servers that need no publisher key (no_key_required). Call after explore, then commit with pick.