# Istanbul MCP (remote · istanbulmcp-production.up.railway.app)

Read-only Istanbul open city data: transport, parking, water, nearby services and datasets.

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

## Components

- remote · `istanbulmcp-production.up.railway.app`: 73/100 (this document), [markdown](https://verifymcp.io/servers/batu1-1an-istanbul-mcp/istanbulmcp-production.md), [page](https://verifymcp.io/servers/batu1-1an-istanbul-mcp/istanbulmcp-production)

## Channel facts

- Endpoint: `https://istanbulmcp-production.up.railway.app/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.6`

## 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**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Istanbul MCP server?

Istanbul MCP is a hosted endpoint at https://istanbulmcp-production.up.railway.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 batu1-1an-istanbul-mcp 'https://istanbulmcp-production.up.railway.app/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "batu1-1an-istanbul-mcp": {
      "url": "https://istanbulmcp-production.up.railway.app/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "batu1-1an-istanbul-mcp": {
      "type": "http",
      "url": "https://istanbulmcp-production.up.railway.app/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.batu1-1an-istanbul-mcp]
url = "https://istanbulmcp-production.up.railway.app/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "batu1-1an-istanbul-mcp": {
      "type": "remote",
      "url": "https://istanbulmcp-production.up.railway.app/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add batu1-1an-istanbul-mcp --url 'https://istanbulmcp-production.up.railway.app/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  batu1-1an-istanbul-mcp:
    url: "https://istanbulmcp-production.up.railway.app/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "batu1-1an-istanbul-mcp": {
      "Transport": "http",
      "Url": "https://istanbulmcp-production.up.railway.app/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add batu1-1an-istanbul-mcp -t streamable-http -u 'https://istanbulmcp-production.up.railway.app/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "batu1-1an-istanbul-mcp": {
      "type": "http",
      "url": "https://istanbulmcp-production.up.railway.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-05 (score 73, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Stability: 0.33 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-03 (score 73, +1)

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

### 2026-11-01 (score 72, +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-10-30 (score 71, +1)

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

### 2026-10-29 (score 70, 0)

- [security regression] HSTS header: unverified → fail
- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] Stability: unverified → 0.13
- [functional improvement] MCP protocol: unverified → pass

### 2026-10-28 (score 70, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.07 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-10-27 (score 70, +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-26 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

## MCP tools (18)

### `istanbul_health` (~16 tokens)

İstanbul servis durumu

Return Istanbul MCP service readiness.

### `istanbul_search_datasets` (~37 tokens)

İBB veri seti arama

Search the IBB open data catalog.

Input parameters:

- `formats`
- `limit`
- `query` (string, required)

### `istanbul_get_dataset` (~29 tokens)

İBB veri seti bilgileri

Return metadata and resources for one IBB dataset.

Input parameters:

- `dataset_id` (string, required)

### `istanbul_get_resource_schema` (~29 tokens)

İBB kaynak kolonları

Return DataStore field schema for a resource.

Input parameters:

- `resource_id` (string, required)

### `istanbul_query_resource` (~79 tokens)

İBB kaynak kayıtları

Query IBB CKAN DataStore records with guarded filters and limits.

    API reference: https://docs.ckan.org/en/latest/maintaining/datastore.html
    Uses datastore_search, not SQL; field names come from the resource schema.

Input parameters:

- `filters`
- `limit`
- `resource_id` (string, required)

### `istanbul_nearby` (~192 tokens)

Yakındaki İstanbul hizmetleri

Find city services by kind and coordinates, or parking/pharmacy by district.

    bbox and types apply only to city_feature (parking, metro_station,
    air_quality_station, public_transport_stop, wifi, ev_charging, taxi_stand,
    market). air_quality includes latest readings; city_feature has station
    locations only. Static layers return published locations, not live status.
    District lists have no distances. Pharmacy records include name, district, address, phone, map links,
    provenance and freshness; maps_search_url is address search, not a verified pin.
    Pharmacy duty-end times are not guaranteed. Card/social locations are static,
    not live operating status.

