Uber
by Uber
Get real-time Uber fare and ETA estimates between two US locations from an AI agent. Anthropic lists 2 tools and Uber publishes no tool list. No ride can be requested through the connector — booking hands off to the Uber app.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Uber via MCP
https://mcp.uber.com/claude/rides-3p/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Uber Tools & Capabilities (2)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The no-booking finding is inferred, not declared. This is the distinction that governs how much weight it carries. Uber publishes no exclusion statement — no page saying the connector cannot request a ride, cannot pay, cannot cancel. What exists is a marketing sentence about handing off to the app, a two-name tool listing, and a scope that is not the one gating Uber's booking API. Those converge, and they are not the same as a vendor drawing the line itself.
- Uber publishes no tool list for this server. The two names come from Anthropic's directory. Both are absent from every Uber page and from every secondary source we searched, so the Reverse-Honeycomb diff has nothing on the vendor side to run against.
- The directory's authless posture is contradicted by the server. Anthropic's snapshot records an authless posture and an
is_authlessflag set true. The server publishes OAuth metadata and refused an anonymous request. Trust the server. 3p.rides.mcpis undocumented. It is the only application scope on the consent screen and Uber describes it nowhere, so a user granting it cannot know what it permits.publish_analytics_eventshas no published behaviour. We could not establish what it sends, when it fires, or whether a user can decline it separately.- We could not read tool schemas or safety annotations. The endpoint returned 403 to an anonymous request on 2026-08-23, with no
WWW-Authenticateheader and no RFC 9728 protected- resource descriptor at any of the four probed paths, so no parameter-level detail is published here. - Fare estimates exclude taxes, Service Fees and promotions, per Uber's own generative AI policy, which directs users to the checkout page for the accurate figure. An agent quoting the estimate as the price will be wrong by the fee stack.
- Price comparison against competitors is called out as a terms violation in Uber's REST API documentation. We found no statement applying that to the MCP connector, and it is unresolved whether it does.
- United States only, per Anthropic's directory description. No Uber source states an expansion plan.
- Commercial use needs written permission. Uber's U.S. Terms of Use, last modified 2026-08-12, restrict the Services to noncommercial use absent a separate written agreement, and separately bar using content from the Services to develop software or train AI systems without prior written permission.
- The
.mdsuffix route is an interpolating catch-all.uber.com/legal/en.mdanduber.com/legal/en/.mdboth return HTTP 200 with a body hash identical to the plain page. A probe that trusted the status code would report a Markdown route that does not exist.
Frequently asked questions
No. Neither tool Anthropic lists requests a ride. The connector returns fare and ETA estimates, and Uber's own connector listing states that all ride requests are handed off to the official Uber app to be completed securely. Nothing in this surface dispatches a driver or charges a card, so no agent action here is irreversible.
Through a deep link the user taps. Uber documents deep links as URLs that launch the Uber app with pickup, dropoff and product pre-filled, and its developer docs describe them as starting the ride request flow rather than completing it. The rider still confirms the trip inside Uber, where the fare and payment method are shown.
Uber does not say. It is the only write-shaped name in the listing, and no Uber documentation anywhere describes it. Its name implies the connector reports interaction telemetry back to Uber. Uber's rider privacy notice lists usage data including app features or pages viewed and Uber search history, so treat estimate queries as observed.
Yes, despite the directory marking it authless. Anthropic's snapshot records an authless posture, but the server publishes OAuth authorization server metadata at mcp.uber.com naming auth.uber.com and a dedicated 3p.rides.mcp scope. An anonymous request to the endpoint was refused on 2026-08-23, so treat the directory's authless flag as stale.
No. The documentation URL in Anthropic's directory is uber.com/legal/en, a catalogue of legal documents whose 975-word index contains no mention of MCP, Model Context Protocol, or generative AI. Uber's developer site covers its REST APIs and never names the connector. No vendor tool enumeration exists to check the directory's two names against.
No tool in the listing moves money. Fare estimates are read-only figures and no tool name carries a payment, wallet, tip or receipt verb. Uber's Guest Rides API does document a tip endpoint and its Riders API documents ride requests billed to a card, but neither appears in this connector and both sit behind different OAuth scopes.
The United States only. Anthropic's directory description states the connector gives fare estimates between any two locations in the United States, and names UberX, UberXL, Comfort and Black as the products it compares. No source we found extends it to other countries, and Uber publishes no coverage list for the connector.
Treat them as indicative, not final. Uber's generative AI policy states that pricing information provided or used to generate responses is an estimate and excludes taxes, Service Fees and promotions, and directs users to the checkout page for the most accurate information. Surge pricing can also move a fare between the estimate and the booking.
Sources
- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-16 · retrieved 2026-08-16
- Uber connector listing on claude.com (retrieved 2026-08-23). Source of the "handed off to the official Uber app" statement. · retrieved 2026-08-23
- Live auth posture check: anonymous JSON-RPC
initializetohttps://mcp.uber.com/claude/rides-3p/mcpreturned HTTP 403 with noWWW-Authenticateheader (2026-08-23) · retrieved 2026-08-23 - Uber MCP OAuth authorization server metadata (retrieved 2026-08-23). Source of the thirteen advertised scopes including
3p.rides.mcp. · retrieved 2026-08-23 - RFC 9728 probe, four paths under
mcp.uber.com/.well-known/— no protected-resource descriptor; a control path returned a matching 404 (2026-08-23) · retrieved 2026-08-23 - Uber Guest Rides API introduction and endpoint index (retrieved 2026-08-23). Source of the
guests.tripsscope and the trip create, dispatch, cancel, tip and message endpoints. · retrieved 2026-08-23 - Uber Guest Rides build guide, Requesting a Trip (retrieved 2026-08-23) · retrieved 2026-08-23
- Uber Riders API authentication guide (retrieved 2026-08-23). Source of
POST /requestsunder a user access token. · retrieved 2026-08-23 - Uber Riders API scopes reference (retrieved 2026-08-23). Source of the privileged
requestscope and the Full Access review requirement. · retrieved 2026-08-23 - Uber Riders API, GET /estimates/price (retrieved 2026-08-23). Source of the price-comparison terms warning and the approval-required banner. · retrieved 2026-08-23
- Uber deep links introduction (retrieved 2026-08-23). Source of
setPickup, the two available deep-link actions, and thepayment_method_idparameter. · retrieved 2026-08-23 - Uber U.S. General Terms of Use, last modified 2026-08-12 (retrieved 2026-08-23) · retrieved 2026-08-12
- Generative AI features at Uber, last modified 2025-06-18 (retrieved 2026-08-23) · retrieved 2025-06-18
- Uber privacy notice for riders and order recipients (retrieved 2026-08-23) · retrieved 2026-08-23
- Uber legal document index, the URL Anthropic's directory nominates as documentation (retrieved 2026-08-23), which redirects to . 975 words, no MCP or connector content.
llms.txtandllms-full.txtboth 404 on the host. · retrieved 2026-08-23 - Uber rider help centre (retrieved 2026-08-23). No connector or MCP article found. · retrieved 2026-08-23
https://www.uber.com/robots.txt(retrieved 2026-08-23) — permits the paths fetched above · retrieved 2026-08-23
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Uber
- Tools
- 2
- Domain
- mcp.uber.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.