Skip to content
LiveSpot logo

LiveSpot MCP server

Which servers in the official MCP registry are LiveSpot's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-20

← Back to LiveSpot

Whose server it is
  • Registry namese.livespot/mcpverified in the MCP registry

The registry name sits under livespot.se. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools8
  • Server calls itselfLiveSpot
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 52 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-20
  • INITE MCP score100 of 100answers 100 · definitions 100 · context 100
  • Answered100% of days7 of 7 daily checks
  • Median first answer454 ms
  • Space in an agent's context≈ 1,272 tokensthe definitions of all its tools (8), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results8 of 8 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · Browse upcoming events filtered by city and date
  • not sure · Compare ticket sellers for a concert or match
  • not sure · Find family-friendly shows and children's events nearby

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers8 tools · read 2026-10-20
  • 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…

  • get_event

    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…

  • 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.

  • list_categories

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

  • browse_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…

  • 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.

  • search

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

  • fetch

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

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "livespot": {
      "type": "http",
      "url": "https://livespot.se/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http livespot https://livespot.se/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://livespot.se/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.