# mcp-event-intelligence

Durable temporal event intelligence: composite triggers, derived events, and runtime wakeups.

- **Type:** MCP server
- **Trust:** 85/100 (A), scored on the package rubric
- **Verification:** verified (build provenance)
- **Version:** 0.4.0
- **Author:** io.github.sarooo17
- **License:** Apache-2.0
- **npm:** mcp-event-intelligence
- **Source:** https://github.com/sarooo17/event-intelligence
- **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport)

## Trust

85/100 (A), scored on the package rubric
- Publisher verified: no
- Build provenance: verified attestation
- npm trusted publishing (OIDC): yes
- Install scripts: nothing suspicious found
- Prompt-injection scan: not run
- Obfuscation scan: not run
- Evidence age: 6 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-09-25T22:16:31.638Z
- **Version scanned:** 0.4.0
- **CVEs:** none found by OSV at scan time

## Tools

15 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `erpnext.sales_invoice.submitted` — A Sales Invoice reached submitted status in ERPNext.
- `erpnext.sales_order.created` — A Sales Order was created in ERPNext.
- `event_sources_list` — List active event sources currently available to Event Intelligence.
- `trigger_plan` — Compile an agent-friendly trigger plan into a validated durable trigger definition using the event sources currently available. This does not mutate state and d
- `trigger_list` — List durable triggers and lifecycle state, optionally scoped to the configured owner.
- `trigger_inspect` — Explain a trigger deterministically, including missing clauses, temporal state, deadlines, lineage, derived outputs and wake receipt.
- `trigger_simulate` — Run a trigger definition against an isolated event sequence without mutating live state.
- `derived_contracts_list` — List versioned derived-event contracts, canonical schemas, fingerprints and registered producers.
- `wake_hydrate` — Hydrate a composite wake into an Activation Envelope containing the configured continuation and matched event evidence. Evidence data is included only according
- `runtime_status` — Return local Event Intelligence runtime status, restored counts, host-managed MCP event connections and pending temporal deadlines.
- `trigger_create` — Create a durable trigger. Persistent MCP mutations require explicit confirmationId and MCP_WRITE_ENABLED=true.
- `trigger_pause` — Pause a durable trigger after explicit confirmation.
- `trigger_resume` — Resume a paused durable trigger after explicit confirmation.
- `trigger_delete` — Delete a durable trigger after explicit confirmation.
- `trigger_update` — Create a new immutable version of an existing durable trigger after explicit confirmation.

## Install

**Verdict: install** — No blocking findings and no open coverage gaps — safe to install as configured.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"mcp-event-intelligence\": {\n      \"command\": \"npx\",\n      \"args\": [\n        \"-y\",\n        \"mcp-event-intelligence\"\n      ],\n      \"env\": {\n        \"RUNTIME_WAKE_TARGETS_JSON\": \"<YOUR_RUNTIME_WAKE_TARGETS_JSON>\",\n        \"TYPESAFE_API_KEY\": \"<YOUR_TYPESAFE_API_KEY>\"\n      }\n    }\n  }\n}"
```
**Credentials it will ask for** (names only — Forge never holds a value):
- `RUNTIME_WAKE_TARGETS_JSON` — Runtime Wake Targets Json (optional)
- `TYPESAFE_API_KEY` — Typesafe API Key (optional)
Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each <YOUR_NAME> in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one.
- This entry needs 2 credentials (0 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset.

## Blast radius

Extensive blast radius — deletes data; holds an api key.
- Floor 53, ceiling 53 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/mcp-event-intelligence
- Install plan: https://forgeregistry.com/api/v1/packages/mcp-event-intelligence/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/mcp-event-intelligence
- HTML page: https://forgeregistry.com/registry/mcp-event-intelligence
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.