# MCP Yellow Pages (remote · api.mcpyp.com)

Find and evaluate MCP servers: search the independent MCP Yellow Pages directory.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.mcpyp.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/mcpyellowpages-mcpyp/api.md), [page](https://verifymcp.io/servers/mcpyellowpages-mcpyp/api)

## Channel facts

- Endpoint: `https://api.mcpyp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 80/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http mcpyellowpages-mcpyp 'https://api.mcpyp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mcpyellowpages-mcpyp": {
      "url": "https://api.mcpyp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mcpyellowpages-mcpyp": {
      "type": "http",
      "url": "https://api.mcpyp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.mcpyellowpages-mcpyp]
url = "https://api.mcpyp.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mcpyellowpages-mcpyp": {
      "type": "remote",
      "url": "https://api.mcpyp.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mcpyellowpages-mcpyp --url 'https://api.mcpyp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mcpyellowpages-mcpyp:
    url: "https://api.mcpyp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mcpyellowpages-mcpyp": {
      "Transport": "http",
      "Url": "https://api.mcpyp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mcpyellowpages-mcpyp -t streamable-http -u 'https://api.mcpyp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "mcpyellowpages-mcpyp": {
      "type": "http",
      "url": "https://api.mcpyp.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-04 (score 70)

First indexed and scored.

## MCP tools (6)

### `find_mcp` (~121 tokens)

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.

Input parameters:

- `limit` (integer): Maximum number of results, default 10, max 100
- `query` (string, required): What the MCP should do, e.g. 'send email', 'stock prices', 'github issues'

### `get_mcp` (~65 tokens)

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.

Input parameters:

- `name` (string, required): Server name or slug from find_mcp results

### `get_config` (~97 tokens)

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.

Input parameters:

- `journey_id` (string): Same journey_id as the pick step
- `name` (string, required): Server name or slug from find_mcp results

### `explore` (~144 tokens)

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.

Input parameters:

- `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, required): What the MCP should do

### `refine` (~139 tokens)

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.

Input parameters:

- `journey_id` (string): Same journey_id as the explore step
- `no_key_required` (boolean): Only servers usable without a publisher API key
- `query` (string, required): What the MCP should do, refined from explore

### `pick` (~143 tokens)

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.

Input parameters:

- `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

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mcpyellowpages-mcpyp/api#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://api.mcpyp.com/mcp
- Website: https://mcpyp.com/
- Changelog RSS feed: https://verifymcp.io/servers/mcpyellowpages-mcpyp/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/mcpyellowpages-mcpyp/api.json
- HTML version of this page: https://verifymcp.io/servers/mcpyellowpages-mcpyp/api