events

Is events MCP server safe?

• No hidden instructions were found in its tool descriptions.
• Its error messages showed no secrets or internal details.
• 3 of its 5 tools are labeled read-only; the others may change or send things.
• Overall it scored 83/100 on 29 Oct 2026.

A test can only see what the server shows from outside, not what it does with your data behind the scenes. Connect servers from makers you trust.

What it can do

5 tools, in the server's own words.

Test results

Safe mode: only tools labeled read-only were run. How the test works

• !
  Ready for the newest MCP version

  1 warning

  • !Uses an older MCP version (2025-06-18). It works today, but it isn't on the July 2026 version (2026-07-28) yet.
  note
• !
  Every tool is described

  2 warnings

  • !upcoming_events: Inputs with no description: category, language, limit
  • !create_event: Inputs with no description: name, description
  note
• !
  Bad inputs give a clean error

  2 warnings

  • !search_events: Accepted wrong type for "query" without complaining
  • !upcoming_events: Accepted wrong type for "within_days" without complaining
  • and 2 more
  note
• !
  Follows MCP best practices (not scored yet)

  1 tip (not scored)

  • !2 tools answer with structured data but don't declare its shape (outputSchema): search_events, upcoming_events. If those answers change shape, nothing can catch it; with a schema, every answer is checked.
  note
• ✓
  ConnectsConnected in 376 ms
  pass
• ✓
  Lists its toolsFound 5 tools
  pass
• ✓
  Tools are labeled safe or dangerousEvery tool has a safety label
  pass
• ✓
  No hidden instructionsNo hidden instructions found in tool descriptions
  pass
• ✓
  Tools work with good inputs

  All good

  • ✓search_events: Worked (286 ms)
  • ✓upcoming_events: Worked (139 ms)
  • ✓get_event: Answered with an error, probably because of our sample input: { "error": "No event with slug \"test\". Try search_events." }
  • –register_agent: Not run: labeled as changing data
  • –create_event: Not run: labeled as changing data
  pass
• ✓
  Fast enough

  All good

  • ✓Connecting took 376 ms
  • ✓Listing tools took 61 ms
  • ✓Average tool answer: 183 ms
  • ✓search_events: Slowest tool: search_events (286 ms)
  pass
• ✓
  No secrets leakedChecked 7 error messages: no secrets or internal details
  pass
• –
  Tools work togetherNo tool's answer could be fed into another tool, so there were no chains to test (not counted either way)
  not tested

Test it yourself

Free and open source. Same checks, same score.

Show this score on GitHub

Free for every server in the directory. Paste this into your README: the badge shows the score from our latest test.

Score over time

• 29 Oct 202683

One test so far. New tests will show here.

Reviews

Coming soon: reviews from people who use events, signed in with GitHub, one per person. Reviews never change the score.