Skip to content

SFomo: Bay Area events MCP server

ai.sfomo/eventssfomo.aistreamable-httpv0.1.0Scanned

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

6 tools: 1 change things and 5 only read.

Tools: 0 delete, 0 irreversible, 1 write, 5 read.
  • Reads private data · 0
  • Reads text others write · 2
  • Can send data out · 0
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the SFomo: Bay Area events MCP server can do

The SFomo: Bay Area events MCP server is published by sfomo.ai, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: create_custom_calendar), but cannot delete data. 5 tools only read.

2 tools bring in text other people can write (get_event and list_upcoming).

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 11, 2026, version 0.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

6 tools

Changes things 1Claude Code: ask
  • create_custom_calendarBuild a subscribable calendar of upcoming Bay Area events from the user's interests.1 finding

    Why it is in this group

    • The name "create_custom_calendar" says "create": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "create_custom_calendar" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_custom_calendar" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Build a subscribable calendar of upcoming Bay Area events from the user's interests. Returns a link that opens the calendar on Bay Area Events (open_on_bay_area_events; 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 Bay Area Events: 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.

    Annotations the server declares

    • title: Create a custom calendar
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 5Show 5 read-only tools
  • find_performerFind 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 …No findings

    Why it is in this group

    • The name "find_performer" says "find": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Find a performer
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_cityOptional coverage/filter-vocabulary lookup; search_events works directly.No findings

    Why it is in this group

    • The name "get_city" says "get": a word for reading.
    Description, as the server wrote it
    Optional coverage/filter-vocabulary lookup; search_events works directly. Get what Bay Area Events 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. Use it when coverage or an unfamiliar filter value is the question; 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.

    Annotations the server declares

    • title: Get city coverage
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_eventGet 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 ori…Reads text others writeNo findings

    Why it is in this group

    • The name "get_event" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "get" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get one event
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_upcomingBrowse the next N days of events day by day, with no search words.Reads text others writeNo findings

    Why it is in this group

    • The name "list_upcoming" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List upcoming events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_eventsSearch 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…No findings

    Why it is in this group

    • The name "search_events" says "search": a word for reading.
    Description, as the server wrote it
    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. Words in `query` match the title, venue, performers, organizer or tags at the start of a word, singular or plural, with common synonyms (standup = stand-up, kids = children); by default all of them must match, with match "any" (or | / commas between them) any one does. A word that matches nothing is read as the closest word the events use, and `search` in the result says how the query was read. Dates are local (America/Los_Angeles), YYYY-MM-DD. Keyword results come earliest first, at most `limit`; `count` says how many matched in total. Topic/audience tags and venue mapping are incomplete: retry without optional filters when thin, use semantic search when offered, and supplement with web search if there are too few verified options. Check original listings for indoor setting, exact age eligibility, price and remaining tickets. Zero results do not mean no events exist. get_city lists valid filter values. No sign-in; each client gets 30 calls a minute and 2,500 event rows an hour.

    Annotations the server declares

    • title: Search events
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write2
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:27 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://sfomo.ai/mcp: tools/list returned 6 tools to an anonymous client, including create_custom_calendar (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "create_custom_calendar" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "create_custom_calendar" says "create": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 changed.~6 changedView diff
  2. Tools3 changed.~3 changedView diff

Install

Pinned to version 0.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http events https://sfomo.ai/mcp
claude mcp add --transport http events https://sfomo.ai/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__events__find_performer",
      "mcp__events__search_events",
      "mcp__events__get_event",
      "mcp__events__list_upcoming",
      "mcp__events__get_city"
    ],
    "ask": [
      "mcp__events__create_custom_calendar"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as events. Review it before you use it.

Capability tags behind 2 rules
  • mcp__events__get_event untrusted-input
  • mcp__events__list_upcoming untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/ai.sfomo/events/verify?hash=ed1f8f15f6b69943f910c94ffa617f2c83ebbd8806eb537b4cad9ea38daf7541" | jq -e '.changed == false'

Pinned hash ed1f8f15f6b6, from Nov 11, 2026, 21:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/ai.sfomo/events/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for ai.sfomo/events
[![Anlyon Radar](https://radar.anlyon.com/badge/ai.sfomo/events.svg)](https://radar.anlyon.com/servers/ai.sfomo/events)

Source: MCP Registry. Synced Oct 21, 2026, 17:43 UTC.

SFomo: Bay Area events MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the SFomo: Bay Area events MCP server safe?

No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the SFomo: Bay Area events MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the SFomo: Bay Area events MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the SFomo: Bay Area events MCP server have?

6 tools: 1 write, 5 read. create_custom_calendar, find_performer, search_events, get_event, list_upcoming and get_city.

Does the SFomo: Bay Area events MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SFomo: Bay Area events MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the SFomo: Bay Area events MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 11, 2026. Every change is on this page and in its Atom feed.