com.getvaletparking/valet-parking-directory
REMOTE · API.GETVALETPARKING.COM
MCP server for valet parking: 789 US operators across 31,186 cities. 7 tools. No auth.
Available components
Last scanned (11 hours ago)
Scores higher than 92% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Maps and Location
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 Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1272 tokens (~159/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Sept 26 0
- Tool “valet_get_operator” rewrote its description, which is the text the model reads security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 0
- HTTPS: unverified → pass ▲ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- Tool “valet_find_operators_in_city” rewrote its description, which is the text the model reads security
- Tool “valet_find_operators_near” rewrote its description, which is the text the model reads security
- 24 Aug 26 0
- Schema quality: 140 → 158 ▼ functional
- New tool “valet_request_quote” functional
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 7 Nov 2026 · Probed https://api.getvaletparking.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=getvaletparking.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 23 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | ac27baed31115bf61305b4a76c5e37fb |
| SANs: getvaletparking.com, api.getvaletparking.com, *.api.getvaletparking.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.getvaletparking.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| getvaletparking.com. | DS published | 2371 | 13 | Verified |
| api.getvaletparking.com. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.getvaletparking.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.getvaletparking.com/mcp | HTTPS enforced | 301 | https://api.getvaletparking.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 →
valet_find_nearest_operators Find Nearest Operators ~163
List nearest valet operators within a 100-mile cap of a coordinate, optionally narrowed by service. Use this when a user is in a city with no listed operators and you need the closest available fallback ranked nearest-first. Empty array if nothing within 100 miles.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in decimal degrees (WGS84). Range: -90 to 90. |
| limit | integer | – | Max results to return; default 10, capped at 50 |
| lng | number | yes | Longitude in decimal degrees (WGS84). Range: -180 to 180. |
| service | string | – | Optional service narrowing. One of the 9 canonical valet service slugs. Omit to list every nearby operator regardless of services offered. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| data_freshness | object | yes | TOOL-10 freshness stamp |
| operators | array | yes | Operators within 100 miles of the input coordinate, sorted nearest-first. Empty array means nothing within 100 miles. |
No examples provided.
valet_find_operators_in_city Find Operators In City ~165
List valet operators serving a city slug plus state slug, optionally narrowed by service. Use this when an agent has a city already disambiguated and wants its operator roster ranked by listing tier then name. Empty array if no listed operators.
| Name | Type | Req | Description |
|---|---|---|---|
| city_slug | string | yes | Lowercase kebab-case city slug (e.g. 'houston', 'san-francisco') |
| limit | integer | – | Max results to return; default 10, capped at 50 |
| service | string | – | Optional service narrowing. One of the 9 canonical valet service slugs. Omit to list every operator serving the city. |
| state_slug | string | yes | Lowercase kebab-case US state slug (e.g. 'tx', 'new-york') |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| data_freshness | object | yes | TOOL-10 freshness stamp |
| operators | array | yes | Operators serving the city, ranked tier:desc then name:asc. Empty array means no matches. |
No examples provided.
valet_find_operators_near Find Operators Near ~216
Find valet operators within a given radius of a coordinate, ranked by listing tier then distance. Use this when you have a coordinate and an event-context radius (5mi single venue, 25mi metro, 50mi regional). radius_miles is required; empty array if no matches.
| Name | Type | Req | Description |
|---|---|---|---|
| lat | number | yes | Latitude in decimal degrees (WGS84). Range: -90 to 90. |
| limit | integer | – | Max results to return; default 10, capped at 50 |
| lng | number | yes | Longitude in decimal degrees (WGS84). Range: -180 to 180. |
| radius_miles | number | yes | Search radius in miles. REQUIRED, no default. Pick based on context: 5 mi for a single venue, 25 mi for a metro, 50 mi for a regional sweep. |
| service | string | – | Optional service narrowing. One of the 9 canonical valet service slugs. Omit to list every operator within radius regardless of services offered. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| data_freshness | object | yes | TOOL-10 freshness stamp |
| operators | array | yes | Operators within radius_miles of the input coordinate, ranked tier:desc then distance:asc. Empty array means no matches within radius. |
No examples provided.
valet_get_operator Get Operator Profile ~111
Get the full operator profile by slug including address, phone, listing URL, website (paid listings only), services, venues_served, FAQs, and tipping note. Use this when an agent has a slug from a search tool or directory URL and needs the profile. Returns isError on slug 404 or upstream outage.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | Canonical kebab-case operator slug (e.g. '12-oaks-parking-llc'). Lowercase letters, digits, hyphens only. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| data_freshness | object | yes | TOOL-10 freshness stamp |
| operator | object | yes | The full merged operator profile (Typesense + Payload long-tail fields) |
No examples provided.
valet_list_services List Valet Services ~71
List the 9 canonical valet service slugs with display name and category. Use this when an agent needs to validate or discover the supported service taxonomy before composing a follow-up search (e.g. valet_search_by_service_and_city). Returns the in-bundle catalog; no upstream call; no isError path.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| data_freshness | object | yes | TOOL-10 freshness stamp |
| services | array | yes | The 9 canonical valet service types, in catalog order |
No examples provided.
valet_request_quote Request Valet Quote ~286
Submit a valet parking quote request to the operators serving a US city. Use this when a person has asked you to arrange valet and has given their name, email, phone, city, service type and event date. The request is only sent after they confirm by email.
| Name | Type | Req | Description |
|---|---|---|---|
| city_other | string | – | Free-text city name when no directory slug is known. Omit if using city_slug. |
| city_slug | string | – | Canonical kebab-case city slug from valet_search_cities, e.g. 'austin'. Omit if using city_other. |
| contact_email | string | yes | Email address to send the one-tap confirmation link to |
| contact_name | string | yes | The requester's full name |
| contact_phone | string | yes | Phone number the operator can call |
| event_date | string | yes | Event date in YYYY-MM-DD format |
| guest_count | integer | – | Approximate guest count, if known |
| notes | string | – | Free-text notes for the operator, e.g. venue name or timing details |
| operator_slug | string | – | Send to this one operator only instead of the full fan-out for the city. Omit to notify every matched operator in the city. |
| service | string | yes | One of the 9 canonical valet service slugs |
| vehicle_count | integer | – | Approximate vehicle count, if known |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| next | string | yes | What the agent should tell the person to do next |
| reference | string | yes | Short human-readable reference for this quote request |
| status | string | yes | Always pending-confirmation on success |
No examples provided.
valet_search_by_service_and_city Search By Service And City ~144
Search valet operators by service slug plus city slug across all matching states. Use this when an agent has both a service slug and a city slug and wants a cross-state tier-then-name ranked list. Invalid service slugs surface the 9 canonical alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| city_slug | string | yes | Lowercase kebab-case city slug (e.g. 'austin', 'springfield'). May match multiple cities across states. |
| limit | integer | – | Max results to return; default 10, capped at 50 |
| service_slug | string | yes | Required canonical valet service slug. One of 9 values; call valet_list_services for the full set. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| data_freshness | object | yes | TOOL-10 freshness stamp |
| operators | array | yes | Operators offering service_slug in any city matching city_slug across all states. Empty array means no matches. |
No examples provided.
valet_search_cities Search Cities ~116
Search the cities directory by name prefix with population-ranked results. Use this when an agent needs to resolve a partial city name into a canonical city slug plus state slug plus lat/lng before composing valet_find_operators_in_city or valet_find_operators_near. Empty array if no matches.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results to return; default 8, capped at 25 |
| query | string | yes | Partial or full city name (>=2 chars). Matched against name and lowercase name fields with prefix semantics. |
| Name | Type | Req | Description |
|---|---|---|---|
| _meta | object | yes | TOOL-11 ToS and attribution block |
| cities | array | yes | Cities matching the query, ranked by text match then population desc |
| data_freshness | object | yes | TOOL-10 freshness stamp |
No examples provided.
How do I install the com.getvaletparking/valet-parking-directory MCP server?
com.getvaletparking/valet-parking-directory is a hosted endpoint at https://api.getvaletparking.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 · api.getvaletparking.com
claude mcp add --transport http com-getvaletparking-valet-parking-directory 'https://api.getvaletparking.com/mcp'
What is the com.getvaletparking/valet-parking-directory MCP server?
com.getvaletparking/valet-parking-directory is an MCP server listed in the public MCP registry as com.getvaletparking/valet-parking-directory. MCP server for valet parking: 789 US operators across 31,186 cities. 7 tools. No auth. This page covers its hosted endpoint (https://api.getvaletparking.com/mcp).
Is the com.getvaletparking/valet-parking-directory MCP server safe to use?
com.getvaletparking/valet-parking-directory scores 86 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 com.getvaletparking/valet-parking-directory MCP server expose?
com.getvaletparking/valet-parking-directory exposes 8 tools: valet_list_services, valet_get_operator, valet_search_cities, valet_find_operators_in_city, valet_search_by_service_and_city, and 3 more. Their descriptions and schemas cost roughly 1,272 tokens of context every time the server is loaded.
Does the com.getvaletparking/valet-parking-directory MCP server require authentication?
No. We connected to com.getvaletparking/valet-parking-directory without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.getvaletparking/valet-parking-directory MCP server still maintained?
com.getvaletparking/valet-parking-directory is still listed as active in the MCP registry. We last reached this channel on 7 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.getvaletparking/valet-parking-directory MCP server?
VerifyMCP ran 13 checks on com.getvaletparking/valet-parking-directory, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.