← Index

OpenAgenda

com.openagenda/mcpv1.3.2Search

Search, analyze and manage events on OpenAgenda.

In-path gate · all MCP tools

Using OpenAgenda in Claude, Cursor, Gemini CLI, Cline, or Zed?

MCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and HOLDs the call when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use Install this server for that).

Install the mcpindex gate (one command)

Rewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less

uv tool install mcpindex-gate && mcpindex-config-wire
Trust verdict · v1 advisory · method
NOT YET SCREENEDno verdict on file

Verdict not yet evaluated for this tool. The semantic screen takes adversarial cases first; coverage rolls out as the corpus expands (15/150 labels to graduation). The deterministic conformance probe is built but has not yet run on the public corpus, so a recorded verdict here is REVIEW or UNVERIFIED, never a clearing ALLOW. Until a verdict is recorded, an agent should treat this tool as not-yet-cleared and fall back to its own checks. Method: the eval, four-state verdict, honest limits.

Own this server? Screen its description →

That verdict was true at screening time (snapshot 2026-07-26).

Contracts can change after screening, with no version bump. The gate pins OpenAgenda’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.

See your first HOLD in 2 minutes →

Related: how to trust an MCP server · screen before install · silent contract drift

Environment variables
OA_API_KEY
requiredsecret

OpenAgenda API key (the stdio credential — a least-privilege/read key is advised). The hosted remote uses OAuth instead.

OA_BASE_URL

v3 API base URL (defaults to https://api.openagenda.com/v3).

OA_EXECUTOR

Code engine: node (default — Node's permission sandbox: no filesystem/subprocess; network NOT bounded) or deno (adds a scoped network egress boundary; recommended hardening, needs deno installed).

OA_LOCAL_NO_SANDBOX

Disable the Node permission sandbox entirely (bare node, NO boundary at all) — trusted/dev use only.

MCP quality score · maturity, not trust · methodology
freshness
25
completeness
20
installability
25
documentation
15
stability
10
Alternatives in Search