# io.github.mir-quadri/nj-transit-mcp

> NJ Transit rail, bus and PATH schedules via MCP (scheduled, plus live PATH)

- name: io.github.mir-quadri/nj-transit-mcp
- version: 1.3.0
- connection class: R0 (autonomous)
- trust: 94/100
- quality: 94/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.mir-quadri%2Fnj-transit-mcp
- tools: https://api.protogrid.dev/v1/servers/io.github.mir-quadri%2Fnj-transit-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "nj-transit-mcp": {
      "type": "http",
      "url": "https://nj-transit-mcp.vercel.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 80
- drivers: +repository +namespace-matches-repo +reachable +uptime-100% +updated-6d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 94/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 6 of 6 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 865 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 5 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 6, about 865 tokens to load them all
- tool set hash: b92af5f81f5451119de9999d4fe41565
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.mir-quadri/nj-transit-mcp.svg)](https://protogrid.dev/servers/io.github.mir-quadri/nj-transit-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://nj-transit-mcp.vercel.app/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (6)

- `lines`: All lines/routes. NJ Transit: 17 rail + light-rail routes.
NJ bus: 263 routes (short_name is the bus number; long names are
empty in the bus feed, use trip headsigns for destinations).
PATH: 4 daytime routes.
- `next_departures`: Next departures from a station/stop (name or stop ID).
system 'nj_transit': rail + light rail, scheduled by default, live
delays when NJT credentials are configured. system 'nj_bus': NJ
Transit bus, SCHEDULED only in v1.2 (BUSDATA live not enabled).
system 'path': live PATH arrivals, no key needed. Times are
America/New_York.
NOTE: New Jersey Transit has no subway. For a subway-like ride use
system='path', or NJ light rail lines HBLR / NLR / River Line.
- `search_stations`: Find stations/stops by name. system: 'nj_transit' (rail + light
rail), 'nj_bus' (NJ Transit bus street stops), 'path', or 'all'.
'all' includes bus, so a first 'all' search downloads the 50 MB bus
GTFS once; use system='nj_bus' for bus-only searches. Returns
station/stop IDs to use with next_departures / trip_between.
- `server_status`: What data this server is actually serving right now: GTFS date
range and counts, whether live NJ data is enabled, PATH feed age.
Use this to answer 'is this live or scheduled?' honestly.
- `service_alerts`: Service alerts. NJ Transit alerts require NJT credentials (see
server_status for how to enable); PATH has no separate alerts feed
in v1, so PATH alerts are reported as unavailable, not invented.
- `trip_between`: Next NJ Transit trains/buses from origin to destination on the
SAME trip (no transfers). Returns departure, arrival and duration.
Times ET. system: 'nj_transit' (default, rail + light rail) or
'nj_bus' (bus, scheduled only in v1.2).