{"slug": "building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested", "title": "Building Observability for MCP Servers: FleetWatch + MCP Blackbox Suggested", "summary": "A developer has open-sourced two tools to add observability to MCP servers: FleetWatch, a monitoring service that tracks uptime, latency, and alerts on failures, and MCP Blackbox, a recording proxy that captures request/response payloads around failures. Both are built with TypeScript, NestJS, and Next.js, and are available on GitHub.", "body_md": "MCP servers are quickly becoming the standard way AI agents reach tools, but the ecosystem is still missing basic infrastructure plumbing: uptime monitoring, latency tracking, and forensic debugging. When an agent run fails, \"the MCP server did something weird\" is usually where the trail goes cold.\n\nI wanted both tools to stay narrow and not overlap with things I'd already built (`mcp-schema-watch`\n\nfor schema drift, `skillcheck`\n\nfor SKILL.md linting, Swarm Trace Viewer for swarm-run analysis). So FleetWatch and MCP Blackbox split the job in half — one watches, one records.\n\nFleetWatch pings your registered MCP servers on a schedule and tracks:\n\nThe moment a server goes down, degrades, or recovers, FleetWatch fires an alert. It's built with TypeScript, NestJS, and Next.js, communicates over WebSockets for live status updates, and ships with a full test suite plus a GitHub Actions CI workflow.\n\n🔗 [https://github.com/DIYA73/fleetwatch](https://github.com/DIYA73/fleetwatch)\n\nFleetWatch tells you *something* broke. MCP Blackbox tells you *why*.\n\nIt's a recording proxy that sits in front of your MCP traffic and captures full request/response payloads. The interesting design decision was around retention: instead of keeping everything (expensive) or nothing (useless when you actually need it), Blackbox permanently pins anything around a failure and prunes the rest. A flight recorder for your MCP servers — the data you need, right when you need it, without the storage bill of logging forever.\n\nSame stack as FleetWatch — TypeScript, NestJS, Next.js, WebSockets — so the two integrate cleanly.\n\n🔗 [https://github.com/DIYA73/mcp-blackbox](https://github.com/DIYA73/mcp-blackbox)\n\nFleetWatch and MCP Blackbox are deliberately separate — you can run either one on its own. But paired together, the workflow is simple: FleetWatch catches the failure in real time, and Blackbox already has the trace waiting for you.\n\nBoth are open source and public on GitHub — issues, stars, and PRs are always welcome. If you're building on MCP and hitting the same \"I have no idea what just happened\" wall, I'd love to hear how you're solving it.", "url": "https://wpnews.pro/news/building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested", "canonical_source": "https://dev.to/diya730/building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested-5c96", "published_at": "2026-07-31 21:13:52+00:00", "updated_at": "2026-07-31 21:42:44.250363+00:00", "lang": "en", "topics": ["developer-tools", "ai-agents", "ai-infrastructure"], "entities": ["FleetWatch", "MCP Blackbox", "GitHub", "TypeScript", "NestJS", "Next.js", "MCP"], "alternates": {"html": "https://wpnews.pro/news/building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested", "markdown": "https://wpnews.pro/news/building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested.md", "text": "https://wpnews.pro/news/building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested.txt", "jsonld": "https://wpnews.pro/news/building-observability-for-mcp-servers-fleetwatch-mcp-blackbox-suggested.jsonld"}}