"Telegram MCP Server by DLHellMe" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Manage cron/heartbeat checks, read pings and flips, pause/resume/delete on Healthchecks.io.
Read Dead Man's Snitch monitors and status; create, tag, pause and unpause snitches.
Read Airbrake projects, error groups, notices, deploys and stats; mute or unmute error groups.
Check updown.io uptime checks, downtimes, response metrics and status pages, and create checks.
Manage status pages: components, incidents and maintenances; set live component status.
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.
Correlate GitHub releases with Sentry issues and PagerDuty incidents.
Manage Cronitor monitors and send telemetry pings — list, inspect, create, update, delete.
Read monitors, incidents, heartbeats, on-call and status pages; acknowledge or resolve incidents.
Read Spike.sh incidents, on-call, escalations and services; acknowledge, resolve, set priority.
Trace events to function runs to the failing step, and bulk-cancel runs.
Investigate security events and manage the allow/deny lists an analyst acts on.
Review uptime, SSL, pagespeed and heartbeat checks, alerts and maintenance windows; create checks.
Debug background jobs — runs, traces, spans, schedules, queues and deployments.
Read status-page status, services, incidents and metrics; create, update and publish incidents.
Read incidents, services, teams, on-call schedules; acknowledge, resolve and note incidents.
Read AI-gateway analytics, configs, virtual keys, workspaces and users; log request feedback.
Read-only Increase banking observability plus one safe non-money-moving write, for AI agents.
Manage incidents and on-call: list/create/update incidents, who is on call, on-call overrides.
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.
