# io.github.mir-quadri/nj-transit-mcp (remote · nj-transit-mcp.vercel.app)

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

- Trust score: 71/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `nj-transit-mcp.vercel.app`: 71/100 (this document), [markdown](https://verifymcp.io/servers/mir-quadri-nj-transit-mcp/nj-transit-mcp.md), [page](https://verifymcp.io/servers/mir-quadri-nj-transit-mcp/nj-transit-mcp)

## Channel facts

- Endpoint: `https://nj-transit-mcp.vercel.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 548 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the io.github.mir-quadri/nj-transit-mcp server?

io.github.mir-quadri/nj-transit-mcp is a hosted endpoint at https://nj-transit-mcp.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http mir-quadri-nj-transit-mcp 'https://nj-transit-mcp.vercel.app/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "mir-quadri-nj-transit-mcp": {
      "url": "https://nj-transit-mcp.vercel.app/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.mir-quadri-nj-transit-mcp]
url = "https://nj-transit-mcp.vercel.app/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mir-quadri-nj-transit-mcp": {
      "type": "remote",
      "url": "https://nj-transit-mcp.vercel.app/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mir-quadri-nj-transit-mcp --url 'https://nj-transit-mcp.vercel.app/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  mir-quadri-nj-transit-mcp:
    url: "https://nj-transit-mcp.vercel.app/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "mir-quadri-nj-transit-mcp": {
      "Transport": "http",
      "Url": "https://nj-transit-mcp.vercel.app/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add mir-quadri-nj-transit-mcp -t streamable-http -u 'https://nj-transit-mcp.vercel.app/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 4.1.5 → 4.1.6

### 2026-11-02 (score 70)

First indexed and scored.

## MCP tools (6)

### `search_stations` (~112 tokens)

Find NJ Transit, bus, and PATH 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.

Input parameters:

- `query` (string, required)
- `system` (string)

### `next_departures` (~161 tokens)

Next departures from a station

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.

Input parameters:

- `limit` (integer)
- `line`
- `station` (string, required)
- `system` (string)
- `towards`

### `trip_between` (~98 tokens)

Next same-trip trains or buses between two stations

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).

Input parameters:

- `destination` (string, required)
- `limit` (integer)
- `origin` (string, required)
- `system` (string)

### `lines` (~69 tokens)

List all routes

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.

Input parameters:

- `system` (string)

### `service_alerts` (~58 tokens)

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.

Input parameters:

- `system` (string)

### `server_status` (~50 tokens)

Server status and data freshness

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/mir-quadri-nj-transit-mcp/nj-transit-mcp#diagnostics

## Score history

- 2026-11-05: 71
- 2026-11-04: 71
- 2026-11-03: 70
- 2026-11-02: 70

## Common questions

### What is the io.github.mir-quadri/nj-transit-mcp server?

io.github.mir-quadri/nj-transit-mcp is listed in the public MCP registry as io.github.mir-quadri/nj-transit-mcp. NJ Transit rail, bus and PATH schedules via MCP (scheduled, plus live PATH). This page covers its hosted endpoint (https://nj-transit-mcp.vercel.app/mcp).

### Is the io.github.mir-quadri/nj-transit-mcp server safe to use?

io.github.mir-quadri/nj-transit-mcp scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.mir-quadri/nj-transit-mcp server expose?

io.github.mir-quadri/nj-transit-mcp exposes 6 tools: search_stations, next_departures, trip_between, lines, service_alerts, server_status. Their descriptions and schemas cost roughly 548 tokens of context every time the server is loaded.

### Does the io.github.mir-quadri/nj-transit-mcp server require authentication?

No. We connected to io.github.mir-quadri/nj-transit-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the io.github.mir-quadri/nj-transit-mcp server still maintained?

io.github.mir-quadri/nj-transit-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://nj-transit-mcp.vercel.app/mcp
- Repository: https://github.com/mir-quadri/nj-transit-mcp
- Changelog RSS feed: https://verifymcp.io/servers/mir-quadri-nj-transit-mcp/nj-transit-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mir-quadri-nj-transit-mcp/nj-transit-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mir-quadri-nj-transit-mcp/nj-transit-mcp