MCP Yellow Pages
REMOTE · API.MCPYP.COM
Find and evaluate MCP servers: search the independent MCP Yellow Pages directory.
Available components
Last scanned (5 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Search and Retrieval
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 709 tokens (~118/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Nov 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://api.mcpyp.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpyp.com | CN=YE1,O=Let's Encrypt,C=US | 19 Oct 2026 | 17 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 614c2e74ff47d4f3cc2caf8b83c887c2e30 |
| SANs: *.mcpyp.com, mcpyp.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.mcpyp.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mcpyp.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.mcpyp.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.mcpyp.com/mcp | HTTPS enforced | 301 | https://api.mcpyp.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
explore ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | – | Optional client-chosen id linking this journey's steps |
| limit | integer | – | Pool size, default 20, max 100 |
| offset | integer | – | Page offset into the ranked pool |
| query | string | yes | What the MCP should do |
No output schema declared.
No examples provided.
find_mcp ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results, default 10, max 100 |
| query | string | yes | What the MCP should do, e.g. 'send email', 'stock prices', 'github issues' |
No output schema declared.
No examples provided.
get_config ~97
Get 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.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | – | Same journey_id as the pick step |
| name | string | yes | Server name or slug from find_mcp results |
No output schema declared.
No examples provided.
get_mcp ~65
Get 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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Server name or slug from find_mcp results |
No output schema declared.
No examples provided.
pick ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | – | Same journey_id as the earlier steps |
| name | string | – | Server name or slug from the refine step, when committing to a specific server |
| query | string | – | Task query, when picking the top-ranked server |
No output schema declared.
No examples provided.
refine ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| journey_id | string | – | Same journey_id as the explore step |
| no_key_required | boolean | – | Only servers usable without a publisher API key |
| query | string | yes | What the MCP should do, refined from explore |
No output schema declared.
No examples provided.
How do I install the MCP Yellow Pages server?
MCP Yellow Pages is a hosted endpoint at https://api.mcpyp.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.mcpyp.com
claude mcp add --transport http mcpyellowpages-mcpyp 'https://api.mcpyp.com/mcp'
What is the MCP Yellow Pages server?
MCP Yellow Pages is listed in the public MCP registry as io.github.MCPYellowPages/mcpyp. Find and evaluate MCP servers: search the independent MCP Yellow Pages directory. This page covers its hosted endpoint (https://api.mcpyp.com/mcp).
Is the MCP Yellow Pages server safe to use?
MCP Yellow Pages scores 70 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MCP Yellow Pages server expose?
MCP Yellow Pages exposes 6 tools: find_mcp, get_mcp, get_config, explore, refine, pick. Their descriptions and schemas cost roughly 709 tokens of context every time the server is loaded.
Does the MCP Yellow Pages server require authentication?
No. We connected to MCP Yellow Pages without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MCP Yellow Pages server still maintained?
MCP Yellow Pages is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.