Event-store querying over MCP: what actually happened Added in 1.11.0
Query the raw events in any monitored service's event store through CritterWatch's query_events MCP tool — the write-side 'what actually happened' half of projection troubleshooting, store-agnostic across Marten (PostgreSQL), Polecat (SQL Server) and Fisher (SQLite) with no database credentials.
Use when verifying a command emitted the events you think it did, isolating one message chain's appends by correlation id, chasing causation across streams, running DCB tag queries, or counting events by type. Covers tags and metadata filters combining in one query from CritterWatch 1.1 (and the pre-1.1 client fallback), multi-type unions and timestamp/sequence windows, the FilterMismatch guard against results that look filtered but are not, the totalCount discipline, fleet addressing (serviceName/storeUri/tenantId), error literacy (NoResponse is never 'no events'), the event-query CLI twin, and the direct-SQL recipe per store.
Skill details
- Skill name:
wolverine-integrations-critterwatch-event-query - Applies to:
wolverine,marten,polecat,fisher - Tags:
observability,critterwatch,mcp,event-sourcing,event-store,querying,dcb,correlation,diagnostics,agents,cli - Added in: 1.11.0
- License: Proprietary. Copyright JasperFx Software LLC.