MCP.Market

AgentWatch MCP server

by nicofains1·io.github.nicofains1/agentwatch·v0.3.1

Multi-agent observability: cascade failure detection, heartbeats, and forensic replay

B82/100grade B
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

0 stars77 downloads/wk

Reviews

Write one

Nobody has reviewed AgentWatch yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

AgentWatch tools (13, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • agentwatch_alert

    Record an alert with automatic deduplication and severity escalation

  • agentwatch_cascade

    Find the root cause chain for a failure event - walks parent links to find where the cascade started

  • agentwatch_create_trace_idwrite action

    Generate a new trace UUID for grouping related events

  • agentwatch_dashboard

    Fleet health overview - shows all agents, their status, uptime, and active alert counts

  • agentwatch_dashboard_text

    Fleet health overview as a formatted ASCII table

  • agentwatch_fleet_health

    Get health status of all agents with uptime percentages

  • agentwatch_get_alerts

    List active (unresolved) alerts, optionally filtered by agent

  • agentwatch_get_failures

    List recent trace failures, optionally filtered by agent

  • agentwatch_get_trace

    Get all events in a trace by trace ID

  • agentwatch_replay

    Replay all cascade chains in a trace - finds every failure and correlates each

  • agentwatch_report_heartbeat

    Report a heartbeat for an agent. Call this periodically to track agent health.

  • agentwatch_resolve_alert

    Mark an alert as resolved

  • agentwatch_trace

    Record a trace event for cross-agent action tracking

Public scan report

scanner v0.1.10 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan21 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 164 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How AgentWatch compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 65% of 4,460 AI and agents servers
Tools
13
the typical AI and agents server has 6
Tools that change things
8%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
77
more than 57% of 1,538 AI and agents servers with a package

What its tools let an agent do: 12 read · 1 change

Install AgentWatch in Claude Code, Cursor or VS Code

Runs npx -y @nicofains1/agentwatch on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add agentwatch -- npx -y @nicofains1/agentwatch
Add to Cursor

What the publisher says

From the AgentWatch repository's README, as published. We do not edit it. Read it on GitHub

agentwatch

Your agent swarm crashed at 2am. You have logs from 10 agents and no idea which one started the cascade. AgentWatch tells you.

It tracks heartbeats, links actions across agents, walks backward from any failure to the root cause, and replays the full sequence. Works with any agent framework (CrewAI, AutoGen, LangGraph, PocketFlow, custom). Stores everything in a local SQLite file.

Early stage. Issues and feedback welcome: https://github.com/nicofains1/agentwatch/issues

See it in action

No install needed:

npx @nicofains1/agentwatch demo

This seeds a 5-agent fleet, triggers a cascade failure, and shows you the full trace:

AgentWatch Fleet Dashboard
============================================================
Agents: 5 total | 3 healthy | 1 degraded | 1 error | 0 offline

Cascade Failure (4 steps, root cause: scheduler/dispatch-batch)
============================================================
[ROOT] scheduler/dispatch-batch [ok] 15ms
       {"assigned_to": "fetcher"}
       |
[  1 ] fetcher/call-api [error] 30000ms
       TIMEOUT after 30000ms
       |
[  2 ] processor/transform [error] 120ms
       Error: input is null - expected array from fetcher
       |
[FAIL] notifier/send-alert [error] 8ms
       Error: no processed data to report

Install

npm install @nicofains1/agentwatch

Requires Node 18+. Uses better-sqlite3 (native bindings, no external database needed).

Quick start

import { AgentWatch } from '@nicofains1/agentwatch';

const aw = new AgentWatch(); // creates agentwatch.db in the current directory

// Report heartbeats from your agents
aw.report('agent-a', 'healthy');
aw.report('agent-b', 'healthy');

// Trace an action in agent-a
const traceId = aw.createTraceId();
const e1 = aw.trace(traceId, 'agent-a', 'fetch-data',
  'url=https://api.example.com', 'rows=150');

// Trace a dependent action in agent-b that fails
const e2 = aw.trace(traceId, 'agent-b', 'process',
  JSON.stringify({ rows: 150 }), 'Error: out of memory', {
    parentEventId: e1.id,
    status: 'error',
    durationMs: 4200,
  });

// Walk back to the root cause
const chain = aw.correlate(e2.id);
console.log(chain?.root_cause);
// -> { agent: 'agent-a', action: 'fetch-data', ... }

// Print fleet status
console.log(aw.dashboardText());

What it does

Heartbeats - Each agent calls aw.report(name, status) on a schedule. AgentWatch tracks health over time and marks agents as stale or offline based on configurable thresholds.

Cross-agent tracing - Actions are linked by trace ID and optional parent event ID. When agent-c fails because agent-b sent bad data that came from agent-a, the full chain is queryable.

Cascade detection - correlate(failureEventId) walks backward from any failure to the root cause, returning the full chain with timing and output at each step.

Alert de-duplication - The same alert type from the same agent within a time window collapses into one entry with an incrementing count. Severity auto-escalates: info (1x) -> warning (3x) -> critical (10x).

Forensic replay - replay(traceId) returns all cascade chains within a trace. Useful for post-mortem analysis when a single trace touched multiple agents.

OpenTelemetry export - Export traces as OTEL spans (GenAI semantic conventions). Works with Jaeger, Grafana, or any OTEL-compatible backend. Requires optional peer deps.

CLI

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

AgentWatch: common questions

Is AgentWatch MCP server safe?
Mostly: it is graded B (82/100). Read the AgentWatch safety report
How do I install AgentWatch?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does AgentWatch need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is AgentWatch maintained?
The last commit was 202 days ago (2026-04-16). The latest release is v0.3.1.
What can I use instead of AgentWatch?
Servers from other publishers that do the same job: PaperBanana MCP server, Mockserver MCP server and Orcareplay MCP server.
How does AgentWatch compare with other AI and agents MCP servers?
safety score 82/100 (higher than 65% of 4,460 AI and agents servers); tools 13 (the typical AI and agents server has 6); tools that change things 8% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to AgentWatch

Same job from other publishers: the closest match first, then the best rated.

  • PaperBanana
    Generate academic diagrams and statistical plots from text using multi-agent AI.
    A
  • Mockserver
    Mock, record/replay, verify and chaos-test any HTTP, REST, gRPC or LLM dependency over MCP.
    A
  • Orcareplay
    Read, replay and fork recorded coding-agent runs.
    A
  • three.ws Brain
    List LLM providers and run chat completions through the three.ws multi-provider router.
    B
  • Shellward
    AI agent security: 7 MCP tools for injection detection, PII scanning, command safety, DLP.
    A

More from nicofains1 →