Suumer
REMOTE · SUUMER.COM
Local US events by town, date and kind (trivia, live music, karaoke...), each checked at its source.
Available components
Last scanned (9 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 615 tokens (~307/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
- Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (50% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_events” rewrote its description, which is the text the model reads security
- Schema quality: 246 → 307 ▼ functional
- Tool “find_events” now declares an output schema ▲ functional
- First check of Tool coverage: 50 functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “report_listing_problem” functional
- “find_events” reworded the description of “kind” cosmetic
- “find_events” reworded the description of “town” cosmetic
- “find_events” made “town” optional cosmetic
- 28 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 27 Oct 26 70
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://suumer.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=suumer.com | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6b7c89435bc599c6ad076e84834527ab0bb |
| SANs: *.suumer.com, suumer.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of suumer.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| suumer.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' https://static.cloudflareinsights.com https://www.instagram.com; style-src 'self'; img-src 'self' data: https:; connect-src 'self' https://cloudflareinsights.com; frame-src https://www.youtube-nocookie.com https://www.facebook.com https://www.instagram.com https://www.tiktok.com https://www.snapchat.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://suumer.com/mcp | Verified | 200 | |
| http (plaintext) | http://suumer.com/mcp | HTTPS enforced | 301 | https://suumer.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_events Find local events on Suumer ~266
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | The day, written YYYY-MM-DD. Leave it out for today in that town. |
| kind | string | – | Kind of event. Leave it out (or "all") for everything. live_music covers concerts, bands, orchestras and choirs. |
| town | string | – | The US town and state the person asked about, like "Denver, CO", "Tampa, FL" or "Sacramento, CA", or a 5-digit ZIP code. Leave it out to use the rough town the app shares. |
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| events | array | yes | – |
| kind | string | yes | – |
| moreUrl | string | yes | – |
| total | integer | yes | – |
| town | string | yes | – |
No examples provided.
report_listing_problem Tell Suumer a listing is wrong ~230
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.
| Name | Type | Req | Description |
|---|---|---|---|
| listing | string | yes | The listing's Suumer page (https://suumer.com/e/...) or its id. |
| problem | string | yes | Which part is wrong: wrong_facts = the name, time, or other facts are wrong; cancelled_or_moved = it was cancelled or moved; wrong_place = the place or address is wrong; not_a_public_event = it is no… |
No output schema declared.
No examples provided.
How do I install the Suumer MCP server?
Suumer is a hosted endpoint at https://suumer.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · suumer.com
claude mcp add --transport http com-suumer-events 'https://suumer.com/mcp'
What is the Suumer MCP server?
Suumer is an MCP server listed in the public MCP registry as com.suumer/events. Local US events by town, date and kind (trivia, live music, karaoke...), each checked at its source. This page covers its hosted endpoint (https://suumer.com/mcp).
Is the Suumer MCP server safe to use?
Suumer scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Suumer MCP server expose?
Suumer exposes 2 tools: find_events, report_listing_problem. Their descriptions and schemas cost roughly 496 tokens of context every time the server is loaded.
Does the Suumer MCP server require authentication?
No. We connected to Suumer without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Suumer MCP server still maintained?
Suumer is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.