# Mobility Database (npm · @pipeworx/mcp-mobility-database)

MobilityData's open catalogue of public-transport feeds — ~4,500 GTFS schedule feeds and ~1,900…

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-mobility-database/mobility-database-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-mobility-database/mobility-database-mcp)
- npm · `@pipeworx/mcp-mobility-database`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database.md), [page](https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-mobility-database`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-mobility-database).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 733 tokens (~244/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**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Mobility Database MCP server?

Mobility Database runs locally as an npm package, launched with npx -y @pipeworx/mcp-mobility-database. 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 pipeworx-io-mobility-database -- npx -y @pipeworx/mcp-mobility-database
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-mobility-database": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-mobility-database"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-mobility-database": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-mobility-database"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-mobility-database -- npx -y @pipeworx/mcp-mobility-database
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-mobility-database": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-mobility-database"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-mobility-database --command npx --arg -y --arg @pipeworx/mcp-mobility-database
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-mobility-database:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-mobility-database"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-mobility-database": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-mobility-database"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-mobility-database -t stdio -c npx -a -y @pipeworx/mcp-mobility-database
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-mobility-database": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-mobility-database"
      ]
    }
  }
}
```

## 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-05 (score 82, +1)

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

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-31 (score 80, +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-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `mobilitydb_search_feeds` (~322 tokens)

Find the public-transport schedule feed (GTFS) for an agency, city or country from the Mobility Database, MobilityData's open catalogue of ~4,500 transit feeds worldwide. Returns the operator's own download URL, the licence it is published under, the geographic bounding box, whether the agency itself publishes it, and whether fetching it needs a credential from the agency. AUTHORITATIVE for "where does this city's transit data come from" — this is the registry the transit-data ecosystem uses, and it names the operator's URL rather than a copy of it. PREFER OVER WEB SEARCH for any question about which transit feeds exist for a place.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2 country code to filter to, e.g. US, FR, JP.
- `data_type` (string): gtfs for scheduled service (the default), gtfs_rt for realtime, or "any" for both.
- `include_inactive` (boolean): Include feeds the catalogue marks deprecated, inactive or superseded by a redirect (default false).
- `limit` (number): Maximum feeds to return (default 25, max 200).
- `municipality` (string): City or municipality name to filter to, e.g. "Chicago".
- `provider` (string): Operator name to filter to, e.g. "Metropolitan Transportation Authority".
- `query` (string): Free text matched against feed name, provider, municipality, region and feed id, e.g. "BART" or "Helsinki".

### `mobilitydb_gtfs_rt_feeds` (~224 tokens)

List the GTFS-Realtime feeds — live vehicle positions, trip updates and service alerts — registered in the Mobility Database for a country, city or operator, with the realtime endpoint URL and the GTFS Schedule feed each one is keyed against. AUTHORITATIVE for which transit agencies publish live data and where: realtime trip ids only resolve against the specific schedule feed named here, so this is what you need before consuming one.

Input parameters:

- `country` (string): ISO 3166-1 alpha-2 country code, e.g. US, DE, JP.
- `entity_type` (string): Which realtime stream: vp (vehicle positions), tu (trip updates), sa (service alerts).
- `group_by_agency` (boolean): Collapse the vp/tu/sa rows an agency publishes into one entry per schedule feed, listing the streams available (default false).
- `limit` (number): Maximum entries to return (default 25, max 200).
- `query` (string): Free text matched against feed name, provider, municipality and feed id.

### `mobilitydb_feed` (~131 tokens)

Everything the Mobility Database records about one transit feed, by its catalogue id (e.g. mdb-1210, or a jbda-* id). Returns the operator's download URL and the catalogue's stable latest-version URL, licence, contact, bounding box, declared GTFS features, publication status, and — for a realtime feed — the GTFS Schedule feed it is keyed against, plus every sibling realtime stream the same agency publishes.

Input parameters:

- `feed_id` (string, required): Mobility Database feed id, e.g. mdb-1210. Shown as `id` by mobilitydb_search_feeds.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Mobility Database MCP server?

Mobility Database is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mobility-database. MobilityData's open catalogue of public-transport feeds, ~4,500 GTFS schedule feeds and ~1,900… This page covers its npm package (@pipeworx/mcp-mobility-database).

### Is the Mobility Database MCP server safe to use?

Mobility Database scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mobility Database MCP server expose?

Mobility Database exposes 3 tools: mobilitydb_search_feeds, mobilitydb_gtfs_rt_feeds, mobilitydb_feed. Their descriptions and schemas cost roughly 677 tokens of context every time the server is loaded.

### Is the Mobility Database MCP server still maintained?

Mobility Database 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.

### What licence is the Mobility Database MCP server under?

Mobility Database declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Mobility Database MCP server?

VerifyMCP ran 16 checks on Mobility Database, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-mobility-database
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-mobility-database
- Repository: https://github.com/pipeworx-io/mcp-mobility-database
- Website: https://pipeworx.io/packs/mobility-database
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-mobility-database/pipeworx-mcp-mobility-database