Seat Sherpa
REMOTE · SEATSHERPA.APP
Find carpool rides in California and Nevada: live seats, times and all-in seat prices. Read-only.
Available components
Last scanned (23 hours ago)
Scores higher than 89% of remote servers
Reachable. Last reached 4 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 Security80
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2018 tokens (~288/item across 7 items; 7 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 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
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.
- 4 Nov 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Schema quality: 1325 → 2018 ▼ functional
- Server version: 1.0.0 → 1.2.1 functional
- New tool “cabpool_link” functional
- New tool “search_cabpools” functional
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 3 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 1 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 31 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 30 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 29 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
- 28 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- “post_ride_link” reworded the description of “date” cosmetic
- “request_ride_link” reworded the description of “date” cosmetic
- “search_rides” reworded the description of “date” cosmetic
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 4 Nov 2026 · Probed https://seatsherpa.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=seatsherpa.app | CN=YR1,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | RSA 2048 | SHA256-RSA | 634c6d458deb0c5ebec5029372486bd5352 |
| SANs: seatsherpa.app | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of seatsherpa.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| seatsherpa.app. | 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 |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://seatsherpa.app/mcp | Verified | 200 | |
| http (plaintext) | http://seatsherpa.app/mcp | HTTPS enforced | 308 | https://seatsherpa.app/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 →
cabpool_link Link to share an Uber or Lyft (Cabpool) ~372
Cabpool: a free Seat Sherpa feature for sharing an Uber, Lyft or Waymo with people going the same way and splitting the fare, most often to or from an airport (SFO, OAK, SJC, LAX, BUR, SAN, SMF and others) or across town in California or Nevada. Use it when the person wants to split a rideshare rather than ride in someone's car, including short trips inside one area (for example "split an Uber from Nob Hill to SFO"), which search_rides does not cover. Returns a link that opens the cabpool form with the pickup, drop-off and day filled in; the person signs in, sees a fare estimate and each person's share, and posts it so others going that way can join. Seat Sherpa does not book, run or charge for the ride and is not affiliated with Uber, Lyft or Waymo: one member books it in their own app and the others pay their share directly. This tool only builds the link and posts nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit and the pers… |
| from | string | yes | Pickup: a place, neighborhood, campus or airport, e.g. "Nob Hill, San Francisco", "UC Davis", "LAX". |
| time | string | – | Optional pickup time, 24-hour HH:MM Pacific (e.g. "06:30"); used only together with date. |
| to | string | yes | Drop-off, e.g. "SFO", "Downtown Oakland". |
No output schema declared.
No examples provided.
get_ride Get a Seat Sherpa ride ~97
Public details of one Seat Sherpa ride by its id (from search_rides or a seatsherpa.app/ride link): route and stops with estimated times, departure (Pacific), seats left, all-in price per seat in USD, the driver's first name, rating and trips, the driver's note to riders, flexibility, the cancellation policy, and the booking link. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| ride_id | integer | yes | The ride id. |
No output schema declared.
No examples provided.
list_service_areas Seat Sherpa service areas ~35
The California and Nevada areas Seat Sherpa carpools run between. Use it to check whether a trip is covered before searching.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
post_ride_link Link to post a drive on Seat Sherpa ~245
For a driver: a link where the person posts a drive they are already taking on Seat Sherpa, the carpool marketplace. Drivers set their own seat price, riders share costs like gas and tolls, and riders searching that route get notified. Use it when the person is the one driving (for example "I'm driving to LA on Friday, can I take people?"), not to find a ride. Takes the starting place, the destination and an optional date. The driver signs in and posts on the page; this tool only builds the link and posts nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit and the driv… |
| from | string | yes | Where the driver starts: a city or place in California or Nevada, e.g. "San Francisco", "Irvine". |
| to | string | yes | Where the driver is going, e.g. "Los Angeles", "Las Vegas". |
No output schema declared.
No examples provided.
request_ride_link Link to request a Seat Sherpa ride ~295
For a rider when no ride fits: a link where the person posts a ride request on Seat Sherpa, the carpool marketplace, so drivers on that route see it and get notified, and the person hears back when a matching ride is posted. Use it after search_rides finds nothing that works (that answer already includes this link), or when the person asks to be told about a trip nobody has posted. Takes the same places and optional date as search_rides. The person signs in and posts the request on the page; this tool only builds the link, posts nothing, and never needs names, phone numbers or emails.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit and the pers… |
| from | string | yes | Where the rider starts: a city or place in California or Nevada, e.g. "San Francisco", "UC Davis", "Irvine". |
| seats | integer | – | Optional: seats the rider needs, 1 to 4. Only mentioned in the answer; the person picks it on the page. |
| to | string | yes | Where the rider is going, e.g. "Los Angeles", "Las Vegas". |
No output schema declared.
No examples provided.
search_cabpools Search shared Uber or Lyft rides (Cabpool) ~266
Find open cabpools on Seat Sherpa: people sharing an Uber, Lyft or Waymo going the same way and splitting the fare, often to or from an airport. Takes a pickup and a drop-off (a city, area, neighborhood or airport such as "San Francisco", "UC Davis", "SFO"; both may be in one area) and an optional date. Returns each cabpool's pickup and drop-off place, departure time (Pacific), service, spots left, an estimate of each person's share in USD and a link to join. Seat Sherpa does not book, run or charge for the ride; when nothing fits, the answer includes a link to post a cabpool.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the… |
| from | string | yes | Pickup area or place, e.g. "San Francisco", "Davis", "LAX". |
| to | string | yes | Drop-off area or place, e.g. "SFO", "Los Angeles". |
No output schema declared.
No examples provided.
search_rides Search Seat Sherpa carpools ~399
Find upcoming long-distance carpool rides on Seat Sherpa (California and Nevada) where everyday drivers sell the empty seats on a trip they are already taking, and riders split the cost of gas. Give a starting place and a destination as city or place names (for example "San Francisco" and "Los Angeles"), and optionally a travel date. Returns rides with open seats: route, departure date and time (Pacific), seats left, the all-in price per seat in USD (what the rider pays, fees included), the driver's first name, and a link where the person books. Rides that stop in a city count for that city, so a San Jose to San Diego ride with a Los Angeles stop is found for Los Angeles to San Diego. Booking happens on the link; this tool cannot book. Rides on a nearby route (for example a San Francisco ride for a San Jose search) are listed separately as nearby_rides; say they are nearby, not exact. When no ride fits exactly, the answer includes a link to post a ride request for that route (the same link request_ride_link gives).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the… |
| days_flexible | integer | – | With a date: also include rides this many days before and after it. Default 1. |
| from | string | yes | Where the rider starts: a city or place in California or Nevada, e.g. "San Francisco", "UC Davis", "Irvine". |
| limit | integer | – | Most rides to return. Default 10. |
| to | string | yes | Where the rider is going, e.g. "Los Angeles", "Las Vegas". |
No output schema declared.
No examples provided.
How do I install the Seat Sherpa MCP server?
Seat Sherpa is a hosted endpoint at https://seatsherpa.app/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 · seatsherpa.app
claude mcp add --transport http app-seatsherpa-rides 'https://seatsherpa.app/mcp'
What is the Seat Sherpa MCP server?
Seat Sherpa is an MCP server listed in the public MCP registry as app.seatsherpa/rides. Find carpool rides in California and Nevada: live seats, times and all-in seat prices. Read-only. This page covers its hosted endpoint (https://seatsherpa.app/mcp).
Is the Seat Sherpa MCP server safe to use?
Seat Sherpa scores 84 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 Seat Sherpa MCP server expose?
Seat Sherpa exposes 7 tools: search_rides, get_ride, list_service_areas, request_ride_link, post_ride_link, and 2 more. Their descriptions and schemas cost roughly 1,709 tokens of context every time the server is loaded.
Does the Seat Sherpa MCP server require authentication?
No. We connected to Seat Sherpa without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Seat Sherpa MCP server still maintained?
Seat Sherpa is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.