# LiveSpot (remote · livespot.se)

Find concerts, theatre, sport and festivals in Sweden. Authless, read-only MCP.

- Trust score: 81/100 (high trust)
- Change this week: +8
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- remote · `livespot.se`: 81/100 (this document), [markdown](https://verifymcp.io/servers/se-livespot-mcp/livespot.md), [page](https://verifymcp.io/servers/se-livespot-mcp/livespot)

## Channel facts

- Endpoint: `https://livespot.se/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-09-23.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 815 tokens (~101/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability check failed: schema churn in the 21 days we've observed: 0 tool removals, 3 breaking changes, 0 auth/transport breaks, 0 additions.
- **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.
  - 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 LiveSpot MCP server?

LiveSpot is a hosted endpoint at https://livespot.se/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 se-livespot-mcp 'https://livespot.se/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "se-livespot-mcp": {
      "url": "https://livespot.se/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "se-livespot-mcp": {
      "type": "http",
      "url": "https://livespot.se/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.se-livespot-mcp]
url = "https://livespot.se/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "se-livespot-mcp": {
      "type": "remote",
      "url": "https://livespot.se/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add se-livespot-mcp --url 'https://livespot.se/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  se-livespot-mcp:
    url: "https://livespot.se/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "se-livespot-mcp": {
      "Transport": "http",
      "Url": "https://livespot.se/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add se-livespot-mcp -t streamable-http -u 'https://livespot.se/mcp'
```

### Other

```json
{
  "mcpServers": {
    "se-livespot-mcp": {
      "type": "http",
      "url": "https://livespot.se/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-09-23 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 46 to 50.

### 2026-09-21 (score 80, +1)

- [functional improvement] Tool coverage: 25% → 100%
- [functional improvement] Tool “browse_city” now declares an output schema
- [functional improvement] Tool “get_event” now declares an output schema
- [functional improvement] Tool “get_related_events” now declares an output schema
- [functional improvement] Tool “list_categories” now declares an output schema
- [functional improvement] Tool “list_cities” now declares an output schema
- [functional improvement] Tool “search_events” now declares an output schema

### 2026-09-20 (score 79, +4)

- [security regression] Stability: 0.57 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security improvement] Authorization: unverified → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] “browse_city” made “category” required, so existing callers break
- [functional regression] “browse_city” made “limit” required, so existing callers break
- [functional regression] “get_related_events” made “limit” required, so existing callers break
- [functional regression] “search_events” made “category” required, so existing callers break
- [functional regression] “search_events” made “city” required, so existing callers break
- [functional regression] “search_events” made “endDate” required, so existing callers break
- [functional regression] “search_events” made “limit” required, so existing callers break
- [functional regression] “search_events” made “maxPrice” required, so existing callers break
- [functional regression] “search_events” made “page” required, so existing callers break
- [functional regression] “search_events” made “query” required, so existing callers break
- [functional regression] “search_events” made “startDate” required, so existing callers break

### 2026-09-19 (score 75, +1)

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

### 2026-09-17 (score 74, +1)

- [security] Tool “browse_city” rewrote its description, which is the text the model reads
- [security] Tool “get_event” rewrote its description, which is the text the model reads
- [security] Tool “search_events” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 89 → 98

### 2026-09-15 (score 73, +1)

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

### 2026-09-12 (score 72, +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-09-10 (score 71, +1)

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

## MCP tools (8)

### `search_events` (~299 tokens)

Search events

Search LiveSpot for upcoming events across Sweden. Use this when the user asks what's on, what events are happening, what to do, or anything about concerts, sport, theatre, or shows in a Swedish city. Supports free-text, city, category, date range, and max price. Returns a paginated markdown list of events where each title links to livespot.se. Preserve the markdown links when summarizing so users can click through. City slugs are ASCII (goteborg, malmo); Swedish characters are normalized automatically (å/ä→a, ö→o).

Input parameters:

- `category` (string, required): Category slug. Accepts Swedish or English: konsert/concert, teater/theatre, humor/comedy, etc.
- `city` (string, required): City slug in ASCII (goteborg, malmo, stockholm). Swedish characters are replaced: å/ä→a, ö→o.
- `endDate` (string, required): Include only events on or before this date.
- `limit` (integer, required): Results per page. Defaults to 10 to keep payloads under ~100KB.
- `maxPrice` (integer, required): Upper bound on price_min, in SEK.
- `page` (integer, required): Page number (1-indexed).
- `query` (string, required): Free-text query. Accepts natural-language input like "metallica in stockholm next month".
- `startDate` (string, required): Include only events on or after this date.

Output parameters:

- `events` (array): Matching events.
- `page` (number)
- `total` (number): Total matches across all pages.
- `totalPages` (number)

### `get_event` (~120 tokens)

Get event details

Fetch the full detail for a single event. Accepts a full event id, a full slug, or the 8-character short id at the end of a slug (e.g. "f13a31ab"), as returned by search_events, browse_city, and search. Returns a markdown block with a linked title heading plus description, venue, city, date, and price. Preserve the title link when citing the event so users can click through.

Input parameters:

- `id` (string, required): Event id, slug, or short-id prefix as returned by search_events.

Output parameters:

- `availability`: Ticketing status, e.g. AVAILABLE.
- `away_team`
- `categories`: Category slugs.
- `city`
- `currency`: ISO 4217, usually SEK.
- `description`
- `description_en`
- `description_sv`
- `end_date`: End date/time, ISO 8601.
- `event_status`: Lifecycle status, e.g. scheduled/cancelled.
- `home_team`
- `id` (string): LiveSpot event id.
- `image_url`
- `name` (string): Event title.
- `performers`
- `price_max`: Highest ticket price, in `currency`.
- `price_min`: Lowest ticket price, in `currency`.
- `slug`: URL slug; the last 8 chars work as a short id.
- `source`: Ticketing provider the listing came from.
- `sport`
- `start_date`: Start date/time, ISO 8601.
- `start_time_tbd`: True when only the day is known.
- `url`: Canonical event page on livespot.se.
- `venue`

### `list_cities` (~41 tokens)

List cities

Return all LiveSpot cities with their slug, region, and upcoming-event count. Use the slug (ASCII) as the `city` argument to other tools.

Output parameters:

- `cities` (array)

### `list_categories` (~33 tokens)

List categories

Return the canonical LiveSpot category catalog with both Swedish and English slugs. Pass either slug to other tools as `category`.

Output parameters:

- `categories` (array)

### `browse_city` (~117 tokens)

Browse a city

List upcoming events in a city, optionally narrowed by category. Equivalent to search_events with just {city, category}. Returns markdown bullets where each title links to livespot.se — preserve those links when summarizing. City slugs are ASCII (goteborg, malmo); Swedish characters are normalized automatically.

Input parameters:

- `category` (string, required): Category slug to filter by.
- `city` (string, required): City slug in ASCII (e.g. goteborg, malmo).
- `limit` (integer, required): Max events to return. Default 10.

Output parameters:

- `events` (array): Matching events.
- `total` (number): Total upcoming events matching the city/category.

### `get_related_events` (~70 tokens)

Get related events

Find events related to a given event (same city, nearby date, overlapping category). Returns markdown bullets where each title links to livespot.se — preserve those links when summarizing.

Input parameters:

- `id` (string, required): Event id or slug.
- `limit` (integer, required): Max related events. Default 6.

Output parameters:

- `events` (array): Matching events.

### `search` (~52 tokens)

Search (Deep Research)

Search LiveSpot events. Returns { results: [{ id, title, url }, ...] } per the OpenAI Deep Research spec. Event content originates from third-party ticket providers.

Input parameters:

- `query` (string, required): Search query.

Output parameters:

- `results` (array)

### `fetch` (~53 tokens)

Fetch (Deep Research)

Fetch a single LiveSpot event document. Returns { id, title, text, url, metadata } per the OpenAI Deep Research spec.

Input parameters:

- `id` (string, required): Resource id (event id or slug) returned by search.

Output parameters:

- `id` (string)
- `metadata` (object)
- `text` (string)
- `title` (string)
- `url` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/se-livespot-mcp/livespot#diagnostics

## Score history

- 2026-09-23: 81
- 2026-09-22: 80
- 2026-09-21: 80
- 2026-09-20: 79
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 74
- 2026-09-16: 73
- 2026-09-15: 73
- 2026-09-14: 72
- 2026-09-13: 72
- 2026-09-12: 72
- 2026-09-11: 71
- 2026-09-10: 71
- 2026-09-09: 70
- 2026-09-08: 70
- 2026-09-07: 69
- 2026-09-06: 69
- 2026-09-05: 68
- 2026-09-04: 68
- 2026-09-03: 67
- 2026-09-02: 67

## Common questions

### What is the LiveSpot MCP server?

LiveSpot is an MCP server listed in the public MCP registry as se.livespot/mcp. Find concerts, theatre, sport and festivals in Sweden. Authless, read-only MCP. This page covers its hosted endpoint (https://livespot.se/mcp).

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

LiveSpot scores 81 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 LiveSpot MCP server expose?

LiveSpot exposes 8 tools: search_events, get_event, list_cities, list_categories, browse_city, and 3 more. Their descriptions and schemas cost roughly 785 tokens of context every time the server is loaded.

### Does the LiveSpot MCP server require authentication?

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

### Is the LiveSpot MCP server still maintained?

LiveSpot is still listed as active in the MCP registry. We last reached this channel on 23 September 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://livespot.se/mcp
- Website: https://livespot.se/
- Changelog RSS feed: https://verifymcp.io/servers/se-livespot-mcp/livespot.xml
- Changelog JSON feed: https://verifymcp.io/servers/se-livespot-mcp/livespot.json
- HTML version of this page: https://verifymcp.io/servers/se-livespot-mcp/livespot