Skip to content

Seat Sherpa MCP server

app.seatsherpa/ridesseatsherpa.appstreamable-httpv1.0.0Scanned

Find carpool rides in California and Nevada: live seats, times and all-in seat prices. Read-only.

7 tools: 3 do something that can't be undone and 4 only read.

Tools: 0 delete, 3 irreversible, 0 write, 4 read.
  • Reads private data · 1
  • Reads text others write · 6
  • Can send data out · 3
  • 3 findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Seat Sherpa MCP server can do

The Seat Sherpa MCP server is published by seatsherpa.app, a domain the MCP Registry verified. It has 7 tools. It can do things that cannot be undone, such as sending, paying or publishing (request_ride_link, post_ride_link and cabpool_link), but cannot delete data. 4 tools only read.

1 tool reads private data (get_ride); 6 tools bring in text other people can write (search_rides, get_ride, request_ride_link and 3 more); 3 tools can send data out of your system (request_ride_link, post_ride_link and cabpool_link). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 3 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 12, 2026, version 1.0.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

7 tools

Can't be undone 3Claude Code: ask
  • post_ride_linkFor a driver: a link where the person posts a drive they are already taking on Seat Sherpa, the carpool marketplace.Reads text others writeCan send data out1 finding

    Why it is in this group

    • The name "post_ride_link" says "post": a word for a change.
    • The input addresses people (input.to): what it sends cannot be taken back.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "post_ride_link" says "post": it sends or publishes something to other people.
    • outboundThe input takes a destination (input.to): what the tool writes goes there.

    Findings

    • Warn

      The server marks "post_ride_link" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "post_ride_link" says "post": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Link to post a drive on Seat Sherpa
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 4Show 4 read-only tools
  • get_ridePublic 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 pr…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_ride" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "note": it reads notes.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get a Seat Sherpa ride
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • list_service_areasThe California and Nevada areas Seat Sherpa carpools run between.No findings

    Why it is in this group

    • The name "list_service_areas" says "list": a word for reading.
    Description, as the server wrote it
    The California and Nevada areas Seat Sherpa carpools run between. Use it to check whether a trip is covered before searching.

    Annotations the server declares

    • title: Seat Sherpa service areas
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_cabpoolsFind 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.Reads text others writeNo findings

    Why it is in this group

    • The name "search_cabpools" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Search shared Uber or Lyft rides (Cabpool)
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • search_ridesFind 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…Reads text others writeNo findings

    Why it is in this group

    • The name "search_rides" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Search Seat Sherpa carpools
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

18 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 private-data tool breaks every one.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write6
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__rides__get_ride"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:30 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://seatsherpa.app/mcp: tools/list returned 7 tools to an anonymous client, including request_ride_link (irreversible), post_ride_link (irreversible), cabpool_link (irreversible)

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 2 to 3

Findings

Matches of fixed checks, with the text they matched.

3 warn
  • The server marks "request_ride_link" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "request_ride_link" says "request": a word for a change.

    What this check looks for
  • The server marks "post_ride_link" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "post_ride_link" says "post": a word for a change.

    What this check looks for
  • The server marks "cabpool_link" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The name "cabpool_link" says "link": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 added, 3 changed.+2 added~3 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
    • Tools that change things, listed without credentials: 2 to 3
  3. Tools3 changed.~3 changedView diff

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http rides https://seatsherpa.app/mcp
claude mcp add --transport http rides https://seatsherpa.app/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rides__search_rides",
      "mcp__rides__get_ride",
      "mcp__rides__list_service_areas",
      "mcp__rides__search_cabpools"
    ],
    "ask": [
      "mcp__rides__request_ride_link",
      "mcp__rides__post_ride_link",
      "mcp__rides__cabpool_link"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rides. Review it before you use it.

Capability tags behind 6 rules
  • mcp__rides__search_rides untrusted-input
  • mcp__rides__get_ride private-data, untrusted-input
  • mcp__rides__request_ride_link untrusted-input, outbound
  • mcp__rides__post_ride_link untrusted-input, outbound
  • mcp__rides__search_cabpools untrusted-input
  • mcp__rides__cabpool_link untrusted-input, outbound

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/app.seatsherpa/rides/verify?hash=b710e1b5e5e95b7e0ee102596eb24b23039461a4c92eb1cc973e216b177bcdaa" | jq -e '.changed == false'

Pinned hash b710e1b5e5e9, from Nov 12, 2026, 03:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/app.seatsherpa/rides/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for app.seatsherpa/rides
[![Anlyon Radar](https://radar.anlyon.com/badge/app.seatsherpa/rides.svg)](https://radar.anlyon.com/servers/app.seatsherpa/rides)

Source: MCP Registry. Synced Oct 21, 2026, 17:45 UTC.

Seat Sherpa MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Seat Sherpa MCP server safe?

No scan can promise that. What its definitions show: 7 tools, 3 of which can change, send or delete something, and 3 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Seat Sherpa MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Seat Sherpa MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: request_ride_link, post_ride_link and cabpool_link.

What tools does the Seat Sherpa MCP server have?

7 tools: 3 irreversible, 4 read. request_ride_link, post_ride_link, cabpool_link, search_rides, get_ride, list_service_areas and search_cabpools.

Does the Seat Sherpa MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Seat Sherpa MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): request_ride_link, post_ride_link and cabpool_link.

Has the Seat Sherpa MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 12, 2026. Every change is on this page and in its Atom feed.