io.github.MCPYellowPagesPublished by GitHub account MCPYellowPagesv1.0.2Updated Nov 5, 2026
Find and evaluate MCP servers: search the independent MCP Yellow Pages directory.
Remote MCP directory server that lets an assistant search, inspect and compare measured MCP servers and get ready-to-paste client configs.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.MCPYellowPages%2Fmcpyp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Add this to your client's mcpServers config.
{
"mcpServers": {
"yellow-pages": {
"type": "http",
"url": "https://api.mcpyp.com/mcp"
}
}
}Search the MCP Yellow Pages measured catalog. Start here to discover MCP servers for a task. Returns servers ranked by content match, then by independently measured quality (liveness, deep-test results, tool counts). Every result was actually probed by MCPYP; requires_key tells you whether the server needs a publisher API key before use.
limitqueryrequiredGet the full measured profile of one MCP server: description, measured tool list with parameters, liveness and deep-test outcomes, endpoint region. Use after find_mcp to inspect a candidate before connecting.
namerequiredGet a ready-to-paste client configuration for one MCP server. If the server requires a publisher API key, the config contains a placeholder plus where to obtain the key; MCPYP never issues or stores keys. Pass the same journey_id as the pick step so the funnel conversion is logged.
namerequiredjourney_idStep 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.
limitqueryrequiredoffsetjourney_idStep 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.
queryrequiredjourney_idno_key_requiredStep 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.
namequeryjourney_id83% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.