_ registry / mcp http-sse · checked 2h ago

sf-transit-mcp

https://mcp.riv.lc

Registry code: f4a4f98951ac926b

api record

Plan trips requested by the user in San Francisco and the Bay Area. Use search_places to find addresses, stops, and destinations before plan_trip. For stop departures, use get_stop_departures with a selected STOP result id and coordinates from search_places, or a stopId and coordinates from a plan_trip leg. Never invent stop IDs. Use the home address supplied by the user; never invent an address or coordinates. Ask the user to choose when more than one place could match. Choose an accessible entrance; do not assume a landmark's center is an entrance. Interpret relative times in Pacific time…

endpoint
https://mcp.riv.lc/sf-transit/mcp
protocol
http-sse ·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 sf-transit-mcp live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is sf-transit-mcp free to use?
Yes — the hub reached it with no key and no payment.
What tools does sf-transit-mcp have?
4 tools: get_service_info, plan_trip, get_stop_departures, search_places.
Is sf-transit-mcp 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
702ms

last good check

priced tools
0

of 4 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • get_service_info unknown never probed

    Read the current time, available tools, data sources, and service limits without contacting a routing service.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • plan_trip unknown 2h ago

    Find complete trips with walking, transit, transfers, scheduled and predicted times, and total travel time. Use coordinates from the selected search result. Omit times for leaving now; otherwise supply departureTime OR arrivalTime with a UTC offset. Transit trips include walking to and from stops. Add walk or bicycle to modes to compare walking or cycling without transit. Coordinates are sent to Transitous. No API key.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "origin",
    "destination"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 3,
      "maximum": 6,
      "minimum": 1
    },
    "modes": {
      "type": "array",
      "items": {
        "enum": [
          "transit",
          "walk",
          "bicycle"
        ],
        "type": "string"
      },
      "default": [
        "transit"
      ],
      "maxItems": 3,
      "minItems": 1
    },
    "origin": {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "label": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "latitude": {
          "type": "number",
          "maximum": 38.9,
          "minimum": 36.85
        },
        "longitude": {
          "type": "number",
          "maximum": -121.2,
          "minimum": -123.6
        }
      },
      "additionalProperties": false
    },
    "wheelchair": {
      "type": "boolean",
      "default": false
    },
    "arrivalTime": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    },
    "destination": {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "label": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "latitude": {
          "type": "number",
          "maximum": 38.9,
          "minimum": 36.85
        },
        "longitude": {
          "type": "number",
          "maximum": -121.2,
          "minimum": -123.6
        }
      },
      "additionalProperties": false
    },
    "maxTransfers": {
      "type": "integer",
      "maximum": 8,
      "minimum": 0
    },
    "departureTime": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    }
  },
  "additionalProperties": false
}
    arguments 102 lines
  • get_stop_departures unknown 2h ago

    Show upcoming departures at a selected Bay Area transit stop, including live predictions where available, scheduled times, cancellations, and boarding restrictions. Use the stop ID and coordinates from a search_places STOP result or plan_trip stop. Omit departureTime for now. Stop ID and time are sent to Transitous. No API key.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "stop"
  ],
  "properties": {
    "stop": {
      "type": "object",
      "required": [
        "latitude",
        "longitude",
        "stopId"
      ],
      "properties": {
        "label": {
          "type": "string",
          "maxLength": 200,
          "minLength": 1
        },
        "stopId": {
          "type": "string",
          "maxLength": 500,
          "minLength": 1
        },
        "latitude": {
          "type": "number",
          "maximum": 38.9,
          "minimum": 36.85
        },
        "longitude": {
          "type": "number",
          "maximum": -121.2,
          "minimum": -123.6
        }
      },
      "additionalProperties": false
    },
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 20,
      "minimum": 1
    },
    "departureTime": {
      "type": "string",
      "format": "date-time",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • search_places unknown 2h ago

    Find matching Bay Area addresses, landmarks, or transit stops and their map coordinates. Including the city helps distinguish places with the same name. Returns a list when more than one place matches. No API key. The search text is sent to Transitous.

    mcp-tool

    {
  "type": "object",
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 5,
      "maximum": 10,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 240,
      "minLength": 2
    }
  },
  "additionalProperties": false
}
    arguments 21 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 f4a4f98951ac926b.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f4a4f98951ac926b/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/f4a4f98951ac926b/badge.svg)](https://brick.blue/agent/f4a4f98951ac926b?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
80%

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.