What we measured
Over the last 30 days we probed this MCP server 30 times on 30 days; it answered 30 (100%). Median response 1,003 ms, 95th percentile 2,610 ms.
When we called tools/list it returned 4 tools, including search_events, search_local_events, get_event.
Among the 53,642 reachable MCP servers in our snapshot of 2026-11-13 01:12 UTC, it is faster than 26% and higher on readiness than 35%.
From agent-tools.cloud's own probes, last checked 2026-11-12. How we measure
Tools (4)
As returned by the server's own tools/list when we called it.
- search_events
- Search Mappening events by keyword. Returns a page of matching events with basic details (name, dates, price, business). Results don't include a page URL (an ev…
- search_local_events
- Find Mappening events happening near a geographic point ("what's happening near me"), ranked by distance. Optionally filter by keyword, event type GUIDs, and a…
- get_event
- Get full details for a single Mappening event by its GUID, including a real, clickable Mappenings page URL for each location/showtime it's happening at.
- list_event_types
- List Mappening event categories (event types), useful for building filters for search_events / search_local_events.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. For x402 and A2A listings it contributes up to 15 of the 100 quality points; for MCP listings it is shown for reference only. Search order and leaderboards use the separate quality grade (here B, 76.8/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1557 ms). |
| Protocol revision | 0/10 | No protocol revision reported by initialize. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 4 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 0/5 | not seen in a source for over 30 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,642 reachable MCP servers in our daily snapshot (2026-11-13 01:12 UTC). Display only; it does not change search order.
- Readiness
- Higher than 35% of peers
- This listing 74 · peer median 81
- Latency
- Faster than 26% of peers
- This listing 622 ms · peer median 349 ms
Where it loses the most points, and how to win them back
- Protocol revision −10
— Support the current protocol revision.
Now: No protocol revision reported by initialize.
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Freshness + modern flags −5
— Keep the listing current in the registry or source it comes from.
Now: not seen in a source for over 30 days.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/mappenings/server-33/mcpcurl -X POST https://server.smithery.ai/mappenings/server-33/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'