EventMatey Event Discovery
REMOTE · MCP.EVENTMATEY.COM
Find public EventMatey events that organisers have approved for AI discovery.
Available components
Last scanned (23 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 21 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- 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 Usability79
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 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
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation 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 in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Oct 26 75
- Server version: 1.0.12 → 1.0.18 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Server version: 1.0.10 → 1.0.12 functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 21 Nov 2026 · Probed https://mcp.eventmatey.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=eventmatey.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4bae58bcca9ea8f0e1f758334ee8fcc |
| SANs: eventmatey.com, mcp.eventmatey.com, *.mcp.eventmatey.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.eventmatey.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| eventmatey.com. | No DS | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.eventmatey.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.eventmatey.com/mcp | Inconclusive | 406 |
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 →
get_event_details ~42
Get fuller public details for one discoverable EventMatey event, including the canonical hosted booking URL.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | EventMatey event UUID |
No output schema declared.
No examples provided.
search_events_by_keyword ~179
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.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | Optional category or tag filters |
| end_date | string | – | Optional inclusive end date in YYYY-MM-DD format |
| keyword | string | yes | 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 |
No output schema declared.
No examples provided.
search_events_nearby ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
How do I install the EventMatey Event Discovery MCP server?
EventMatey Event Discovery is a hosted endpoint at https://mcp.eventmatey.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 · mcp.eventmatey.com
claude mcp add --transport http com-eventmatey-mcp-event-discovery 'https://mcp.eventmatey.com/mcp'
What is the EventMatey Event Discovery MCP server?
EventMatey Event Discovery is an MCP server listed in the public MCP registry as com.eventmatey.mcp/event-discovery. Find public EventMatey events that organisers have approved for AI discovery. This page covers its hosted endpoint (https://mcp.eventmatey.com/mcp).
Is the EventMatey Event Discovery MCP server safe to use?
EventMatey Event Discovery scores 75 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 EventMatey Event Discovery MCP server expose?
EventMatey Event Discovery exposes 3 tools: search_events_by_keyword, search_events_nearby, get_event_details. Their descriptions and schemas cost roughly 437 tokens of context every time the server is loaded.
Does the EventMatey Event Discovery MCP server require authentication?
No. We connected to EventMatey Event Discovery without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the EventMatey Event Discovery MCP server still maintained?
EventMatey Event Discovery is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the EventMatey Event Discovery MCP server?
VerifyMCP ran 11 checks on EventMatey Event Discovery, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about EventMatey Event Discovery: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.