# Commlo commute network (remote · public.commlo.com)

Dated rail commute times to downtown for home addresses in the US metro areas Commlo covers.

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

## Components

- remote · `public.commlo.com`: 61/100 (this document), [markdown](https://verifymcp.io/servers/com-commlo-commute-network/public.md), [page](https://verifymcp.io/servers/com-commlo-commute-network/public)

## Channel facts

- Endpoint: `https://public.commlo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.1`

## 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-21.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 40/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 1200 tokens (~400/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 34% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Commlo commute network MCP server?

Commlo commute network is a hosted endpoint at https://public.commlo.com/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 com-commlo-commute-network 'https://public.commlo.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-commlo-commute-network": {
      "url": "https://public.commlo.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-commlo-commute-network": {
      "type": "http",
      "url": "https://public.commlo.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-commlo-commute-network]
url = "https://public.commlo.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-commlo-commute-network": {
      "type": "remote",
      "url": "https://public.commlo.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-commlo-commute-network --url 'https://public.commlo.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-commlo-commute-network:
    url: "https://public.commlo.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-commlo-commute-network": {
      "Transport": "http",
      "Url": "https://public.commlo.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-commlo-commute-network -t streamable-http -u 'https://public.commlo.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-commlo-commute-network": {
      "type": "http",
      "url": "https://public.commlo.com/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-21 (score 61, +1)

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

### 2026-11-20 (score 60, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “commute_lookup” rewrote its description, which is the text the model reads
- [security] Tool “commute_lookup_batch” rewrote its description, which is the text the model reads
- [security] Tool “station_info” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 371 → 420
- [functional] Server version: 1.2.0 → 1.2.1
- [functional] Server version: 1.0.0 → 1.2.0
- [cosmetic] “commute_lookup” reworded the description of “arrive_by”
- [cosmetic] “commute_lookup” reworded the description of “depart_after”
- [cosmetic] “commute_lookup_batch” reworded the description of “arrive_by”
- [cosmetic] “commute_lookup_batch” reworded the description of “depart_after”
- [cosmetic] “station_info” reworded the description of “arrive_by”
- [cosmetic] “station_info” reworded the description of “depart_after”

### 2026-11-19 (score 60, +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-18 (score 59, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-17 (score 59)

First indexed and scored.

## MCP tools (3)

### `commute_lookup` (~408 tokens)

Commute lookup

Commute to downtown from a residential address the user names (a home they are considering, never the device's location) on one service date: drive (without traffic) or walk to a rail station, a station buffer and the scheduled train. Any US home address; one outside coverage returns the covered areas. window_id only where supported. Up to 5 options, nearest first, with sources and methodology.

Input parameters:

- `address_id` (string)
- `address_text` (string)
- `arrive_by` (string): A clock time on the service date (H:MM, HH:MM, or HH:MM:SS, local time in the region of the address or station) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00,…
- `buffer_seconds` (integer)
- `components` (object)
- `context` (object): Optional. Fill only with facts the user volunteered. No names, contact details or chat text.
- `depart_after` (string): A clock time on the service date (H:MM, HH:MM, or HH:MM:SS, local time in the region of the address or station) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00,…
- `direction` (string)
- `options` (integer): How many options to return, from 1 to 5, default 3. The nearest one or two stations are always included, so an answer can hold more options than requested.
- `service_date` (string, required)
- `terminal_id` (string)
- `window_id` (string)

### `commute_lookup_batch` (~371 tokens)

Commute lookup, batch

The same dated commute as commute_lookup for up to 10 US home addresses in one call, for comparing homes. Returns one result per address in request order; an address that cannot be answered (including one outside coverage) gets its own error entry and the others still answer. Default 1 option per address.

Input parameters:

- `addresses` (array, required)
- `arrive_by` (string): A clock time on the service date (H:MM, HH:MM, or HH:MM:SS, local time in the region of the address or station) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00,…
- `buffer_seconds` (integer)
- `context` (object): Optional. Fill only with facts the user volunteered. No names, contact details or chat text.
- `depart_after` (string): A clock time on the service date (H:MM, HH:MM, or HH:MM:SS, local time in the region of the address or station) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00,…
- `direction` (string)
- `options` (integer): Options per address, from 1 to 3, default 1. The nearest one or two stations are always included, so an answer can hold more options than requested.
- `service_date` (string, required)
- `terminal_id` (string)
- `window_id` (string)

### `station_info` (~306 tokens)

Station info

Facts about one covered rail station on one service date, by station ID or name: its routes, the downtown terminals it serves and facility links when known.

Input parameters:

- `arrive_by` (string): A clock time on the service date (H:MM, HH:MM, or HH:MM:SS, local time in the region of the address or station) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00,…
- `buffer_seconds` (integer)
- `context` (object): Optional. Fill only with facts the user volunteered. No names, contact details or chat text.
- `depart_after` (string): A clock time on the service date (H:MM, HH:MM, or HH:MM:SS, local time in the region of the address or station) or an RFC 3339 date-time with an offset, for example 09:00, 2026-11-12T09:00:00-06:00,…
- `direction` (string)
- `name` (string)
- `service_date` (string, required)
- `station_id` (string)
- `terminal_id` (string)
- `window_id` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-commlo-commute-network/public#diagnostics

## Score history

- 2026-11-21: 61
- 2026-11-20: 60
- 2026-11-19: 60
- 2026-11-18: 59
- 2026-11-17: 59

## Common questions

### What is the Commlo commute network MCP server?

Commlo commute network is an MCP server listed in the public MCP registry as com.commlo/commute-network. Dated rail commute times to downtown for home addresses in the US metro areas Commlo covers. This page covers its hosted endpoint (https://public.commlo.com/mcp).

### Is the Commlo commute network MCP server safe to use?

Commlo commute network scores 61 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 Commlo commute network MCP server expose?

Commlo commute network exposes 3 tools: commute_lookup, commute_lookup_batch, station_info. Their descriptions and schemas cost roughly 1,085 tokens of context every time the server is loaded.

### Does the Commlo commute network MCP server require authentication?

No. We connected to Commlo commute network without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Commlo commute network MCP server still maintained?

Commlo commute network is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Commlo commute network MCP server?

VerifyMCP ran 12 checks on Commlo commute network, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Commlo commute network: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://public.commlo.com/mcp
- Website: https://commlo.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-commlo-commute-network/public.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-commlo-commute-network/public/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-commlo-commute-network/public.json
- HTML version of this page: https://verifymcp.io/servers/com-commlo-commute-network/public
