# Local Events Tracker (remote · localeventstracker.com)

Search local events, follow artists and interests, get weekend recommendations and change alerts

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `localeventstracker.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/agentstructure-local-events/localeventstracker.md), [page](https://verifymcp.io/servers/agentstructure-local-events/localeventstracker)

## Channel facts

- Endpoint: `https://localeventstracker.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- 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-10-18.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - 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**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1552 tokens (~141/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% 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 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Local Events Tracker MCP server?

Local Events Tracker is a hosted endpoint at https://localeventstracker.com/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 agentstructure-local-events 'https://localeventstracker.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "agentstructure-local-events": {
      "url": "https://localeventstracker.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "agentstructure-local-events": {
      "type": "http",
      "url": "https://localeventstracker.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.agentstructure-local-events]
url = "https://localeventstracker.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "agentstructure-local-events": {
      "type": "remote",
      "url": "https://localeventstracker.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add agentstructure-local-events --url 'https://localeventstracker.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  agentstructure-local-events:
    url: "https://localeventstracker.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "agentstructure-local-events": {
      "Transport": "http",
      "Url": "https://localeventstracker.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add agentstructure-local-events -t streamable-http -u 'https://localeventstracker.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "agentstructure-local-events": {
      "type": "http",
      "url": "https://localeventstracker.com/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-10-18 (score 74, +1)

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

### 2026-10-17 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “manage_alert_delivery” rewrote its description, which is the text the model reads
- [security] Tool “search_local_events” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 127 → 141
- [cosmetic] “manage_alert_delivery” added an optional parameter “code”
- [cosmetic] “manage_alert_delivery” added an optional parameter “consent”
- [cosmetic] “manage_alert_delivery” added an optional parameter “phone”
- [cosmetic] Tool “manage_alert_delivery” changed its title: Email and phone alerts → Email, phone and text alerts

### 2026-10-16 (score 73, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

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

- [functional improvement] Stability: unverified → 0.03

### 2026-10-14 (score 72)

First indexed and scored.

## MCP tools (11)

### `search_local_events` (~313 tokens)

Search local events

Find upcoming events (concerts, comedy, theatre, sports, family shows, festivals) near a US ZIP code, a city or coordinates, filtered by dates, categories (Music, Sports, Arts & Theatre, Film, Miscellaneous, or genres such as Jazz or Comedy), keywords, artist, venue and maximum price. Returns events with local date, time zone, venue, published price range (null means not published, never free), ticket link, provenance, freshness and coverage limits. Sources: Ticketmaster, plus SeatGeek when enabled on this server; each event names its source (SeatGeek events say "Event data from SeatGeek"; credit it). SeatGeek resale_market prices are listed resale prices, not face value. The same event on both sources is shown once, with the other link under other_listings. Coverage varies by country; say so when results are thin. Never invent events beyond the results.

Input parameters:

- `artist` (string)
- `categories` (array)
- `city` (string)
- `country_code` (string)
- `end_date` (string)
- `include_unpriced` (boolean)
- `keywords` (array)
- `latitude` (number)
- `longitude` (number)
- `max_price` (number)
- `page` (integer)
- `radius_km` (number)
- `size` (integer)
- `start_date` (string)
- `venue` (string)
- `zip` (string)

### `get_event_details` (~75 tokens)

Get event details

Full details for one event by event_id (from any other tool): venue, performers, price range if published, ticket link, source records, when AgentStructure first saw it, and its history of detected changes. Refreshes from Ticketmaster when stored data is older than 6 hours.

Input parameters:

- `event_id` (string, required)

### `track_event_interests` (~110 tokens)

Track event interests

Save a persistent watchlist: a place (US ZIP code, city or coordinates, plus radius_km) and/or followed artists or teams, with optional categories, keywords, venues, maximum price and how many days ahead. AgentStructure then checks on a schedule and records newly observed matching events and changes as alerts. Saving again with the same name replaces it. Returns current matches as a preview.

Input parameters:

- `filters` (object, required)
- `name` (string, required)
- `preview` (boolean)

### `list_local_event_alerts` (~114 tokens)

List new event alerts

Return new alerts for this user: newly observed events matching a watchlist or a followed artist, and changes (cancelled, postponed, rescheduled, date, time, venue or price changes, sale start) to matching or saved events. Returned alerts are marked as read. Set refresh true to run a small check right now (limited per hour). An empty list means nothing new, not nothing happening.

Input parameters:

- `include_seen` (boolean)
- `limit` (integer)
- `refresh` (boolean)

