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)
Available components
Last scanned (4 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 548 tokens (~91/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 3 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- Server version: 4.1.5 → 4.1.6 functional
- 2 Nov 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://nj-transit-mcp.vercel.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.vercel.app | CN=WR1,O=Google Trust Services,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 9c5f0e6a35c955e113044c86848e4cd5 |
| SANs: *.vercel.app | ||||||
| CN=WR1,O=Google Trust Services,C=US (CA) | CN=GTS Root R1,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | RSA 2048 | SHA256-RSA | 7fd9e2c2d2048a0474b627a26d0868a7 |
| CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 19 Jun 2020 | 28 Jan 2028 | RSA 4096 | SHA256-RSA | 77bd0d6cdb36f91aea210fc4f058d30d |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nj-transit-mcp.vercel.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| vercel.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nj-transit-mcp.vercel.app/mcp | Verified | 200 | |
| http (plaintext) | http://nj-transit-mcp.vercel.app/mcp | HTTPS enforced | 308 | https://nj-transit-mcp.vercel.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
lines List all routes ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| system | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
next_departures Next departures from a station ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| line | – | – | – |
| station | string | yes | – |
| system | string | – | – |
| towards | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_stations Find NJ Transit, bus, and PATH stations ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | – |
| system | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
server_status Server status and data freshness ~50
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.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
service_alerts Service alerts ~58
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.
| Name | Type | Req | Description |
|---|---|---|---|
| system | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
trip_between Next same-trip trains or buses between two stations ~98
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).
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | – |
| limit | integer | – | – |
| origin | string | yes | – |
| system | string | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · nj-transit-mcp.vercel.app
claude mcp add --transport http mir-quadri-nj-transit-mcp 'https://nj-transit-mcp.vercel.app/mcp'
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.