mcpbeat Sign in

Local Events Tracker MCP Server

not responding

Local Events Tracker is listed as active in the registry but did not answer our last check. It exposes 11 tools.

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

Uptime history 11 days of history · worst day 0%
11 days agonow
12.1%
Uptime 24h
11 of 91 checks
11
Tools
read from the server
274 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 3

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 October 2026. No other catalogue keeps this.

17 Oct 2 tool descriptions were rewritten manage_alert_delivery, search_local_events
17 Oct a tool changed the parameters it asks for manage_alert_delivery

Local Events Tracker does not always answer

Over the last week it answered 10.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add local-events --transport http https://localeventstracker.com/mcp
Settings → Connectors → Add custom connector, then paste this address
https://localeventstracker.com/mcp
~/.codex/config.toml
[mcp_servers.local-events]
url = "https://localeventstracker.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "local-events": {
      "url": "https://localeventstracker.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "local-events": {
      "type": "http",
      "url": "https://localeventstracker.com/mcp"
    }
  }
}

Available tools 11

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

manage
manage_alert_delivery
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.
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).
manage_event_watchlist
List, pause, resume, update or delete the user's watchlists by name. Also shows plan limits.
event
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.
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.
local
list_local_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.
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.
followed
get_followed_artists
List the performers and teams this user follows.
save
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.
track
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.
weekend
get_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.

Endpoints

URLTransportStateLatencyChecked
https://localeventstracker.com/mcp streamable-http answering 90 ms 10 min ago

Alternatives to Local Events Tracker

same job, measured the same way
Edgaralert
by ikop32-code

SEC insider trading alerts, Form 4 signals, 8-K events, and company research via EDGAR Alert API.

15 installs/wk local only
ResonanceMetrics
by resonancemetrics

AEO/GEO brand reports and recommendations for agents signed in to ResonanceMetrics.

answering
HostTracker
by hosttracker

Website uptime monitoring: run checks from 300+ locations, manage monitors, alerts and incidents

65 tools answering
The Used Car Index
by theusedcarindex

Free NHTSA recalls, complaints and investigations per vehicle, recall alerts, dealer listing events.

4 tools answering
X
xDog Trading
by xdogtrading

27 live market-research tools for trading agents: scans, options flow, sentiment, valuation, alerts

answering
Prices Deal
by theluckystrike

Track prices and deals: watch a shop page, get target alerts, see price history. Data stays local.

10 tools local only
Appsignal
by pulsemcp

MCP server for AppSignal — get alert details, search logs, and retrieve logs within time ranges.

55 installs/wk local only
Verlon AI MCP
by verlon

Inspect and manage Verlon AI gates, logs, recommendations, and experiments from any MCP client.

43 installs/wk local only

Local Events Tracker — questions

Answers built from our own checks of this server.

What can Local Events Tracker do?
It exposes 11 tools, read directly from the server on our last check. Among them: get_event_changes, get_event_details, get_followed_artists, get_weekend_recommendations, list_local_event_alerts, manage_alert_delivery and 5 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Local Events Tracker mostly used for?
Its tools cluster around manage, event and local. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Local Events Tracker working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 11 of 91 checks got a reply (12.1%), average response time 274 ms. The bar chart above shows every period we have measured.
The registry lists Local Events Tracker as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Local Events Tracker?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Local Events Tracker need an API key?
No. Local Events Tracker completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 11 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Local Events Tracker?
It answers our handshake in 274 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.