# EventMatey Event Discovery (remote · mcp.eventmatey.com)

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

- Trust score: 62/100 (medium)
- Change this week: +1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.eventmatey.com`: 62/100 (this document), [markdown](https://verifymcp.io/servers/com-eventmatey-mcp-event-discovery/mcp.md), [page](https://verifymcp.io/servers/com-eventmatey-mcp-event-discovery/mcp)

## Channel facts

- Endpoint: `https://mcp.eventmatey.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.8`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 437 tokens (~145/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-eventmatey-mcp-event-discovery https://mcp.eventmatey.com/mcp
```

### Codex

```toml
[mcp_servers.com-eventmatey-mcp-event-discovery]
url = "https://mcp.eventmatey.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-eventmatey-mcp-event-discovery": {
      "type": "remote",
      "url": "https://mcp.eventmatey.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-eventmatey-mcp-event-discovery --url https://mcp.eventmatey.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-eventmatey-mcp-event-discovery:
    url: "https://mcp.eventmatey.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-eventmatey-mcp-event-discovery": {
      "type": "http",
      "url": "https://mcp.eventmatey.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 62, +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.

### 2026-07-31 (score 61, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 60)

First indexed and scored.

## MCP tools (3)

### `search_events_by_keyword` (~179 tokens)

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.

Input parameters:

- `categories` (array): Optional category or tag filters
- `end_date` (string): Optional inclusive end date in YYYY-MM-DD format
- `keyword` (string, required): Keyword or phrase to search for, such as baking class or live music
- `limit` (integer): Maximum number of events to return
- `location_text` (string): Optional UK location hint such as Bristol, Manchester, or London
- `max_price_gbp` (number): Optional maximum price in GBP
- `min_price_gbp` (number): Optional minimum price in GBP
- `start_date` (string): Optional inclusive start date in YYYY-MM-DD format

### `search_events_nearby` (~216 tokens)

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.

Input parameters:

- `categories` (array): Optional category or tag filters
- `end_date` (string): Optional inclusive end date in YYYY-MM-DD format
- `latitude` (number): Optional latitude for future geo-capable search
- `limit` (integer): Maximum number of events to return
- `location_text` (string): Use this for the current v1 location search, such as Bristol or Leeds
- `longitude` (number): Optional longitude for future geo-capable search
- `max_price_gbp` (number): Optional maximum price in GBP
- `min_price_gbp` (number): Optional minimum price in GBP
- `radius_km` (number): Optional search radius in kilometres for future geo-capable search
- `start_date` (string): Optional inclusive start date in YYYY-MM-DD format

### `get_event_details` (~42 tokens)

Get fuller public details for one discoverable EventMatey event, including the canonical hosted booking URL.

Input parameters:

- `event_id` (string, required): EventMatey event UUID

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-eventmatey-mcp-event-discovery/mcp#diagnostics

## Score history

- 2026-08-03: 62
- 2026-08-02: 62
- 2026-08-01: 61
- 2026-07-31: 61
- 2026-07-30: 63
- 2026-07-29: 62
- 2026-07-28: 62
- 2026-07-27: 61
- 2026-07-26: 60

## Links

- Remote endpoint: https://mcp.eventmatey.com/mcp
- Website: https://mcp.eventmatey.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-eventmatey-mcp-event-discovery/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-eventmatey-mcp-event-discovery/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-eventmatey-mcp-event-discovery/mcp