mcpbeat

EventMatey Event Discovery MCP Server

com.eventmatey.mcp/event-discovery
answering

EventMatey Event Discovery is answering right now. Last checked 8 min ago. It exposes 3 tools.

Find public EventMatey events that organisers have approved for AI discovery.

Uptime history 44 hours of history
44 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
170 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add event-discovery --transport http https://mcp.eventmatey.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "event-discovery": {
      "url": "https://mcp.eventmatey.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.event-discovery]
url = "https://mcp.eventmatey.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "event-discovery": {
      "url": "https://mcp.eventmatey.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "event-discovery": {
      "url": "https://mcp.eventmatey.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

events
search_events_by_keyword
Search public EventMatey events by keyword, optional UK location text, date range, categories, and price range. Returns only published and bookable events that the organiser has enabled for AI discovery.
search_events_nearby
Search EventMatey events by location. The current v1 implementation uses location_text plus date/category/price filters. Latitude/longitude and radius are accepted for forward compatibility but are not yet used for true distance search.
event
get_event_details
Get fuller public details for one discoverable EventMatey event, including the canonical hosted booking URL.

Endpoints

URLTransportStateLatencyChecked
https://mcp.eventmatey.com/mcp streamable-http answering 212 ms 8 min ago

EventMatey Event Discovery — questions

Answers built from our own checks of this server.

What can EventMatey Event Discovery do?
It exposes 3 tools, read directly from the server on our last check. Among them: get_event_details, search_events_by_keyword, search_events_nearby. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is EventMatey Event Discovery working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 170 ms. The bar chart above shows every period we have measured.
How do I connect EventMatey Event Discovery?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does EventMatey Event Discovery need an API key?
No. EventMatey Event Discovery completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is EventMatey Event Discovery?
It answers our handshake in 170 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.