Is Eventsorg safe and trustworthy?

tashan scores Eventsorg on public evidence — tashan score 45.0/100, it is currently active, note: a single primary maintainer (bus-factor risk), no known advisories against the current release, its declared dependencies reach: cloud, credentials, database, network. Audit scope: OSV advisories, install-time scripts, build provenance and declared permission surface. We do not review source code or execute the capability.

How do I install Eventsorg?

In Claude Code: run `claude mcp add eventsorg -- npx -y eventsorg-mcp`. In Cursor / Claude Desktop, add it to mcp.json / claude_desktop_config.json.

‹ The Index

Eventsorg

npm

An open-source Model Context Protocol (MCP) server and background autonomous agent designed to run the logistics of live events.

Works with: Claude Code, Cursor, Claude Desktop, Codex CLI, Gemini CLI, Cline, Windsurf, VS Code (installable)
installable: each client documents how to load an MCP server of this type — that is the client's promise, not a claim verified against this capability

Work: Agent development

Who it is for: AI engineer

Install (Claude Code):

claude mcp add eventsorg -- npx -y eventsorg-mcp

solid

“3 worked examples; short of deep on per-tool docs and a stated limitation”

This grade is wrong ›

tashan score: 45.0
Instruction depth: 63.0 (solid — documents the job properly, with examples you could follow)
Adoption: 34/wk
Upkeep: 55.0
Freshness: 90.0
Evidence coverage: 100% of the inputs this score can use
Health: active
License: ISC

Security audit

Every finding is shown in full — which advisory, the version that fixes it, and the exact command run at install time. Nothing in this audit is behind a licence.

No known advisoriesclearchecked against OSV for 1.0.2

Talks to cloud provider APIs · Handles credentials or secrets · Connects to databases · Makes network requestsfrom declared dependencies

Can carry remote content into your agentit can pull third-party text into the model's context — treat what it returns as untrusted input

No build provenanceno attestation — the published artifact cannot be traced to its source

What changed recently

2026-08-11 eventsorg-mcp now reaches cloud, credentials, database, network Its declared dependencies reach further into your machine than they did before.

You are reading this because you came looking. tashan Pro gives tashan doctor the history behind it, so a run over your own config says which of YOURS moved.

You searched for one. Check the rest of your stack:

npx tashan-cli doctor

Reads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.

tashan Pro$6/mo

We recorded 1 change to Eventsorg in the last 45 days. Pro tells you on the day — for the servers in your own config, not the ones you thought to look up.

Every score since we started measuring, for any capability
The named replacement when something you run is dying — not just that it is
tashan doctor over the config you already have, on your machine

Start a 7-day trial › Everything measured on this page stays free.

Show your score

Measured this well? Put the live badge in your README — it updates as the score does.

[![tashan](https://tashan.sh/badge/pkg-eventsorg-mcp.svg)](https://tashan.sh/capability/pkg-eventsorg-mcp.html)

npm ↗ · source ↗ · pkg:eventsorg-mcp

Already running this? npx tashan-cli doctor checks your whole config against the Index — how it works ›

Measured 2026-08-14 · scorer s5 · how · something wrong here?