Show HN: Metrics, Monitoring, and Alerting for Agents

ChirrOp released @chirropjs/chirrop-mcp, an MCP server that exposes the full ChirrOp monitoring API as tools, resources and prompts to MCP-compatible clients including Claude Code, Claude Desktop and Cursor, installable via npm or npx. The server separates its own CHIRROP_API_KEY credential, which can never be referenced from a tool call, from CHIRROP_SECRET_-prefixed variables for notification destinations such as Slack, Discord and Telegram, so a prompt-injected request cannot send the API key to an attacker's webhook; destination URLs and credentials are redacted in tool output and the chirrop://destinations resource.

MCP server for the ChirrOp https://www.chirrop.com monitoring platform. Exposes the full ChirrOp API as tools, resources, and prompts for any MCP-compatible client Claude Code, Claude Desktop, Cursor, etc. . npm install @chirropjs/chirrop-mcp Or run directly: npx @chirropjs/chirrop-mcp | Variable | Required | Purpose | |---|---|---| | CHIRROP API KEY | Yes | Your ChirrOp API key, used by the server to call the ChirrOp API. Must start with chp . | | CHIRROP SECRET <NAME | No | Secrets for notification destinations webhook URLs, bot tokens that you want to reference as env:CHIRROP SECRET <NAME instead of pasting them into the conversation. See Destination secrets destination-secrets . | These are two separate kinds of variable on purpose. CHIRROP API KEY is the server's own credential and can never be referenced from a tool call. Only CHIRROP SECRET -prefixed variables can, so a prompt-injected request can't send your API key to an attacker's webhook. Set the variables wherever your MCP client launches the server. The server does not read .env files itself. Pass the key when adding the server: claude mcp add chirrop -e CHIRROP API KEY=chp your api key -- npx -y @chirropjs/chirrop-mcp To keep the key out of a committed .mcp.json , export it in your shell instead and reference it from the config: export CHIRROP API KEY=chp your api key { "mcpServers": { "chirrop": { "command": "npx", "args": "-y", "@chirropjs/chirrop-mcp" , "env": { "CHIRROP API KEY": "${CHIRROP API KEY}" } } } } Claude Code expands ${CHIRROP API KEY} from the environment it was started in, so export the variable before running claude , then check the connection with /mcp . Add to your claude desktop config.json : { "mcpServers": { "chirrop": { "command": "npx", "args": "-y", "@chirropjs/chirrop-mcp" , "env": { "CHIRROP API KEY": "chp your api key" } } } } Slack, Discord and webhook URLs and Telegram bot tokens are secrets. Rather than pasting them into the conversation, add them to the server's environment with a CHIRROP SECRET prefix: "env": { "CHIRROP API KEY": "chp your api key", "CHIRROP SECRET SLACK URL": "https://hooks.slack.com/services/T000/B000/XXXX", "CHIRROP SECRET TELEGRAM TOKEN": "123456:ABC-your-bot-token" } Then refer to them by name when creating or updating a destination, e.g. "create a Slack destination using env:CHIRROP SECRET SLACK URL " . The tool call then contains: { "channel": "slack", "url": "env:CHIRROP SECRET SLACK URL", "scope": "all", "policy ids": , "enabled": true } - References to any variable without the CHIRROP SECRET prefix including CHIRROP API KEY are refused. - Restart the server after adding a variable; a reference to an unset variable returns an error. - Destination URLs and credentials are redacted in everything the server returns tools and the chirrop://destinations resource , e.g. https://hooks.slack.com/ redacted . Email address and Telegram chat id stay visible because they identify the recipient rather than authenticate. - Event references : every tool that takes an event id UUID also accepts event the event name plus an optional agent — the server resolves the UUID for you. compare events accepts a mix of UUIDs and exact names. - Pagination : list events and list alerts default to 50 results and return has more / next offset for paging. - Cheap reads : get event rollups supports summary only=true to return just the statistical summary plus anomalous buckets. - Timestamps : time-series and health responses include retrieved at so staleness can be reasoned about reliably. - Secrets : destination url and credentials values accept env:CHIRROP SECRET <NAME references and are redacted in output. See Destination secrets destination-secrets . - Idempotent logging : send logs returns the log id of every entry generated if you didn't supply one . If a send fails, retry with the same log id s so nothing is double-counted. - Health checks : get stream health and get agent summary compare each policy's threshold against the latest bucket of that policy's own period minute/hour/day . In get agent summary , a stream whose data couldn't be fetched shows status: "error" with the reason, rather than appearing stale. - No deletes : the ChirrOp API has no delete operations. Retire policies and destinations by setting enabled: false ; event definitions cannot be removed. | Tool | Description | |---|---| | send logs | Send up to 250 log entries to ChirrOp, with per-entry results including each log id for safe retries | | Tool | Description | |---|---| | list events | List event definitions, filterable by agent/name, with pagination | | list agents | List distinct agent identities and their event counts | | get event | Get a single event definition | | create event | Create a new event definition | | update event | Update event metadata | | get event rollups | Get time-bucketed rollup data minute/hour/day with anomaly/trend enrichment; summary only for a cheap overview | | get stream health | One-call health check: staleness, active alerts, proximity to each policy's threshold over its own period | | get agent summary | Health overview of every event stream produced by an agent; per-stream error status if its data can't be fetched | | Tool | Description | |---|---| | get event analytics | Get window comparison analytics 1h/1d/7d/1m vs previous | | detect anomalies | Scan rollup buckets and return statistically anomalous ones | | compare events | Side-by-side statistical comparison of multiple event streams | | Tool | Description | |---|---| | list policies | List monitoring policies, optionally filtered by event | | get policy | Get a single policy | | create policy | Create a new alerting policy | | update policy | Update an existing policy | | Tool | Description | |---|---| | list alerts | List alerts, filterable by status/event, with pagination | | get alert | Get alert details | | get alert deliveries | Get delivery attempts for an alert, filterable by kind and destination | | acknowledge alert | Acknowledge a triggered alert | | resolve alert | Resolve an alert | | archive alert | Archive an alert | | Tool | Description | |---|---| | list destinations | List notification destinations, filterable by channel/enabled state URLs and credentials redacted | | get destination | Get a single destination URLs and credentials redacted | | create destination | Create a notification destination email/webhook/Slack/Telegram/Discord ; secrets may be env:CHIRROP SECRET <NAME references | | update destination | Update a destination, or set enabled: false to retire it | | test destination | Send a test notification and get a test alert id | | URI | Description | |---|---| | chirrop://events | All event definitions | | chirrop://events/summary | Events combined with triggered alert counts | | chirrop://alerts/triggered | Currently triggered alerts | | chirrop://alerts/{status} | Alerts filtered by lifecycle status | | chirrop://destinations | All configured destinations URLs and credentials redacted | | chirrop://events/{event id}/rollups/{period} | Time-bucketed rollup data for an event event id must be a UUID; period is minute, hour or day | | chirrop://events/{event id}/analytics/{period}/{previous} | Window comparison analytics for an event period is 1h, 1d, 7d or 1m; previous is previous window, previous 1d, previous 7d or previous 1m | | chirrop://agents/{agent}/events | All events produced by a specific agent | | Prompt | Description | |---|---| | setup-monitoring | Guided walkthrough: create event, policy, destination, and verify | | triage-alert | Investigate an alert through a structured triage loop | | compare-analytics | Walk through a window comparison with interpretation | | investigate-stream | End-to-end health check, anomaly scan, trend context, and recommendation | | bulk-ingest-review | Review ingest health across all streams and produce a markdown summary | | Symptom | Cause and fix | |---|---| | Every tool returns "CHIRROP API KEY is not set" | The server started without the key. Add it to the server's env block, or export it in the shell you launch your MCP client from, then restart the server. | | Every tool returns "CHIRROP API KEY is invalid: … must start with 'chp '" | The key is malformed, or a ${CHIRROP API KEY} placeholder wasn't expanded because the variable wasn't exported when the client started. Fix the value and restart. | | "Authentication failed … Check that CHIRROP API KEY is valid" | The key has the right format but ChirrOp rejected it revoked, or from another account . | | Environment variable "NAME" cannot be referenced: only variables prefixed CHIRROP SECRET are allowed | Rename the variable to CHIRROP SECRET NAME in the server's environment, restart, and reference env:CHIRROP SECRET NAME . | | Environment variable "CHIRROP SECRET …" … is not set | The variable is referenced but missing from the server's environment. Add it and restart. | | Server shows as disconnected in Claude Code | Run /mcp to see its status and reconnect. Make sure npx or node is on the PATH of the environment Claude Code runs in. | git clone https://github.com/chirrop/chirrop-mcp cd chirrop-mcp npm install npm run build Run the tests: npm test Test with the MCP Inspector: CHIRROP API KEY=chp your key npx @modelcontextprotocol/inspector node dist/index.js MIT