# yesmcp (remote · mcp.yesmcp.com)

See what an MCP connector can do for your business, get a scenario map, book a consultation.

- Trust score: 74/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-26

## Components

- remote · `mcp.yesmcp.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-yesmcp-connector/mcp.md), [page](https://verifymcp.io/servers/com-yesmcp-connector/mcp)

## Channel facts

- Endpoint: `https://mcp.yesmcp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (manage_booking).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1557 tokens (~141/item across 11 items; 8 tools + 3 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 42/100
  - Stability check failed: schema churn in the 22 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **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.
  - Structured output schemas are declared (38% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the yesmcp MCP server?

yesmcp is a hosted endpoint at https://mcp.yesmcp.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 com-yesmcp-connector 'https://mcp.yesmcp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-yesmcp-connector": {
      "url": "https://mcp.yesmcp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-yesmcp-connector": {
      "type": "http",
      "url": "https://mcp.yesmcp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-yesmcp-connector]
url = "https://mcp.yesmcp.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-yesmcp-connector --url 'https://mcp.yesmcp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-yesmcp-connector:
    url: "https://mcp.yesmcp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-yesmcp-connector": {
      "Transport": "http",
      "Url": "https://mcp.yesmcp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-yesmcp-connector -t streamable-http -u 'https://mcp.yesmcp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-yesmcp-connector": {
      "type": "http",
      "url": "https://mcp.yesmcp.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-09-25 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 29 to 32.

### 2026-09-21 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 22 to 25.

### 2026-09-19 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 15 to 19.

### 2026-09-17 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 9 to 12.

### 2026-09-15 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 2 to 5.

### 2026-09-11 (score 68, −3)

- [security regression] Stability: 0.20 → fail
- [security regression] A breaking change shipped without a version bump: still 0.1.0
- [security regression] Tool “cancel_booking” was removed
- [security regression] Tool “directory_census” was removed
- [security regression] Tool “reschedule_booking” was removed
- [security] New tool “manage_booking”, which the server declares destructive
- [functional improvement] Schema quality: 1813 → 1557
- [functional improvement] Tool coverage: 30% → 38%

### 2026-09-09 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (8)

### `list_availability` (~306 tokens)

List available consultation windows

Lists yesmcp's genuinely bookable consultation windows — only real, future, unclaimed slots. Use it before book_consult; the `slotId` of the window the user picks is what book_consult needs. Times are returned in yesmcp's timezone with an explicit UTC offset (for example `2026-08-27 14:00 CEST (UTC+2)`). Before you confirm anything with the user, ask which timezone or city they are in, then state the slot in BOTH their timezone and yesmcp's. Never show a bare wall-clock time. If nothing is open in the period asked about, the tool names the next available window instead of returning an empty list. Directory reviewers: pass `review_access` with the token from the submitted test-prompt list to see the seeded [TEST] reviewer windows instead of real availability. Do not use it for real users.

Input parameters:

- `from` (string): Earliest date to consider, `YYYY-MM-DD` or a full ISO-8601 UTC timestamp.
- `limit` (integer): How many windows to return at most. Defaults to 8.
- `review_access` (string): Directory-review test parameter (R20). The documented token switches this listing to the seeded reviewer windows, which are separate from real availability. Omit it for real users.
- `to` (string): Latest date to consider, `YYYY-MM-DD` or a full ISO-8601 UTC timestamp.

### `book_consult` (~309 tokens)

Book a consultation

Books one of yesmcp's consultation windows for the user. Requires the `slotId` from list_availability plus the user's name, email address and the topic they want to discuss. Before calling this tool, tell the user in plain words what booking stores and why: yesmcp stores their name, their email address, and the topic they give — the name and email to hold the slot and send the confirmation, the topic to prepare for the call. Nothing else is collected. Only call this tool once the user has given you those three values knowingly. The booking is only committed once the confirmation email has actually been accepted by the mail provider — if it fails, nothing is stored and the window stays open. Times are returned in yesmcp's timezone with an explicit UTC offset (for example `2026-08-27 14:00 CEST (UTC+2)`). Before you confirm anything with the user, ask which timezone or city they are in, then state the slot in BOTH their timezone and yesmcp's. Never show a bare wall-clock time.

Input parameters:

- `email` (string, required): The user's email address; the confirmation is sent there.
- `name` (string, required): The user's name, as they want to be addressed.
- `slotId` (string, required): The `slotId` of the window, exactly as returned by list_availability.
- `topic` (string, required): What the user wants to discuss, in their own words. One or two sentences.

### `manage_booking` (~280 tokens)

Cancel or move a booking

Cancels an existing yesmcp consultation booking (`action: cancel`) or moves it to a different window keeping the same reference (`action: reschedule`). Both require the booking reference from the confirmation email AND the email address the booking was made with — ask the user for both before calling. A move additionally needs the `newSlotId` of the target window from list_availability, and is only committed once the new confirmation email is accepted; if it fails, the original time stays booked. Confirm with the user before cancelling: it cannot be undone (though they can always book a fresh window). Times are returned in yesmcp's timezone with an explicit UTC offset (for example `2026-08-27 14:00 CEST (UTC+2)`). Before you confirm anything with the user, ask which timezone or city they are in, then state the slot in BOTH their timezone and yesmcp's. Never show a bare wall-clock time.

Input parameters:

- `action` (string, required): What to do with the booking.
- `bookingId` (string, required): The booking reference, exactly as in the confirmation email.
- `email` (string, required): The email address the booking was made with.
- `newSlotId` (string): Only for `reschedule`: the `slotId` of the new window, as returned by list_availability.

### `get_services` (~78 tokens)

What yesmcp offers

Returns yesmcp's real services catalog: what is offered, how an engagement runs, and timeline expectations. Answer the user only from what this tool returns — do not add offerings, prices or delivery claims of your own. If the tool says the catalog is not published yet, say exactly that and point the user at the contact link it gives.

### `advise_scenarios` (~248 tokens)

Scenario playbook for a business type

Given a business type in the user's own words (for example `hair salon`, `restaurant`, `dental clinic`), returns yesmcp's curated playbook: what that business's customers could do inside AI chats, what the business's own team could run from their chat, what building it takes, and a concrete next step. When no playbook exists for the exact business type, the tool returns the closest one — say clearly that it is adjacent guidance and do NOT invent specifics for the business type the user named. Called without `answers`, the tool also returns two short intake questions: ask them as they are written, then call the tool again with the user's `answers` to get the scenario map with a feasibility verdict.

Input parameters:

- `answers` (object): The user's answers to the intake questions this tool returns when called without them. Any subset is accepted; pass only what the user actually said.
- `businessType` (string, required): The user's business type, in their own words.
- `focus` (string): Which half of the scenario map to show. Defaults to `both`; pass `customers` or `team` only when the user asked for one of them specifically.

Output parameters:

- `channelNote`: Derived only from `answers.customer_channel`; null when that answer was not given.
- `feasibility`: Derived only from `answers.systems`; null when that answer was not given.
- `focus` (string): Which shelves were asked for.
- `matchedStatus` (string): `adjacent` means the map is the closest playbook, not this vertical's own.
- `nextStep`: The playbook's own next step, or null.
- `shelves` (object): Playbook bullets, verbatim; the shelf the focus filtered out is empty.
- `vertical`: The matched playbook's human title, or null.

### `demo_walkthrough` (~75 tokens)

Reviewer walkthrough

Returns yesmcp's demo sequence: the exact prompts a reviewer can replay, the tool call each one maps to, and what each should return. Also gives the review-access token and the currently open [TEST] reviewer windows. Intended for directory reviewers and for anyone who wants a guided tour of this connector; it changes nothing.

### `booking_widget` (~107 tokens)

Open the booking calendar

Opens yesmcp's interactive booking calendar right in the chat: the user browses real free consultation windows, picks one and books it with a short form — name, email and topic are collected by the form itself. Prefer this tool over list_availability when the user wants to book or asks to see times, and this client can render interactive tools. The widget performs the booking through book_consult, so every booking rule still applies. Read-only by itself: opening the calendar stores nothing.

Output parameters:

- `slots` (array): Genuinely bookable windows, soonest first.
- `timezone` (string): yesmcp's own IANA timezone.

### `services_widget` (~92 tokens)

Show yesmcp's services

Shows yesmcp's services as an interactive card carousel right in the chat: what we build, hosting & monitoring, security, ownership. Each card lets the user book a scoping call without leaving the widget (through book_consult — every booking rule applies). Prefer this over get_services when the user asks what yesmcp does or offers and this client can render interactive tools. Read-only: browsing stores nothing.

Output parameters:

- `services` (array): yesmcp's service catalog, carousel order.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-yesmcp-connector/mcp#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 71
- 2026-09-18: 70
- 2026-09-17: 70
- 2026-09-16: 69
- 2026-09-15: 69
- 2026-09-14: 68
- 2026-09-13: 68
- 2026-09-12: 68
- 2026-09-11: 68
- 2026-09-10: 71
- 2026-09-09: 71
- 2026-09-08: 70
- 2026-09-07: 70
- 2026-09-06: 69
- 2026-09-05: 69
- 2026-09-04: 68

## Common questions

### What is the yesmcp MCP server?

yesmcp is an MCP server listed in the public MCP registry as com.yesmcp/connector. See what an MCP connector can do for your business, get a scenario map, book a consultation. This page covers its hosted endpoint (https://mcp.yesmcp.com/mcp).

### Is the yesmcp MCP server safe to use?

yesmcp scores 74 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 yesmcp MCP server expose?

yesmcp exposes 8 tools: list_availability, book_consult, manage_booking, get_services, advise_scenarios, and 3 more. Their descriptions and schemas cost roughly 1,495 tokens of context every time the server is loaded.

### Does the yesmcp MCP server require authentication?

No. We connected to yesmcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the yesmcp MCP server still maintained?

yesmcp is still listed as active in the MCP registry. We last reached this channel on 26 September 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://mcp.yesmcp.com/mcp
- Website: https://yesmcp.com/connect/
- Changelog RSS feed: https://verifymcp.io/servers/com-yesmcp-connector/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-yesmcp-connector/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-yesmcp-connector/mcp