MCP Near Me
REMOTE · MCPNEAR.COM
Find participating local service providers and book live appointment times.
Available components
Last scanned (15 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 23 Oct 2026.
Category E-commerce
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (create_service_booking). See how to fix → View diagnostics → Fail
- 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 Usability42
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1906 tokens (~86/item across 22 items; 12 tools + 10 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 14% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
- 23 Oct 26 0
- 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 security
- 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” functional
- 22 Oct 26 0
- 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 security
- New resource “near-me-service-request-compatibility-4” functional
- New resource “near-me-service-request-compatibility-5” functional
- “render_service_request_form” added an optional parameter “option_key” cosmetic
- 20 Oct 26 +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.
- 18 Oct 26 +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.
- 16 Oct 26 +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.
- 14 Oct 26 +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.
- 12 Oct 26 +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.
- 10 Oct 26 +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.
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 23 Oct 2026 · Probed https://mcpnear.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcpnear.com | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6a0867bffee820f5f694314697be28a7494 |
| SANs: mcpnear.com, www.mcpnear.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 mcpnear.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mcpnear.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 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcpnear.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcpnear.com/mcp | HTTPS enforced | 301 | https://mcpnear.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 →
cancel_service_booking Cancel an approved appointment ~115
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.
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous_session_id | string | yes | – |
| booking_change_authorization_token | string | yes | One-time approval supplied only by the protected management form. |
| correlation_id | string | yes | – |
| idempotency_key | string | yes | – |
| source | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
complete_account_link Finish saving booking details ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| linking_session_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
create_service_booking Create the confirmed service booking ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous_session_id | string | yes | – |
| booking_authorization_token | string | yes | – |
| campaign_id | string | – | – |
| correlation_id | string | yes | – |
| idempotency_key | string | yes | – |
| source | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_my_service_booking Open one of my appointments ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| booking_id | string | yes | – |
| intent | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
get_service_options Get current service options ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
list_my_service_bookings List my appointments ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
prepare_service_booking_change Review an exact appointment change ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| booking_id | string | – | – |
| idempotency_key | string | yes | – |
| management_context_token | string | – | Opaque short-lived context supplied only by the protected management form. |
| new_slot_id | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
render_service_request_form Open the final service confirmation card ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
reschedule_service_booking Reschedule an approved appointment ~126
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.
| Name | Type | Req | Description |
|---|---|---|---|
| anonymous_session_id | string | yes | – |
| booking_change_authorization_token | string | yes | One-time approval supplied only by the protected management form. |
| correlation_id | string | yes | – |
| idempotency_key | string | yes | – |
| source | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
select_service_option Select a company in the final card ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expected_state_version | integer | yes | – |
| idempotency_key | string | yes | – |
| option_key | string | yes | – |
| request_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
start_service_request Start a service request ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | – |
| idempotency_key | string | yes | – |
| provider_hint | – | – | – |
| user_intent | string | yes | – |
| vertical_hint | string | – | Optional exact live vertical ID. Omit it when uncertain and let the server classify user_intent. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
update_service_request Update a service request ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | – | – |
| expected_state_version | integer | yes | – |
| explicitly_unknown_field_ids | array | – | – |
| idempotency_key | string | yes | – |
| request_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | – | yes | – |
No examples provided.
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.
remote · mcpnear.com
claude mcp add --transport http com-voicedispatcher-mcp-near-me 'https://mcpnear.com/mcp'
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.