accueil / serveurs / Recherche & Web / app.seatsherpa/rides
app.seatsherpa/rides
serveur MCP (Model Context Protocol) · seat-sherpa 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que app.seatsherpa/rides est sûr ?
Au dernier audit MCP Hub, le serveur MCP « app.seatsherpa/rides » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 5 outils
- get_ride≈ 187 tokens
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.
Paramètres, retour & exemple (1)
Paramètresride_id· integer · requis
The ride id.
Exemple d'appel{"name": "get_ride", "arguments": {"ride_id": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_service_areas≈ 112 tokens
The California and Nevada areas Seat Sherpa carpools run between. Use it to check whether a trip is covered before searching.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "list_service_areas", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - post_ride_link≈ 354 tokens
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.
Paramètres, retour & exemple (3)
Paramètresto· string · requis
Where the driver is going, e.g. "Los Angeles", "Las Vegas".date· string · optionnel
Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-20 (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 driver picks the date on the page.from· string · requis
Where the driver starts: a city or place in California or Nevada, e.g. "San Francisco", "Irvine".
Exemple d'appel{"name": "post_ride_link", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - request_ride_link≈ 420 tokens
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.
Paramètres, retour & exemple (4)
Paramètresto· string · requis
Where the rider is going, e.g. "Los Angeles", "Las Vegas".date· string · optionnel
Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-20 (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 person picks the date on the page.from· string · requis
Where the rider starts: a city or place in California or Nevada, e.g. "San Francisco", "UC Davis", "Irvine".seats· integer · optionnel
Optional: seats the rider needs, 1 to 4. Only mentioned in the answer; the person picks it on the page.
Exemple d'appel{"name": "request_ride_link", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - search_rides≈ 545 tokens
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).
Paramètres, retour & exemple (5)
Paramètresto· string · requis
Where the rider is going, e.g. "Los Angeles", "Las Vegas".date· string · optionnel
Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-20 (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 soonest rides.from· string · requis
Where the rider starts: a city or place in California or Nevada, e.g. "San Francisco", "UC Davis", "Irvine".limit· integer · optionnel
Most rides to return. Default 10.days_flexible· integer · optionnel
With a date: also include rides this many days before and after it. Default 1.
Exemple d'appel{"name": "search_rides", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».