Input parameters:

- `bbox`
- `district`
- `kind` (string)
- `lat`
- `limit`
- `lon`
- `radius_m`
- `types`

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_traffic_status` (~19 tokens)

İstanbul trafik yoğunluğu

Return Istanbul citywide traffic index.

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_water_status` (~111 tokens)

İSKİ su ve baraj durumu

Get ISKI active faults (district or fault_number) or dam occupancy.

    Dam filters apply only to dams; fault_number is exclusive with district.
    Nearby faults are provided by istanbul_nearby(kind="water_fault"). Results
    carry fallback freshness and approximate fault locations; no restoration guarantee.

Input parameters:

- `dam_name`
- `district`
- `fault_number`
- `kind` (string)
- `limit`
- `min_occupancy`

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_mobility_nearby` (~127 tokens)

Yakındaki ulaşım seçenekleri

Summarize mobility near a static place reference or coordinates.

    district (all 39 Istanbul districts) is exclusive with place/coordinates and
    returns parking only, without distances. District-only place names do the same.
    For Acıbadem specify 'Acıbadem, Kadıköy' or 'Acıbadem, Üsküdar'. Not address geocoding.

Input parameters:

- `district`
- `lat`
- `limit`
- `lon`
- `place`
- `radius_m` (integer)

### `istanbul_city_services_nearby` (~146 tokens)

Yakındaki WiFi ve kütüphaneler

Summarize WiFi near a static reference point and district-level libraries/culture.

    district (all 39 Istanbul districts) is exclusive with place/coordinates;
    district-only place names also return district address lists, without WiFi or
    invented distances. Radius applies only to WiFi with a point. For Acıbadem,
    specify 'Acıbadem, Kadıköy' or 'Acıbadem, Üsküdar'. Not full address geocoding.

Input parameters:

- `district`
- `lat`
- `limit`
- `lon`
- `place`
- `radius_m` (integer)

### `istanbul_neighborhood_profile` (~44 tokens)

İstanbul mahalle profili

Return a joined neighborhood profile from social, building, and earthquake scenario records.

Input parameters:

- `district` (string, required)
- `limit`
- `neighborhood`

### `istanbul_transit_line` (~80 tokens)

İETT hat bilgileri ve tarifesi

Get IETT line info, ordered stops or planned main-terminal departures.

    limit applies only to departures. This is not live intermediate-stop ETA.
    Cross-operator service notices are provided by istanbul_transport_disruptions.

Input parameters:

- `action` (string)
- `limit`
- `line_code` (string, required)

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_transport_disruptions` (~45 tokens)

Ulaşım aksaklıkları ve duyurular

Return current official disruptions and service announcements across supported transport operators.

Input parameters:

- `limit`
- `line`
- `mode`
- `operator`

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_metro_accessibility_status` (~70 tokens)

Metro ekipman ve arıza durumu

Return official Metro İstanbul equipment/total counts and current equipment fault details, optionally filtered by line, station, or equipment type. This is not an end-to-end accessibility guarantee.

Input parameters:

- `equipment_type`
- `limit`
- `line`
- `station`

### `istanbul_datastore_query` (~179 tokens)

Sınırlı açık veri SQL sorgusu

Run a bounded SELECT over records from one allowlisted CKAN resource.

    SQLite dialect: use table records and published column names. GROUP BY and
    aggregates are supported; no writes, arbitrary functions or application DB.
    A complete bounded capture is required, never partial counts. The server
    enforces an outer result limit (default 20, max 100) even if SQL omits LIMIT.
    Only resources configured in CKAN_SQL_ALLOWED_RESOURCE_IDS are available.
    Local query syntax and bounds: https://github.com/Batu1-1an/istanbulmcp/blob/main/docs/datastore-sql.md
    Source API: https://docs.ckan.org/en/latest/maintaining/datastore.html

Input parameters:

- `limit`
- `resource_id` (string, required)
- `sql` (string, required)

### `istanbul_market_schedule` (~92 tokens)

İstanbul pazar takvimi

Return the published weekly İBB market schedule, optionally by district/day.

    day accepts Turkish/English weekdays, today/yesterday/tomorrow, or an ISO
    date. Results are a static weekly schedule, not proof a market is open today;
    coordinates are source points and maps_url is a map search link.

Input parameters:

- `day`
- `district`
- `limit`

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_next_departures` (~260 tokens)

