protogrid

Search / ai.sfomo/events

SFomo: Bay Area events

R0· no sign-in

Read-only search of upcoming SF Bay Area events: AI/tech, dance, music, arts, food, fitness.

v0.1.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality75good
Trust82of 100
Uptime, 30 days95%
Latency p50280 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "events": {
      "type": "http",
      "url": "https://sfomo.ai/mcp"
    }
  }
}
claude mcp add --transport http events https://sfomo.ai/mcp
[mcp_servers.events]
url = "https://sfomo.ai/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "events": {
      "type": "remote",
      "url": "https://sfomo.ai/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "events": {
      "type": "http",
      "url": "https://sfomo.ai/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=events&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vc2ZvbW8uYWkvbWNwIn0%3D"
}
{
  "servers": {
    "events": {
      "type": "http",
      "url": "https://sfomo.ai/mcp"
    }
  }
}
{
  "mcpServers": {
    "events": {
      "httpUrl": "https://sfomo.ai/mcp"
    }
  }
}
extensions:
  "events":
    enabled: true
    name: "events"
    type: streamable_http
    uri: "https://sfomo.ai/mcp"
    timeout: 300

Quality 75 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene100 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations6 of 6 tools declare readOnlyHint or destructiveHint
  • pass
    tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
  • pass
    tools.token_costabout 3,930 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability25 · weight 15
  • warn
    stability.changes19 tool changes in 30 days
  • fail
    stability.rug_pull4 tools kept their name but changed most of their description in 30 days; review before trusting them
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

6 tools, about 3,930 tokens to load them all · tool set 32be9649c874 · tools last changed 2026-10-20 · checked 2026-10-20 11:08 UTC

Tool changes

  • get_cityadded

    Get what SFomo covers in Bay Area: how many upcoming events it lists and for which dates, when the data was last published, how many sources feed it, and upcoming events per category, topic, neighborhood and town. Call it before searching to pick valid category, topic, neighborhood and town values, or to tell a user what this site covers; it returns counts only, no events (use search_events or list_upcoming for those). Takes no arguments. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  • list_upcomingchangeddescription, input schema, output schemameaning changed
    before

    List the next N days of events, optionally for one category, topic or place. `by_day` counts every match per date; when there are more than `limit`, the rows shown are spread across the days (earliest first within each day), so narrow with category, topic or place, or page a single day with search_events from/to.

    after · 38% of words in common

    Browse the next N days of events day by day, with no search words. `by_day` counts every match per date, and when more events match than `limit` the rows are spread evenly across the days (earliest first within each day), so each day is represented. Use it for overviews like "what's happening this week"; for search words, free-only, a town or exact from/to dates use search_events, and for one event's details get_event. Optional filters: one category or topic, an audience, and a place: `neighborhood` keeps events inside a named area (radius_km widens it past the boundary), `near` ranks events by distance from a place or "lat,lon" within radius_km. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  • get_eventchangeddescription, output schemameaning changed
    before

    Look up one upcoming event by its stable `id` (as returned by search_events / list_upcoming), with its source link and first_seen / last_seen / last_fetched dates.

    after · 25% of words in common

    Get the full listing for one upcoming event by the `id` that search_events, list_upcoming or find_performer returned: 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. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  • search_eventschangeddescription, input schema, output schemameaning changed
    before

    Search upcoming Bay Area events (dance, AI, music, arts, food, sports, comedy, fun, exercise, volunteer, dating). All words in `query` must match title/location/performers/organizer/tags. Dates are local (America/Los_Angeles), YYYY-MM-DD.

    after · 26% of words in common

    Search every upcoming Bay Area event by words, dates, price, topic or place: dance, AI, music, arts, food, sports, comedy, exercise, volunteering, dating, business and professional networking. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, for one act by name find_performer. All words in `query` must appear in the title, venue, performers, organizer or tags; dates are local (America/Los_Angeles), YYYY-MM-DD. Results come earliest first, at most `limit`; `count` says how many matched in total, so narrow the search rather than paging. get_city lists valid neighborhood, town, category and topic values. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  • create_custom_calendarchangeddescription, input schema, output schema
    before

    Build a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on SFomo (open_on_sfomo; give the user this first), subscribe links (Google Calendar, Apple/Outlook webcal, plain .ics) and a preview. The calendar refreshes itself every few hours, so new matching events keep appearing. An event is included if it matches ANY interest and no exclude term. Nothing is stored by SFomo: the interests are encoded in the link itself. Interview the user first (see the custom_calendar prompt), check matches with search_events, and call this again to adjust.

    after · 79% of words in common

    Build a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on SFomo (open_on_sfomo; give the user this first), subscribe links (Google Calendar, Apple/Outlook webcal, plain .ics) and a preview. The calendar refreshes itself every few hours, so new matching events keep appearing. An event is included if it matches ANY interest and no exclude term. Nothing is stored by SFomo: the interests are encoded in the link itself. Interview the user first (see the custom_calendar prompt), check matches with search_events, and call this again to adjust. For a one-off answer rather than a standing calendar, use search_events. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  • find_performerchangeddescription, output schema
    before

    Find a performer, band, comedian or act in Bay Area by name (words in `query` must all match; case-insensitive) and get their upcoming events, top venues, genres or topics and the platforms that list them. Names come only from public event listings; there are no contact details. Use it for "when is <band> playing" or "who plays at <venue>". Use get_event with an id for one event's full listing.

    after · 81% of words in common

    Find a performer, band, comedian or act in Bay Area by name (words in `query` must all match; case-insensitive) and get their upcoming events, top venues, genres or topics and the platforms that list them. Names come only from public event listings; there are no contact details. Use it for "when is <band> playing" or "who plays at <venue>". For events by topic or venue rather than by name, use search_events; use get_event with an id for one event's full listing. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

  • list_upcomingchangedtitle, description, input schema, annotationsmeaning changed
    before

    List the next N days of events, optionally for one category.

    after · 25% of words in common

    List the next N days of events, optionally for one category, topic or place. `by_day` counts every match per date; when there are more than `limit`, the rows shown are spread across the days (earliest first within each day), so narrow with category, topic or place, or page a single day with search_events from/to.

  • get_eventchangedtitle, annotations
  • search_eventschangedtitle, annotations
  • create_custom_calendarchangedtitle, annotations

