_ registry / mcp streamable-http · checked 5m ago

eventmatey-event-discovery

https://mcp.eventmatey.com

Registry code: f7b484a21be5d334

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.eventmatey.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is eventmatey-event-discovery live?
Yes — it answered the hub's last check (checked 5m ago). It answered 99% of checks over the last 30 days.
Is eventmatey-event-discovery free to use?
Yes — the hub reached it with no key and no payment.
What tools does eventmatey-event-discovery have?
3 tools: search_events_by_keyword, get_event_details, search_events_nearby.
Is eventmatey-event-discovery safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.1%· all time 99.1%

latency
382ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 444 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
topic
productivity & business events & memberships
used for
  • search public events by keyword
  • search events near a location
  • get event details and booking url
takes → gives
text, data → data
tools
3 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_events_nearby reads open 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum number of events to return"
    },
    "end_date": {
      "type": "string",
      "format": "date",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      "description": "Optional inclusive end date in YYYY-MM-DD format"
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Optional latitude for future geo-capable search"
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Optional longitude for future geo-capable search"
    },
    "radius_km": {
      "type": "number",
      "maximum": 250,
      "minimum": 1,
      "description": "Optional search radius in kilometres for future geo-capable search"
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40,
        "minLength": 1
      },
      "maxItems": 10,
      "description": "Optional category or tag filters"
    },
    "start_date": {
      "type": "string",
      "format": "date",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      "description": "Optional inclusive start date in YYYY-MM-DD format"
    },
    "location_text": {
      "type": "string",
      "maxLength": 160,
      "minLength": 1,
      "description": "Use this for the current v1 location search, such as Bristol or Leeds"
    },
    "max_price_gbp": {
      "type": "number",
      "maximum": 100000,
      "minimum": 0,
      "description": "Optional maximum price in GBP"
    },
    "min_price_gbp": {
      "type": "number",
      "maximum": 100000,
      "minimum": 0,
      "description": "Optional minimum price in GBP"
    }
  }
}
    arguments 71 lines
  • search_events_by_keyword reads unknown 14h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "keyword"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 10,
      "maximum": 25,
      "minimum": 1,
      "description": "Maximum number of events to return"
    },
    "keyword": {
      "type": "string",
      "maxLength": 120,
      "minLength": 1,
      "description": "Keyword or phrase to search for, such as baking class or live music"
    },
    "end_date": {
      "type": "string",
      "format": "date",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      "description": "Optional inclusive end date in YYYY-MM-DD format"
    },
    "categories": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 40,
        "minLength": 1
      },
      "maxItems": 10,
      "description": "Optional category or tag filters"
    },
    "start_date": {
      "type": "string",
      "format": "date",
      "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$",
      "description": "Optional inclusive start date in YYYY-MM-DD format"
    },
    "location_text": {
      "type": "string",
      "maxLength": 160,
      "minLength": 1,
      "description": "Optional UK location hint such as Bristol, Manchester, or London"
    },
    "max_price_gbp": {
      "type": "number",
      "maximum": 100000,
      "minimum": 0,
      "description": "Optional maximum price in GBP"
    },
    "min_price_gbp": {
      "type": "number",
      "maximum": 100000,
      "minimum": 0,
      "description": "Optional minimum price in GBP"
    }
  }
}
    arguments 62 lines
  • get_event_details reads unknown 14h ago

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

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "event_id"
  ],
  "properties": {
    "event_id": {
      "type": "string",
      "format": "uuid",
      "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000)$",
      "description": "EventMatey event UUID"
    }
  }
}
    arguments 15 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id f7b484a21be5d334.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/f7b484a21be5d334/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/f7b484a21be5d334/badge.svg)](https://brick.blue/agent/f7b484a21be5d334?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.