MCP Yellow Pages
io.github.MCPYellowPages/mcpypMCPYellowPagesstreamable-httpv1.0.2Scanned
Find and evaluate MCP servers: search the independent MCP Yellow Pages directory.
6 tools: 3 change things and 3 only read.
- Reads private data · 1
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the MCP Yellow Pages can do
The MCP Yellow Pages is published by the GitHub account MCPYellowPages. It has 6 tools. It can create or change data (3 tools: explore, refine and pick), but cannot delete data. 3 tools only read.
1 tool reads private data (get_config); 1 tool brings in text other people can write (get_config).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 18, 2026, version 1.0.2.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
exploreStep 1 of the MCPYP selection funnel (broad search).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
pickStep 3 of the MCPYP selection funnel (final selection).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
refineStep 2 of the MCPYP selection funnel (refined search).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
Only reads 3Show 3 read-only tools
find_mcpSearch the MCP Yellow Pages measured catalog — the entry point for finding an MCP server.No findings
Why it is in this group
- The name "find_mcp" says "find": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
get_configGet 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/#/fin…Reads private dataReads text others writeNo findings
Why it is in this group
- The name "get_config" says "get": a word for reading.
What it can reach
- private-dataThe description's first sentence says "get" and "doc": it reads documents.
- untrusted-inputThe description's first sentence says "get" and "http": it reads web pages, which anyone can write.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
get_mcpGet the full measured profile of one MCP server: description, measured tool list with parameters, liveness and deep-test outcomes, key status, endpoint and region.No findings
Why it is in this group
- The name "get_mcp" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 19, 2026, 17:23 UTC, unchanged since Nov 5, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.mcpyp.com/mcp: tools/list returned 6 tools to an anonymous client, including explore (write), refine (write), pick (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Install
Pinned to version 1.0.2. Values in angle brackets are yours to fill in.
claude mcp add --transport http mcpyp https://api.mcpyp.com/mcpclaude mcp add --transport http mcpyp https://api.mcpyp.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__mcpyp__find_mcp",
"mcp__mcpyp__get_mcp",
"mcp__mcpyp__get_config"
],
"ask": [
"mcp__mcpyp__explore",
"mcp__mcpyp__refine",
"mcp__mcpyp__pick"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as mcpyp. Review it before you use it.
Capability tags behind 1 rule
- mcp__mcpyp__get_config private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.MCPYellowPages/mcpyp/verify?hash=63e53f5e6182316fea9624e4b70eedd6a4be071ffd8cef841e518dfc23db308f" | jq -e '.changed == false'Pinned hash 63e53f5e6182, from Nov 18, 2026, 16:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.MCPYellowPages/mcpyp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.MCPYellowPages/mcpyp)Source: MCP Registry. Synced Nov 4, 2026, 23:17 UTC.
MCP Yellow Pages: questions and answers
Answered from the scan above, not from the publisher's description.
Is the MCP Yellow Pages safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the MCP Yellow Pages delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the MCP Yellow Pages do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the MCP Yellow Pages have?
- 6 tools: 3 write, 3 read. explore, refine, pick, find_mcp, get_mcp and get_config.
Does the MCP Yellow Pages need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the MCP Yellow Pages send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the MCP Yellow Pages changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 18, 2026. Every change is on this page and in its Atom feed.