Showing the latest 10. Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 82 / 100

no-repository
provenance55
liveness98
freshness100
hygiene80

+dns-namespace +website +reachable +uptime-95% +updated-12d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://sfomo.ai/mcp streamable-httpnoneyes95%280 ms2025-11-252026-10-20

Tools (6)

create_custom_calendarread-onlyBuild a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on SFomo (open_on_sfomo; give the user this first), subscribe links (Google Calendar, Apple/Outlook webcal, plain .ics) and a preview. The calendar refreshes itself every few hours, so new matching events keep appearing. An event is included if it matches ANY interest and no exclude term. Nothing is stored by SFomo: the interests are encoded in the link itself. Interview the user first (see the custom_calendar prompt), check matches with search_events, and call this again to adjust. For a one-off answer rather than a standing calendar, use search_events. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
find_performerread-onlyFind a performer, band, comedian or act in Bay Area by name (words in `query` must all match; case-insensitive) and get their upcoming events, top venues, genres or topics and the platforms that list them. Names come only from public event listings; there are no contact details. Use it for "when is <band> playing" or "who plays at <venue>". For events by topic or venue rather than by name, use search_events; use get_event with an id for one event's full listing. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
get_cityread-onlyGet what SFomo covers in Bay Area: how many upcoming events it lists and for which dates, when the data was last published, how many sources feed it, and upcoming events per category, topic, neighborhood and town. Call it before searching to pick valid category, topic, neighborhood and town values, or to tell a user what this site covers; it returns counts only, no events (use search_events or list_upcoming for those). Takes no arguments. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
get_eventread-onlyGet the full listing for one upcoming event by the `id` that search_events, list_upcoming or find_performer returned: 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. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
list_upcomingread-onlyBrowse the next N days of events day by day, with no search words. `by_day` counts every match per date, and when more events match than `limit` the rows are spread evenly across the days (earliest first within each day), so each day is represented. Use it for overviews like "what's happening this week"; for search words, free-only, a town or exact from/to dates use search_events, and for one event's details get_event. Optional filters: one category or topic, an audience, and a place: `neighborhood` keeps events inside a named area (radius_km widens it past the boundary), `near` ranks events by distance from a place or "lat,lon" within radius_km. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.
search_eventsread-onlySearch every upcoming Bay Area event by words, dates, price, topic or place: dance, AI, music, arts, food, sports, comedy, exercise, volunteering, dating, business and professional networking. Use it whenever the question has search words, a date range ("this weekend": from/to), free-only, a town or an area; for a day-by-day overview of the next few days with no search words use list_upcoming, for one act by name find_performer. All words in `query` must appear in the title, venue, performers, organizer or tags; dates are local (America/Los_Angeles), YYYY-MM-DD. Results come earliest first, at most `limit`; `count` says how many matched in total, so narrow the search rather than paging. get_city lists valid neighborhood, town, category and topic values. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "ai.sfomo/events",
  "title": "SFomo: Bay Area events",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://sfomo.ai/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "0.1.0",
  "websiteUrl": "https://sfomo.ai/agents/",
  "description": "Read-only search of upcoming SF Bay Area events: AI/tech, dance, music, arts, food, fitness."
}