Planlı GTFS durak kalkışları

Search GTFS stop names or return published departures for selected stops.

    Use stop_query with limit only to discover stop_id candidates by name,
    including Turkish/ASCII spellings (Kadıköy/kadikoy). This mode returns stops,
    NOT departures. Same-name stops remain separate; never choose the first
    automatically. Approximate spelling suggestions are labeled, not matches.
    Ask the user to select a candidate using name/map, then call with stop_id.
    stop_code identifies the published stop sign when present. stop_desc and
    platform_direction_text preserve source text; they are not inferred route directions.
    Missing metadata stays null; districts are not inferred.

    at is an ISO datetime with a UTC offset; omitted means now in Europe/Istanbul.
    The search covers 24 hours. stop_id and coordinates are mutually exclusive.
    line matches the published route short name. Times are scheduled, never live
    ETA, delays or proof of service. Outside-calendar queries are unavailable.

Input parameters:

- `at`
- `lat`
- `limit`
- `line`
- `lon`
- `radius_m` (integer)
- `stop_id`
- `stop_query`

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

### `istanbul_gtfs_snapshot_status` (~75 tokens)

GTFS tarife anlık görüntü durumu

Inspect local GTFS load age, calendar validity, row counts and skipped rows.

    No upstream request or refresh is made. A missing or warming snapshot is
    unavailable, not an empty timetable. Cache age is not feed publication age;
    a loaded snapshot does not prove live arrivals or transport service.

Output parameters:

- `data` (array)
- `error`
- `freshness`
- `geojson`
- `limits` (array)
- `next_queries` (array)
- `ok` (boolean)
- `pagination`
- `result_info`
- `sources` (array)
- `summary` (string)
- `warnings` (array)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/batu1-1an-istanbul-mcp/istanbulmcp-production#diagnostics

## Score history

- 2026-11-05: 73
- 2026-11-04: 73
- 2026-11-03: 73
- 2026-11-02: 72
- 2026-11-01: 72
- 2026-10-31: 71
- 2026-10-30: 71
- 2026-10-29: 70
- 2026-10-28: 70
- 2026-10-27: 70
- 2026-10-26: 69
- 2026-10-25: 69

## Common questions

### What is the Istanbul MCP server?

Istanbul MCP is listed in the public MCP registry as io.github.Batu1-1an/istanbul-mcp. Read-only Istanbul open city data: transport, parking, water, nearby services and datasets. This page covers its hosted endpoint (https://istanbulmcp-production.up.railway.app/mcp/).

### Is the Istanbul MCP server safe to use?

Istanbul MCP scores 73 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 Istanbul MCP server expose?

Istanbul MCP exposes 18 tools: istanbul_health, istanbul_search_datasets, istanbul_get_dataset, istanbul_get_resource_schema, istanbul_query_resource, and 13 more. Their descriptions and schemas cost roughly 1,630 tokens of context every time the server is loaded.

### Does the Istanbul MCP server require authentication?

Its publisher declares no required credentials for Istanbul MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Istanbul MCP server still maintained?

Istanbul MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 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://istanbulmcp-production.up.railway.app/mcp/
- Repository: https://github.com/Batu1-1an/istanbulmcp
- Changelog RSS feed: https://verifymcp.io/servers/batu1-1an-istanbul-mcp/istanbulmcp-production.xml
- Changelog JSON feed: https://verifymcp.io/servers/batu1-1an-istanbul-mcp/istanbulmcp-production.json
- HTML version of this page: https://verifymcp.io/servers/batu1-1an-istanbul-mcp/istanbulmcp-production