Local Events Tracker
REMOTE · LOCALEVENTSTRACKER.COM
Search local events, follow artists and interests, get weekend recommendations and change alerts
Available components
Last scanned (12 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Entertainment and Games
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 18 Oct 26 +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.
- 17 Oct 26 0
- 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 security
- Schema quality: 127 → 141 ▼ functional
- “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 cosmetic
- 16 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 15 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 14 Oct 26 72
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 18 Oct 2026 · Probed https://localeventstracker.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=localeventstracker.com | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 55cd4311f3dfb344034bd499b1ed0514f9e |
| SANs: localeventstracker.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of localeventstracker.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| localeventstracker.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://localeventstracker.com/mcp | Verified | 200 | |
| http (plaintext) | http://localeventstracker.com/mcp | HTTPS enforced | 308 | https://localeventstracker.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_event_changes Get event changes ~73
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | – | – |
| limit | integer | – | – |
| since | string | – | – |
No output schema declared.
No examples provided.
get_event_details Get event details ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
No output schema declared.
No examples provided.
get_followed_artists Get followed artists ~20
List the performers and teams this user follows.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_weekend_recommendations Weekend recommendations ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| busy | array | – | – |
| city | string | – | – |
| country_code | string | – | – |
| latitude | number | – | – |
| limit | integer | – | – |
| location_label | string | – | – |
| longitude | number | – | – |
| radius_km | number | – | – |
| timezone | string | – | – |
| weekend_of | string | – | – |
No output schema declared.
No examples provided.
list_local_event_alerts List new event alerts ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_seen | boolean | – | – |
| limit | integer | – | – |
| refresh | boolean | – | – |
No output schema declared.
No examples provided.
manage_alert_delivery Email, phone and text alerts ~185
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| code | string | – | – |
| consent | boolean | – | – |
| string | – | – | |
| phone | string | – | – |
No output schema declared.
No examples provided.
manage_event_profile Manage event profile ~168
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).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| confirm | boolean | – | – |
| currency | – | – | – |
| interest | string | – | – |
| interest_type | string | – | – |
| location | object | – | – |
| location_label | string | – | – |
| max_price | – | – | – |
| preferred_days | array | – | – |
| preferred_times | array | – | – |
| timezone | – | – | – |
| weight | number | – | – |
No output schema declared.
No examples provided.
manage_event_watchlist Manage watchlists ~52
List, pause, resume, update or delete the user's watchlists by name. Also shows plan limits.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| filters | object | – | – |
| name | string | – | – |
No output schema declared.
No examples provided.
save_event_feedback Save event feedback ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | – |
| feedback | string | yes | – |
No output schema declared.
No examples provided.
search_local_events Search local events ~313
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
track_event_interests Track event interests ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filters | object | yes | – |
| name | string | yes | – |
| preview | boolean | – | – |
No output schema declared.
No examples provided.
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.
remote · localeventstracker.com
claude mcp add --transport http agentstructure-local-events 'https://localeventstracker.com/mcp'
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.