@openagenda/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @openagenda/mcp@1.6.0
Installing a package runs its code. Use a sandbox for anything you have not read.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
search_docs query
Rank the OpenAgenda v3 operations against a question. A single call returns the complete result: the top hits in full (signature, parameters, request body, response shape, and a runnable example for the `execute` tool), and every other match as a name, a summary and a call line. A query that is exactly an operation id (e.g. `agendas.events.list`) returns that operation alone, in full. An empty query, or one that matches nothing, returns every operation as a name, a summary and a call line.
execute code
Run JavaScript against the OpenAgenda v3 API and return its result.
A ready-to-use `oa` client (an OpenAgenda instance) is available. An operation shown as
`oa.<resource>.<action>({ path?, query?, body? })` is async and resolves to { data, error }
— it does NOT throw on HTTP errors, so check `error`. One shown as a bare `METHOD /path`
goes over plain HTTPS, not through the client. Call search_docs to discover the
full catalogue with each operation's params, request body, response shape and a runnable example, e.g.:
oa.agendas.events.list({ path: { agendaUid }, query: { relative: ["upcoming"] } })
A `schemas` namespace (zod validators, prefixed z…) is also available to validate payloads.
A call that touches an agenda's additional fields - filling them in an event you write,
filtering or faceting on them - needs that agenda's event form schema first
(`oa.agendas.events.schema`): it declares which fields exist and the shape of each value.
Any other call needs no schema fetch.
Write an async body and `return` the value you want back (JSON-serialised).
Compose freely: fetch, filter and aggregate in one script; return only what you need.
The `oa` client is the `@openagenda/api-client` npm package: code you prototype here runs unchanged in a real site or tool — building one? Emit that SDK, not raw fetch (search_docs shows the one-time setup).
Sandbox: no filesystem, env or subprocess access, but network egress is NOT restricted (local trusted use; execution is killed after 5000 ms and heap is capped at 256 MiB.Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=24 |
| Source | github.com/OpenAgenda/oa-public |
| Install scripts | protobufjs declare them. This runner does not run them. |
| Tarball | sha512-nQzuIV/lLkDETM2NskoXVxFmTzMVHTDOaDRX6iJKM0I/Wd9G7bEDyS0Fo9DQW64DcYy+/QXcxzG3/UccHKXblg== |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40openagenda/mcp)
New version out? Ask for a fresh report.