Read-only MCP server for support ticket investigation across PostgreSQL, AWS CloudWatch and New Relic
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"opsinsight-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
<div align="center"> <img src="docs/assets/logo-512.png" alt="opsinsight-mcp logo" width="120"> # Investigation MCP Server [](https://github.com/Vignesh-2552/mcp-log-db-investigator/actions/workflows/ci.yml) [](LICENSE)    <h3>A <a href="https://gofastmcp.com">FastMCP</a> server exposing safe, read-only tools for investigating support tickets across PostgreSQL, AWS CloudWatch, and New Relic.</h3> <div class="toc"> <a href="#overview">Overview</a> • <a href="#architecture">Architecture</a> • <a href="#quick-start">Quick Start</a> • <a href="#configure-your-ai-assistant">Configure Your AI Assistant</a> • <a href="#usage-examples">Usage Examples</a> • <a href="#mcp-server-api">MCP Server API</a> • <a href="#security-model">Security Model</a> • <a href="#development">Development</a> </div> </div> ## Overview When a support ticket comes in ("checkout failed for user 4417 around 14:30"), answering it usually means opening a DB client, the AWS Console, and a logging platform, hand-writing a query in each, then manually cross-referencing timestamps and ids across all three. This server turns that into a conversation with an MCP client. Features include: - 🐘 **PostgreSQL** — schema discovery, validated read-only `SELECT` execution, PII-masked sample rows, and catalog-driven identifier/store lookup (no hardcoded table list). - ☁️ **AWS CloudWatch** — log group discovery, Logs Insights queries (cost-capped by bytes scanned), pattern-based log filtering, and metric statistics. - 🟢 **New Relic** — event type and log field discovery (`keyset()`), correlation-id detection, and validated NRQL…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.