What's Up In: local events

{
  "mcpServers": {
    "ai.whatsupin/events": {
      "url": "https://whatsupin.ai/mcp"
    }
  }
}

Indexed tools

Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.

6 shown · authentication unknown

• Get one city's coverage

  get_city

  Get what one What's Up In city covers: how many upcoming events it lists and for which dates, when its data was last published, how many sources feed it, and upcoming events per category, topic, neighborhood and town. Call it before searching a city to pick valid category, topic, neighborhood and town values, or to tell a user what that city covers; it returns counts only, no events (use search_events or list_upcoming for those, list_cities for every city at once). No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  Schema valid · SHA-256 b99c3eecf0e9…

  View input schema

  {
    "type": "object",
    "properties": {
      "city": {
        "type": "string",
        "description": "Which city (name or slug): Boston, Chicago, Los Angeles, Orange County, Sacramento, San Diego, San Francisco, Seattle, Atlanta, Cancún, Colorado Springs & Pueblo, DC, Denver, Detroit, Houston, Las Vegas, Mexico City, New York, Philadelphia, Phoenix, Portland, Salt Lake City. list_cities has the full list."
      }
    },
    "required": [
      "city"
    ]
  }

• Get one event

  get_event

  Get the full listing for one upcoming event by the `id` that search_events or list_upcoming returned, passing the same `city` it came from: title, dates, venue, price (all-in, or "See tickets"), the original listing (`link`), every source that lists it and first_seen / last_seen / last_fetched dates. Ids stay the same while an event is listed; a past or removed event returns an error, so search again. (search_across_cities results carry `on_site` links instead.) No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  Schema valid · SHA-256 779b3e5775e1…