# Suumer

> Local US events by town, date and kind (trivia, live music, karaoke...), each checked at its source.

- name: com.suumer/events
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 82/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.suumer%2Fevents
- tools: https://api.protogrid.dev/v1/servers/com.suumer%2Fevents/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "events": {
      "type": "http",
      "url": "https://suumer.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 98
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-94% +updated-18d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 2 of 2 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,011 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 100 (weight 15)

- pass `stability.changes`: 2 tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 2, about 1,011 tokens to load them all
- tool set hash: b49dbf9ec7af1717d0ab35eb290535c5
- tools last changed: 2026-10-28T16:59:42.207Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.suumer/events.svg)](https://protogrid.dev/servers/com.suumer/events)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-28 `report_listing_problem` added
  - Use when the person says a Suumer listing is wrong (the time changed, it was cancelled or moved, the place is wrong, it is not open to the public) and wants Suumer told, or agrees when you offer. Sends one report to Suumer's review queue holding only the listing and which part is wrong, picked from a fixed list: no note, name, email or account is sent or kept. A person at Suumer checks the listing against its source; nothing on the listing changes by itself. Take the listing from the suumerPage of a find_events result. The same report sent twice in a day counts once.
- 2026-10-28 `find_events` changed (description, inputSchema, outputSchema)
  - before: Things to do on one day near one US town (trivia, live music, karaoke, comedy, games, markets, talks and more), each checked against the page it came from. Give a town ("Columbus, OH" or a 5-digit ZIP), a date, and optionally a kind of event. Each result has its own Suumer page to cite (suumerPage), and the original source page when we can show it.
  - after: Things to do on one day near one US town (trivia, live music, karaoke, comedy, games, markets, talks and more), each checked against the page it came from. Give the town the person asked about ("Denver, CO", "Tampa, FL" or "Sacramento, CA") or a 5-digit ZIP, a date, and optionally a kind of event. With no town, the rough town the app shares is used, if it shares one. Read-only: it changes nothing. US events only, at most 25 per call, soonest first. Each result has its own Suumer page to cite (suumerPage), and the original source page when we can show it.

Full history: https://api.protogrid.dev/v1/servers/com.suumer%2Fevents/changes

## Remotes

- https://suumer.com/mcp (streamable-http, auth none, reachable true, uptime30d 0.9411765)

## Packages

_none_

## Tools (2)

- `find_events`: Things to do on one day near one US town (trivia, live music, karaoke, comedy, games, markets, talks and more), each checked against the page it came from. Give the town the person asked about ("Denver, CO", "Tampa, FL" or "Sacramento, CA") or a 5-digit ZIP, a date, and optionally a kind of event. With no town, the rough town the app shares is used, if it shares one. Read-only: it changes nothing. US events only, at most 25 per call, soonest first. Each result has its own Suumer page to cite (suumerPage), and the original source page when we can show it.
- `report_listing_problem`: Use when the person says a Suumer listing is wrong (the time changed, it was cancelled or moved, the place is wrong, it is not open to the public) and wants Suumer told, or agrees when you offer. Sends one report to Suumer's review queue holding only the listing and which part is wrong, picked from a fixed list: no note, name, email or account is sent or kept. A person at Suumer checks the listing against its source; nothing on the listing changes by itself. Take the listing from the suumerPage of a find_events result. The same report sent twice in a day counts once.