"Resources or information on analysis techniques or methods" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Uptime monitoring, status pages and on-call in one place. Create and tune monitors for HTTP, TCP, DNS, ping, TLS certificates, domain expiry, heartbeats and scripted browser logins. Run a check on demand, read uptime and response-time history, acknowledge and resolve incidents, post incident updates, schedule maintenance windows and edit public status pages. Read-only until you grant write access.
Monitor metric streams with control charts and alert only on statistically real drift.
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
Errors, logs and AI-call costs for apps on Node.js, Next.js, Cloudflare Workers or the browser. Ask your AI what’s broken, why, and how to fix it, right inside Cursor or Claude.
Status pages, incidents, maintenance, components and subscribers on Instatus.
Vigilia watches your live app, explains every problem in plain language and writes the fix prompt. Your AI fixes it; Vigilia confirms with real traffic. Vigilia watches web apps that are live with real users, including apps built with Lovable, Bolt, v0, Cursor and Claude Code. It catches errors, failed requests and downtime, explains each problem in plain language, and writes a fix prompt for it. Connect Vigilia to Claude and ask what's broken. Claude lists your open incidents worst first. For each one it reads the plain-language diagnosis, who it affects, the technical evidence (error, page, failing request, stack frames and what the visitor did right before) and Vigilia's fix prompt. In Claude Code or another coding agent, Claude can then fix the cause in your own codebase. Once you've deployed, it marks the incident fixed, and Vigilia watches real traffic to confirm the error stayed away. If it comes back, the incident reopens as a regression. You can also ask how an app is doing (uptime, open incidents, today's traffic), get the exact install snippet for a new project, and check that a live site is running Vigilia. Vigilia never reads or changes your code: the fixing happens in your session, by your AI, in front of you. The only tool that changes anything is marking an incident fixed (the install check just records its result on the app), and you can connect with read-only access. Your data is stored in the EU. Emails, tokens and card numbers are stripped from what visitors' browsers send, and only that scrubbed error context is sent to Anthropic to write the diagnosis. Requires a Vigilia account. The free plan covers one app; reporting backend errors (Supabase, Next.js routes, Workers) is part of Pro.
Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.
AI-native observability and security for engineering teams and coding agents. Search production logs in plain language, investigate issues and root causes, and create or edit live dashboards in your Sazabi workspace. Requires a Sazabi account (OAuth, or a secret key via the X-Sazabi-Secret-Key header).
Replay, verify and audit AI agent decisions with signed evidence. Public demo running on the fictional Acme Mutual insurance environment; a full integration is required to use Forge with real systems.
Game observability for Three.js, Phaser, Babylon.js, PlayCanvas, Unity, Godot, Unreal and GameMaker games. Ask what's wrong with your game and get ranked findings from real players' sessions: frame-time spikes by level, errors with the gameplay just before them, where players die, version comparisons, store reviews and each game's own dashboard. Sign in with your Glitchless account (OAuth); a new workspace can start on a demo game.
Read-only server insight: why a Linux server or K8s cluster is slow, failing or changed.
Read a tool-call log from an AI agent run and see which calls failed, looped or were slow.
Public, read-only MCP for Myndock service discovery and observability. Query aggregate origin HTTP/MCP activity, country and action totals, latency, and acknowledged message deliveries over 1, 24, or 168 hours. Tools: get_service_info, get_statistics, get_support_info. No account or API key required. Discover a separate enrollment-only API for private agent tasks and encrypted exchanges; those actions are not public MCP tools.
Where apps write their log files on Windows, macOS and Linux, as exact copyable paths.
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Guardr keeps watch on the sites you manage. Check any domain from outside and get an A to F health grade for HTTP headers, TLS, DNS and cookies, with fix steps for configuration findings. Three tools: check_site runs a fresh check of one domain, list_sites lists the sites your account watches and get_site returns one watched site in detail. Read-only: Guardr proposes fixes and never changes a site. Needs a Guardr API key; the first site is free.
Free-trial AI fleet spend meter. Quote agent fleet spend from token usage. 100 calls or 14 days. No auth. Official MCP Registry: io.github.mtardy90-sudo/bootlace-ai-spendmap.
Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof.
Offline log parsing, CI failures, HTTP capture analysis and bounded JSON configuration validation.
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
Identify who calls your MCP server or A2A agent: declared identity vs observed behaviour.
Independent verification for agents. Free read-only tools and a signed receipt on every call.
Run AI evaluations, record agent traces and gate releases on evidence, with scoped org access.
Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.
Manage incidents, alerts, monitors, status pages, on-call and telemetry in OneUptime.
Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.
Core Web Vitals (LCP, INP, CLS) per URL from the Chrome UX Report, with daily checks on Pro.
GPU fabric tools: NCCL benchmark analysis, degradation cost, cluster compatibility, XportL facts.
Is Claude, ChatGPT, Gemini, Cursor or Copilot down? Live status from API probes and user reports.
Cost per run, tool, model and day for AI agents, from one call or an OpenTelemetry export.
Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.
Read-only watchtower for AI agents on-chain: decoded receipts, plan vs execution, Safe audits.
Agent cost, latency and quality analysis, report delivery and order status. Crypto payments paused.
Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.
Live status for 172 cloud and SaaS vendors from their official feeds. Is it you, or is it them?
Uptime, API and server monitoring with outages, reporting, on-call and status pages.
Observatory operated and funded by devlo: real tools on frozen tasks; intervals, cost, limits.
The Google GKE MCP server is a managed Model Context Protocol server that provides AI applications with tools to manage Google Kubernetes Engine (GKE) clusters and Kubernetes resources. It exposes a structured, discoverable interface that allows AI agents to interact with GKE and Kubernetes APIs, enabling them to inspect cluster configurations, retrieve Kubernetes resource YAMLs, monitor operations like cluster upgrades, diagnose issues, and optimize costs—all without needing to parse text output or use complex kubectl commands.
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
