_ registry / mcp streamable-http · checked 1h ago

seat-sherpa

https://seatsherpa.app

Registry code: 0ff73d42fd05efa9

api record

Seat Sherpa is the carpool marketplace for long-distance trips in California and Nevada: drivers post trips they are already taking and riders book a seat to split gas. Use search_rides to find rides between two places, get_ride for one ride's details. Prices are all-in per seat in USD. Times are Pacific; a time marked estimated is when the car is expected at that stop. When no ride fits, use request_ride_link to give the person a link to post a ride request, so drivers on that route are notified (a search_rides answer with no rides already includes it). When the person is the driver, use…

endpoint
https://seatsherpa.app/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is seat-sherpa live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is seat-sherpa free to use?
Yes — the hub reached it with no key and no payment.
What tools does seat-sherpa have?
5 tools: search_rides, post_ride_link, get_ride, request_ride_link, list_service_areas.
Is seat-sherpa safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
315ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
1 open 4 never probed 1 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_service_areas open 1h ago

    The California and Nevada areas Seat Sherpa carpools run between. Use it to check whether a trip is covered before searching.

    mcp-tool

    {
      "type": "object",
      "properties": {},
      "additionalProperties": false
    }
    arguments 5 lines
  • search_rides unknown never probed

    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. When no ride fits, the answer includes a link to post a ride request for that route (the same link request_ride_link gives).

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Where the rider is going, e.g. \"Los Angeles\", \"Las Vegas\"."
        },
        "date": {
          "type": "string",
          "description": "Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-07 (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": {
          "type": "string",
          "description": "Where the rider starts: a city or place in California or Nevada, e.g. \"San Francisco\", \"UC Davis\", \"Irvine\"."
        },
        "limit": {
          "type": "integer",
          "maximum": 25,
          "minimum": 1,
          "description": "Most rides to return. Default 10."
        },
        "days_flexible": {
          "type": "integer",
          "maximum": 7,
          "minimum": 0,
          "description": "With a date: also include rides this many days before and after it. Default 1."
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • post_ride_link unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Where the driver is going, e.g. \"Los Angeles\", \"Las Vegas\"."
        },
        "date": {
          "type": "string",
          "description": "Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-07 (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": {
          "type": "string",
          "description": "Where the driver starts: a city or place in California or Nevada, e.g. \"San Francisco\", \"Irvine\"."
        }
      },
      "additionalProperties": false
    }
    arguments 22 lines
  • get_ride unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "ride_id"
      ],
      "properties": {
        "ride_id": {
          "type": "integer",
          "minimum": 1,
          "description": "The ride id."
        }
      },
      "additionalProperties": false
    }
    arguments 14 lines
  • request_ride_link unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "Where the rider is going, e.g. \"Los Angeles\", \"Las Vegas\"."
        },
        "date": {
          "type": "string",
          "description": "Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-07 (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": {
          "type": "string",
          "description": "Where the rider starts: a city or place in California or Nevada, e.g. \"San Francisco\", \"UC Davis\", \"Irvine\"."
        },
        "seats": {
          "type": "integer",
          "maximum": 4,
          "minimum": 1,
          "description": "Optional: seats the rider needs, 1 to 4. Only mentioned in the answer; the person picks it on the page."
        }
      },
      "additionalProperties": false
    }
    arguments 28 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 0ff73d42fd05efa9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/0ff73d42fd05efa9/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/0ff73d42fd05efa9/badge.svg)](https://brick.blue/agent/0ff73d42fd05efa9?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.