# MCP Near Me (remote · mcpnear.com)

Find participating local service providers and book live appointment times.

- Trust score: 70/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `mcpnear.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-voicedispatcher-mcp-near-me/mcpnear.md), [page](https://verifymcp.io/servers/com-voicedispatcher-mcp-near-me/mcpnear)

## Channel facts

- Endpoint: `https://mcpnear.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.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-10-23.

- **Endpoint Security**: 57/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 (create_service_booking).
  - 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**: 42/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1906 tokens (~86/item across 22 items; 12 tools + 10 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 75/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 14% of tool parameters carry a description.
  - Structured output schemas are declared (100% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the MCP Near Me server?

MCP Near Me is a hosted endpoint at https://mcpnear.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-voicedispatcher-mcp-near-me 'https://mcpnear.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-voicedispatcher-mcp-near-me": {
      "url": "https://mcpnear.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-voicedispatcher-mcp-near-me": {
      "type": "http",
      "url": "https://mcpnear.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-voicedispatcher-mcp-near-me]
url = "https://mcpnear.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-voicedispatcher-mcp-near-me": {
      "type": "remote",
      "url": "https://mcpnear.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-voicedispatcher-mcp-near-me --url 'https://mcpnear.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-voicedispatcher-mcp-near-me:
    url: "https://mcpnear.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-voicedispatcher-mcp-near-me": {
      "Transport": "http",
      "Url": "https://mcpnear.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-voicedispatcher-mcp-near-me -t streamable-http -u 'https://mcpnear.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-voicedispatcher-mcp-near-me": {
      "type": "http",
      "url": "https://mcpnear.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-10-23 (score 70, 0)

- [security] Resource “near-me-service-request” now points somewhere else: ui://near-me/service-request-v9.html → ui://near-me/service-request-v11.html
- [security] Resource “near-me-service-request-compatibility-1” now points somewhere else: ui://near-me/service-request-v8.html → ui://near-me/service-request-v10.html
- [security] Resource “near-me-service-request-compatibility-2” now points somewhere else: ui://near-me/service-request-v7.html → ui://near-me/service-request-v9.html
- [security] Resource “near-me-service-request-compatibility-3” now points somewhere else: ui://near-me/service-request-v6.html → ui://near-me/service-request-v8.html
- [security] Resource “near-me-service-request-compatibility-4” now points somewhere else: ui://near-me/service-request-v5.html → ui://near-me/service-request-v7.html
- [security] Resource “near-me-service-request-compatibility-5” now points somewhere else: ui://near-me/service-request-v4.html → ui://near-me/service-request-v6.html
- [security] Resource “near-me-management” now points somewhere else: ui://near-me/management-v3.html → ui://near-me/management-v4.html
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_my_service_booking” rewrote its description, which is the text the model reads
- [functional] New resource “near-me-management-compatibility-1”
- [functional] New resource “near-me-service-request-compatibility-6”
- [functional] New resource “near-me-service-request-compatibility-7”

### 2026-10-22 (score 70, 0)

- [security] Stability: 0.97 → pass
- [security] Resource “near-me-service-request” now points somewhere else: ui://near-me/service-request-v7.html → ui://near-me/service-request-v9.html
- [security] Resource “near-me-service-request-compatibility-1” now points somewhere else: ui://near-me/service-request-v6.html → ui://near-me/service-request-v8.html
- [security] Resource “near-me-service-request-compatibility-2” now points somewhere else: ui://near-me/service-request-v5.html → ui://near-me/service-request-v7.html
- [security] Resource “near-me-service-request-compatibility-3” now points somewhere else: ui://near-me/service-request-v4.html → ui://near-me/service-request-v6.html
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_service_options” rewrote its description, which is the text the model reads
- [security] Tool “render_service_request_form” rewrote its description, which is the text the model reads
- [security] Tool “start_service_request” rewrote its description, which is the text the model reads
- [security] Tool “update_service_request” rewrote its description, which is the text the model reads
- [functional] New resource “near-me-service-request-compatibility-4”
- [functional] New resource “near-me-service-request-compatibility-5”
- [cosmetic] “render_service_request_form” added an optional parameter “option_key”

### 2026-10-20 (score 70, +1)

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

### 2026-10-18 (score 69, +1)

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

### 2026-10-16 (score 68, +1)

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

### 2026-10-14 (score 67, +1)

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

### 2026-10-12 (score 66, +1)

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

### 2026-10-10 (score 65, +1)

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

## MCP tools (12)

### `start_service_request` (~119 tokens)

Start a service request

Start a new supported service request immediately with the user's full intent and known public facts. Returns the vertical introduction and next intake/matching step, including availability when intake is complete; no separate lookup is needed. Use provider_hint only for an explicitly named company.

Input parameters:

- `answers` (object)
- `idempotency_key` (string, required)
- `provider_hint`
- `user_intent` (string, required)
- `vertical_hint` (string): Optional exact live vertical ID. Omit it when uncertain and let the server classify user_intent.

Output parameters:

- `result`

### `update_service_request` (~111 tokens)

Update a service request

Submit supplied answers and any chosen selected_time_key with the latest expected_state_version. Omitted optional/conditional fields do not block progress. Returns the updated next_action and current availability; continue directly without get_service_options. choose_service_provider means ask for a company before opening its protected contact card.

Input parameters:

- `answers` (object)
- `expected_state_version` (integer, required)
- `explicitly_unknown_field_ids` (array)
- `idempotency_key` (string, required)
- `request_id` (string, required)

Output parameters:

- `result`

### `get_service_options` (~61 tokens)

Get current service options

Refresh availability only when needed, such as when the user asks to check again. start_service_request and update_service_request already return current matching data. Returns aggregated windows and refinement fields without selecting a company or reserving capacity.

Input parameters:

- `request_id` (string, required)

Output parameters:

- `result`

### `render_service_request_form` (~132 tokens)

Open the final service confirmation card

Open the protected contact/terms/Confirm card only after company choice. Pass the explicitly chosen company's option_key from current service_options; omit it only for a single option or a previously selected company. First give at most one short introductory sentence, then call this tool as the last action and end the reply. Do not write anything after the card: it owns all subsequent instructions, progress and receipt.

Input parameters:

- `option_key` (string): Exact option_key from this request's current service_options for the company explicitly chosen by the user. Never infer a choice from price or ordering.
- `request_id` (string, required)

Output parameters:

- `result`

### `select_service_option` (~93 tokens)

Select a company in the final card

Use only from the final protected card when the user selects one exact provider option. It rechecks availability, releases any previous selection, creates one temporary hold for the selected company, and returns its protected booking schema. It does not create a booking.

Input parameters:

- `expected_state_version` (integer, required)
- `idempotency_key` (string, required)
- `option_key` (string, required)
- `request_id` (string, required)

Output parameters:

- `result`

### `create_service_booking` (~127 tokens)

Create the confirmed service booking

Use only from the protected final card with its one-time authorization after the user presses Confirm. Provider, request, hold, time and protected answers come from server context; do not pass or reconstruct them. This anonymous action completes the booking and must not trigger Connect or phone verification. Safe retries must reuse the same idempotency key.

Input parameters:

- `anonymous_session_id` (string, required)
- `booking_authorization_token` (string, required)
- `campaign_id` (string)
- `correlation_id` (string, required)
- `idempotency_key` (string, required)
- `source` (string, required)

Output parameters:

- `result`

### `complete_account_link` (~64 tokens)

Finish saving booking details

Compatibility-only completion for an explicitly initiated legacy profile-link session. Never call it as part of a new booking and never ask for an SMS code in chat. Viewing or managing an existing appointment starts Connect through the corresponding booking-management tool.

Input parameters:

- `linking_session_id` (string, required)

Output parameters:

- `result`

### `list_my_service_bookings` (~128 tokens)

List my appointments

Use immediately when the user asks to see or manage appointments. For cancellation or rescheduling, pass status='active'. Active means a confirmed or rescheduled appointment whose arrival window has not ended; past or terminal bookings are never active. If multiple active appointments are returned, show the choices instead of guessing. Connect is handled by the platform; never ask for a phone or code in chat.

Input parameters:

- `limit` (integer)
- `status` (string): Use 'active' for cancellation or rescheduling. It returns only actionable appointments whose arrival window has not ended; omit to include history.

Output parameters:

- `result`

### `get_my_service_booking` (~92 tokens)

Open one of my appointments

Open an appointment that belongs to the connected customer. This is read-only. Historical appointments have no management actions. Give at most one short introductory sentence before calling this tool as the last action, then end the reply: no summary, status, details or instructions after the card. The live card owns viewing, exact change review and completion.

Input parameters:

- `booking_id` (string, required)
- `intent` (string)

Output parameters:

- `result`

### `prepare_service_booking_change` (~128 tokens)

Review an exact appointment change

Use this only from the protected management form after secure appointment access. It prepares the exact reschedule or cancellation review but does not change the booking. A reschedule accepts only a live slot returned inside the protected form and temporarily reserves that capacity. The user must separately confirm the exact preview before a write tool can run.

Input parameters:

- `action` (string, required)
- `booking_id` (string)
- `idempotency_key` (string, required)
- `management_context_token` (string): Opaque short-lived context supplied only by the protected management form.
- `new_slot_id` (string)

Output parameters:

- `result`

### `reschedule_service_booking` (~126 tokens)

Reschedule an approved appointment

Use this only with the one-time approval issued after the user confirms the exact reschedule inside the protected management form. It moves the existing booking to the reserved available time, preserves its prior-time history, frees the old capacity, and sends transactional notifications. Safe retries must reuse the same idempotency key.

Input parameters:

- `anonymous_session_id` (string, required)
- `booking_change_authorization_token` (string, required): One-time approval supplied only by the protected management form.
- `correlation_id` (string, required)
- `idempotency_key` (string, required)
- `source` (string, required)

Output parameters:

- `result`

### `cancel_service_booking` (~115 tokens)

Cancel an approved appointment

Use this only with the one-time approval issued after the user confirms the exact cancellation inside the protected management form. It cancels only the authorized active booking, frees its capacity, and sends transactional notifications. Safe retries must reuse the same idempotency key.

Input parameters:

- `anonymous_session_id` (string, required)
- `booking_change_authorization_token` (string, required): One-time approval supplied only by the protected management form.
- `correlation_id` (string, required)
- `idempotency_key` (string, required)
- `source` (string, required)

Output parameters:

- `result`

## Diagnostics

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

## Score history

- 2026-10-23: 70
- 2026-10-22: 70
- 2026-10-21: 70
- 2026-10-20: 70
- 2026-10-19: 69
- 2026-10-18: 69
- 2026-10-17: 68
- 2026-10-16: 68
- 2026-10-15: 67
- 2026-10-14: 67
- 2026-10-13: 66
- 2026-10-12: 66
- 2026-10-11: 65
- 2026-10-10: 65
- 2026-10-07: 64
- 2026-10-04: 62
- 2026-10-03: 62
- 2026-10-02: 61
- 2026-10-01: 61
- 2026-09-30: 60
- 2026-09-29: 60
- 2026-09-28: 59
- 2026-09-27: 59
- 2026-09-26: 58
- 2026-09-25: 58
- 2026-09-24: 58
- 2026-09-23: 57
- 2026-09-22: 57

## Common questions

### What is the MCP Near Me server?

MCP Near Me is listed in the public MCP registry as com.voicedispatcher/mcp-near-me. Find participating local service providers and book live appointment times. This page covers its hosted endpoint (https://mcpnear.com/mcp).

### Is the MCP Near Me server safe to use?

MCP Near Me 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 Near Me server expose?

MCP Near Me exposes 12 tools: start_service_request, update_service_request, get_service_options, render_service_request_form, select_service_option, and 7 more. Their descriptions and schemas cost roughly 1,296 tokens of context every time the server is loaded.

### Does the MCP Near Me server require authentication?

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

### Is the MCP Near Me server still maintained?

MCP Near Me is still listed as active in the MCP registry. We last reached this channel on 23 October 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://mcpnear.com/mcp
- Website: https://mcpnear.com/mcp-near-me
- Changelog RSS feed: https://verifymcp.io/servers/com-voicedispatcher-mcp-near-me/mcpnear.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-voicedispatcher-mcp-near-me/mcpnear.json
- HTML version of this page: https://verifymcp.io/servers/com-voicedispatcher-mcp-near-me/mcpnear