seatac-co
Registry code: dad23234fd5ea420
Seatac Connection (seatac.co) runs private, pre-booked SUV and sedan rides between Seatac Airport and the Seattle area, plus hourly charters. Use get_service_info for the service area, vehicles, and policies; quote_ride for a live fare on a specific trip; start_booking for a prefilled seatac.co link where the customer reviews and pays; and find_cruise_sailings for which pier and terminal a ship sails from on a date, with a ready ride-to-pier booking link. Never invent prices: fares are quoted per trip. Phone (206) 737-0808, [email protected].
- endpoint
- https://seatac.co/api/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 seatac-co live?
- Yes — it answered the hub's last check (checked 49m ago). It answered 100% of checks over the last 30 days.
- Is seatac-co free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does seatac-co have?
- 4 tools: start_booking, find_cruise_sailings, quote_ride, get_service_info.
- Is seatac-co 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.
90 days 100%· all time 100%
last good check
of 4 tools
- unknown → live
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.
through this hub
successful
what callers paid
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.
get_service_info open 49m ago
Describe Seatac Connection: private, pre-booked rides between Seatac Airport and the Seattle area, plus hourly charters. Returns the service area, vehicle types with passenger and bag capacity, booking requirements, and the cancellation and refund policy. Fares are quoted per trip; use quote_ride for a live price.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesstart_booking unknown never probed
Create a prefilled seatac.co reservation link for the customer to open. They review the trip, enter contact details, and pay on seatac.co. Nothing is booked or charged by this tool.
{ "type": "object", "required": [ "pickup" ], "properties": { "bags": { "type": "integer", "maximum": 12, "minimum": 0, "description": "Number of checked-size bags (0-12)." }, "hours": { "type": "integer", "maximum": 24, "minimum": 1, "description": "Set only for an hourly charter: the number of hours (1-24)." }, "pickup": { "type": "string", "description": "Pickup location. Street address, hotel, or place in the Seattle area, e.g. \"Seattle-Tacoma International Airport\", \"Pier 91\", \"Hyatt Regency Bellevue\", or \"1301 5th Ave, Seattle\"." }, "dropoff": { "type": "string", "description": "Drop-off location. Street address, hotel, or place in the Seattle area, e.g. \"Seattle-Tacoma International Airport\", \"Pier 91\", \"Hyatt Regency Bellevue\", or \"1301 5th Ave, Seattle\". Optional for hourly charters." }, "passengers": { "type": "integer", "maximum": 12, "minimum": 1, "description": "Number of passengers (1-12)." }, "vehicle_slug": { "type": "string", "description": "Optional vehicle_slug from quote_ride or get_service_info to preselect." }, "flight_number": { "type": "string", "description": "Optional flight number for Seatac pickups or drop-offs, e.g. AS 123." }, "pickup_datetime": { "type": "string", "description": "Pickup date and time, ISO 8601. Without an offset it is read as Seattle local time (America/Los_Angeles), e.g. 2026-11-02T14:30. Optional." } }, "additionalProperties": false }arguments 47 linesfind_cruise_sailings unknown 49m ago
Look up Seattle cruise sailings from the Port of Seattle schedule (2026 season and the preliminary 2027 season): which pier and terminal a ship uses on a date, and which ships sail on a day. Filter by ship (fuzzy), cruise_line, date or from/to, and pier. Each upcoming embarkation (turnaround) day includes ride_to_pier with a prefilled seatac.co booking link from Seattle-Tacoma International Airport; call quote_ride with its quote_ride_arguments plus a pickup time for the live fare. Without a date filter, only sailings from today on are returned.
{ "type": "object", "properties": { "to": { "type": "string", "format": "date", "description": "End of a date range, YYYY-MM-DD (inclusive)." }, "date": { "type": "string", "format": "date", "description": "A single date, YYYY-MM-DD." }, "from": { "type": "string", "format": "date", "description": "Start of a date range, YYYY-MM-DD (inclusive)." }, "pier": { "enum": [ "66", "91" ], "type": "string", "description": "Pier 66 (Bell Street) or Pier 91 (Smith Cove)." }, "ship": { "type": "string", "description": "Ship name, any case; partial names work, e.g. \"Norwegian Bliss\" or \"Bliss\"." }, "cruise_line": { "type": "string", "description": "Cruise line, e.g. \"Norwegian\" or \"Holland America\"." } }, "additionalProperties": false }arguments 37 linesquote_ride unknown 49m ago
Get the live fare for a specific Seatac Connection ride, per eligible vehicle, priced exactly as seatac.co checkout prices it. Each vehicle includes a booking_url where the customer reviews and pays. Rate limited; reuse a quote instead of re-requesting it.
{ "type": "object", "required": [ "pickup", "pickup_datetime", "passengers" ], "properties": { "bags": { "type": "integer", "maximum": 12, "minimum": 0, "description": "Number of checked-size bags (0-12)." }, "hours": { "type": "integer", "maximum": 24, "minimum": 1, "description": "Set only for an hourly charter: the number of hours (1-24)." }, "pickup": { "type": "string", "description": "Pickup location. Street address, hotel, or place in the Seattle area, e.g. \"Seattle-Tacoma International Airport\", \"Pier 91\", \"Hyatt Regency Bellevue\", or \"1301 5th Ave, Seattle\"." }, "dropoff": { "type": "string", "description": "Drop-off location. Street address, hotel, or place in the Seattle area, e.g. \"Seattle-Tacoma International Airport\", \"Pier 91\", \"Hyatt Regency Bellevue\", or \"1301 5th Ave, Seattle\". Optional for hourly charters." }, "passengers": { "type": "integer", "maximum": 12, "minimum": 1, "description": "Number of passengers (1-12)." }, "flight_number": { "type": "string", "description": "Optional flight number for Seatac pickups or drop-offs, e.g. AS 123." }, "pickup_datetime": { "type": "string", "description": "Pickup date and time, ISO 8601. Without an offset it is read as Seattle local time (America/Los_Angeles), e.g. 2026-11-02T14:30." } }, "additionalProperties": false }arguments 45 lines
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.
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.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - 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. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's iddad23234fd5ea420.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/dad23234fd5ea420/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/dad23234fd5ea420?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.
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.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- 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.