Valet Parking Directo… vs Vorim MCP Server | AllMCPs
Side-by-Side Model Context Protocol Comparison
Valet Parking Directory vs Vorim MCP Server
In-depth architectural comparison of the Valet Parking Directory and Vorim MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Valet Parking Directory
Security · Remote HTTP/SSE
Quality: 47/100 (Fair) | Auth: No auth required
Vorim MCP Server
Security · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Valet Parking Directory if you need specialized Security tools running via a hosted cloud SSE transport. Choose Vorim MCP Server if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Valet Parking Directory when:
You need dedicated capabilities in the Security domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
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. Returns the in-bundle catalog; no upstream call; no isError path.
valet_get_operator
Get the full operator profile by slug including address, phone, website, 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 complete profile to rank or present. Returns isError on slug 404 or upstream outage.
valet_search_cities
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.
valet_find_operators_in_city
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 premium tier first then name. Empty array if no listed operators.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Valet Parking Directory is categorized under Security and uses a remote streaming HTTP/SSE transport. In contrast, Vorim MCP Server belongs to Security using local stdio subprocess. Select Valet Parking Directory when you need capabilities focused on security and Vorim MCP Server when you require tools for security.
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.
valet_find_nearest_operators
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.
valet_find_operators_near
Find valet operators within a given radius of a coordinate, ranked premium tier first 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.
Vorim MCP Server Tools (19)
vorim_ping
Check API health and connectivity
vorim_register_agent
Register a new agent with Ed25519 cryptographic identity
vorim_register_ephemeral
Register a `did:key` ephemeral agent with TTL
vorim_get_agent
Get agent details by ID
vorim_list_agents
List all agents with pagination and filtering
vorim_update_agent
Update agent metadata (name, description, status)
vorim_revoke_agent
Permanently revoke an agent
vorim_check_permission
Check if agent has a permission scope (sub-5ms)
vorim_grant_permission
Grant a permission with optional expiry and rate limits