# Lineup Atlas (remote · lineupatlas.com)

Upcoming club nights, festivals and artist tour dates worldwide, with official ticket links

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

## Components

- remote · `lineupatlas.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp.md), [page](https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp)

## Channel facts

- Endpoint: `https://lineupatlas.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-21.

- **Endpoint Security**: 83/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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 45/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 943 tokens (~94/item across 10 items; 9 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 99/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 96% 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 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 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 Lineup Atlas MCP server?

Lineup Atlas is a hosted endpoint at https://lineupatlas.com/api/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-lineupatlas-lineup-atlas 'https://lineupatlas.com/api/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-lineupatlas-lineup-atlas": {
      "url": "https://lineupatlas.com/api/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-lineupatlas-lineup-atlas": {
      "type": "http",
      "url": "https://lineupatlas.com/api/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-lineupatlas-lineup-atlas]
url = "https://lineupatlas.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-lineupatlas-lineup-atlas": {
      "type": "remote",
      "url": "https://lineupatlas.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-lineupatlas-lineup-atlas --url 'https://lineupatlas.com/api/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-lineupatlas-lineup-atlas:
    url: "https://lineupatlas.com/api/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-lineupatlas-lineup-atlas": {
      "Transport": "http",
      "Url": "https://lineupatlas.com/api/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-lineupatlas-lineup-atlas -t streamable-http -u 'https://lineupatlas.com/api/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-lineupatlas-lineup-atlas": {
      "type": "http",
      "url": "https://lineupatlas.com/api/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 74, 0)

- [functional] Server version: 0.1402.0 → 0.1410.0

### 2026-11-20 (score 74, +1)

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

### 2026-11-19 (score 73, 0)

- [functional] Server version: 0.1390.0 → 0.1402.0

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

- [functional] Server version: 0.1376.0 → 0.1390.0

### 2026-11-17 (score 72, 0)

- [functional] Server version: 0.1369.0 → 0.1376.0

### 2026-11-16 (score 72, 0)

- [functional] Server version: 0.1363.0 → 0.1369.0

### 2026-11-15 (score 72, +1)

- [functional] Server version: 0.1342.0 → 0.1363.0

### 2026-11-14 (score 71, −3)

- [functional improvement] MCP protocol: fail → pass
- [functional] The server now declares the “resources” capability
- [functional] First check of Schema quality: 0
- [functional] MCP protocol version: 2025-06-18 → 2026-07-28
- [functional] New resource “agent-tools-ownership”
- [functional] Server version: 0.1291.0 → 0.1342.0

## MCP tools (9)

### `search_events` (~243 tokens)

Search parties and festivals

Upcoming electronic music parties and festivals listed on Lineup Atlas (past dates are never returned). Filter by text (artist, venue, title), city, country, kind, genre and date range. Each result has its Lineup Atlas page (webUrl): link it when you use the result.

Input parameters:

- `city` (string): City name as written locally, e.g. Berlin, Paris, Amsterdam.
- `country` (string): ISO 3166-1 alpha-2 country code, e.g. DE, FR, NL.
- `from` (string): Earliest start date, ISO 8601 (YYYY-MM-DD).
- `genre` (string): One genre of the Lineup Atlas vocabulary.
- `kind` (string): Only parties (club nights) or only festivals.
- `limit` (integer): How many results (1 to 20, default 10).
- `locale` (string): Language of the texts and page links (default: en).
- `query` (string): Free text: an artist, a venue, a party or festival name.
- `to` (string): Latest start date, ISO 8601 (YYYY-MM-DD).

### `get_event` (~80 tokens)

Get a party or festival

One party or festival by its id or slug (from search_events): dates, venue, line-up, set times when published, practical facts quoted from the official site, ticket link and FAQ.

Input parameters:

- `id` (string, required): The id or slug returned by search_events.
- `locale` (string): Language of the texts and page links (default: en).

### `search_artists` (~98 tokens)

Search artists

DJs and live acts listed on Lineup Atlas, by name or genre, optionally only those playing in a city.

Input parameters:

- `city` (string): Only artists with an upcoming date in this city.
- `limit` (integer): How many results (1 to 20, default 10).
- `locale` (string): Language of the texts and page links (default: en).
- `query` (string): An artist name or a genre.

### `get_artist_dates` (~76 tokens)

Get an artist and their upcoming dates

An artist by slug (from search_artists or search): short bio and every upcoming date listed on Lineup Atlas, with the page of each date.

Input parameters:

- `locale` (string): Language of the texts and page links (default: en).
- `slug` (string, required): The artist slug, e.g. amelie-lens.

### `search_venues` (~82 tokens)

Search clubs and venues

Clubs and venues listed on Lineup Atlas, by name, optionally in one city.

Input parameters:

- `city` (string)
- `limit` (integer): How many results (1 to 20, default 10).
- `locale` (string): Language of the texts and page links (default: en).
- `query` (string): A club or venue name.

### `get_venue_events` (~71 tokens)

Get a club or venue and its upcoming dates

A club or venue by slug (from search_venues or search): address, facts and its upcoming parties.

Input parameters:

- `locale` (string): Language of the texts and page links (default: en).
- `slug` (string, required): The venue slug, e.g. berghain or rex-club.

### `get_city` (~77 tokens)

What's on in a city

A city's page by slug (from list_cities): tonight, this weekend, upcoming parties and festivals, venues and the genres that have a page there.

Input parameters:

- `locale` (string): Language of the texts and page links (default: en).
- `slug` (string, required): The city slug, e.g. berlin, paris, amsterdam.

### `list_cities` (~52 tokens)

List cities

Every city that has a page on Lineup Atlas, with its number of upcoming dates and its slug (for get_city).

Input parameters:

- `locale` (string): Language of the texts and page links (default: en).

### `search` (~66 tokens)

Search everything

The Lineup Atlas search box: artists, parties, festivals, venues, cities and promoters matching a text, strongest first, each with its page.

Input parameters:

- `locale` (string): Language of the texts and page links (default: en).
- `query` (string, required): At least two characters.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp#diagnostics

## Score history

- 2026-11-21: 74
- 2026-11-20: 74
- 2026-11-19: 73
- 2026-11-18: 73
- 2026-11-17: 72
- 2026-11-16: 72
- 2026-11-15: 72
- 2026-11-14: 71
- 2026-11-13: 74
- 2026-11-12: 74
- 2026-11-11: 73
- 2026-11-10: 73

## Common questions

### What is the Lineup Atlas MCP server?

Lineup Atlas is an MCP server listed in the public MCP registry as com.lineupatlas/lineup-atlas. Upcoming club nights, festivals and artist tour dates worldwide, with official ticket links. This page covers its hosted endpoint (https://lineupatlas.com/api/mcp).

### Is the Lineup Atlas MCP server safe to use?

Lineup Atlas scores 74 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 Lineup Atlas MCP server expose?

Lineup Atlas exposes 9 tools: search_events, get_event, search_artists, get_artist_dates, search_venues, and 4 more. Their descriptions and schemas cost roughly 845 tokens of context every time the server is loaded.

### Does the Lineup Atlas MCP server require authentication?

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

### Is the Lineup Atlas MCP server still maintained?

Lineup Atlas 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 Lineup Atlas MCP server?

VerifyMCP ran 13 checks on Lineup Atlas, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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://lineupatlas.com/api/mcp
- Website: https://lineupatlas.com/en/developers
- Changelog RSS feed: https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-lineupatlas-lineup-atlas/api-mcp