### `get_weekend_recommendations` (~174 tokens)

Weekend recommendations

Rank events for the coming weekend (Friday to Sunday local dates) near a saved or given location, using the user's saved interests, followed artists, budget, preferred days and times, and past feedback. Each result says why it was recommended, using only what actually matched. Pass busy intervals from the user's calendar (if the user allowed calendar access in the assistant) to skip conflicts; free/busy is enough, never send event details.

Input parameters:

- `busy` (array)
- `city` (string)
- `country_code` (string)
- `latitude` (number)
- `limit` (integer)
- `location_label` (string)
- `longitude` (number)
- `radius_km` (number)
- `timezone` (string)
- `weekend_of` (string)

### `get_event_changes` (~73 tokens)

Get event changes

Detected changes with previous and current values, for one event_id or for all events the user saved, is going to or marked interested. EVENT_MISSING_FROM_SOURCE is low confidence and does not mean cancelled.

Input parameters:

- `event_id` (string)
- `limit` (integer)
- `since` (string)

### `manage_event_watchlist` (~52 tokens)

Manage watchlists

List, pause, resume, update or delete the user's watchlists by name. Also shows plan limits.

Input parameters:

- `action` (string, required)
- `filters` (object)
- `name` (string)

### `save_event_feedback` (~75 tokens)

Save event feedback

Record the user's reaction to an event: interested, not_interested (never recommend again), going, saved (alerts on changes), more_like_this or less_like_this (adjusts genre weighting). Only call when the user says so; never infer it.

Input parameters:

- `event_id` (string, required)
- `feedback` (string, required)

### `get_followed_artists` (~20 tokens)

Get followed artists

List the performers and teams this user follows.

### `manage_event_profile` (~168 tokens)

Manage event profile

View or change the user's event preferences and privacy: budget, preferred days and times, time zone, interests (artist, team, genre, category, venue, keyword), saved locations (city precision; trips with valid_from/valid_until never replace home), clear personalization, or delete the account and all its data (both need confirm: true and an explicit request from the user).

Input parameters:

- `action` (string, required)
- `confirm` (boolean)
- `currency`
- `interest` (string)
- `interest_type` (string)
- `location` (object)
- `location_label` (string)
- `max_price`
- `preferred_days` (array)
- `preferred_times` (array)
- `timezone`
- `weight` (number)

### `manage_alert_delivery` (~185 tokens)

Email, phone and text alerts

Choose where alerts go besides this chat: add_email sends a confirmation link to the address (alerts start only after the user confirms), add_phone returns a private subscribe link for the free ntfy phone app, add_sms (paid plans, U.S. numbers) texts a 6-digit code to phone; pass consent: true only after the user agreed to receive automated alert texts (msg & data rates may apply, reply STOP to cancel), then verify_sms with the code. remove_email, remove_phone and remove_sms stop them, get shows the current setup. One digest is sent after each daily check; at most one text a day. Only add an address or number the user gave for this purpose.

Input parameters:

- `action` (string, required)
- `code` (string)
- `consent` (boolean)
- `email` (string)
- `phone` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/agentstructure-local-events/localeventstracker#diagnostics

## Score history

- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72

## Common questions

### What is the Local Events Tracker MCP server?

Local Events Tracker is an MCP server listed in the public MCP registry as io.github.agentstructure/local-events. Search local events, follow artists and interests, get weekend recommendations and change alerts. This page covers its hosted endpoint (https://localeventstracker.com/mcp).

### Is the Local Events Tracker MCP server safe to use?

Local Events Tracker 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 Local Events Tracker MCP server expose?

Local Events Tracker exposes 11 tools: search_local_events, get_event_details, track_event_interests, list_local_event_alerts, get_weekend_recommendations, and 6 more. Their descriptions and schemas cost roughly 1,359 tokens of context every time the server is loaded.

### Does the Local Events Tracker MCP server require authentication?

Yes. Local Events Tracker asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the Local Events Tracker MCP server still maintained?

Local Events Tracker is still listed as active in the MCP registry. We last reached this channel on 18 October 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://localeventstracker.com/mcp
- Website: https://localeventstracker.com/
- Changelog RSS feed: https://verifymcp.io/servers/agentstructure-local-events/localeventstracker.xml
- Changelog JSON feed: https://verifymcp.io/servers/agentstructure-local-events/localeventstracker.json
- HTML version of this page: https://verifymcp.io/servers/agentstructure-local-events/localeventstracker