"Git MCP (Model Context Protocol) Server" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
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.
Multi-protocol capability index: lookup, live refresh, pay-preflight, endpoint health.
Rights-aware censorship, China-economic status, and tamper-evident AI evaluation tools.
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
Is this AI/dev API down? Is this model deprecated, what replaces it? Live status for ~40 APIs.
Closed-source remote MCP: model benchmarks, costs, HN signals, tech registry.
AI news, model pricing, service status, and machine-payable premium tools. AFTA-certified.
MCP health (~2k servers) + API status & model deprecations (~40 APIs). One suite for agents.
Real-world Android battery stats from BatterySnap users: device, model and fleet rankings.
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.
Physical-world evidence and operability checks with provenance and explicit data gaps.
Synthetic checks, nightly regression replay and model-drift alerts for AI agents
Check if an AI model is deprecated, retiring, or silently changed price or context window.
Via protocol hop count, value discarded
Live LLM API price + status radar across 11 providers, with public per-model price HISTORY.
Measured readings on open-source dependencies: health, end-of-life, model prices, incidents.
DriftOracle - 15 tools for model/data drift monitoring: PSI, KS-test, alerts, evidence packs.
Nephia is a brand monitoring service, and this is its remote MCP server. Claude, Cursor, ChatGPT or any MCP client can read the mentions your brand gets on 14 sources: X, Reddit (posts and comments), YouTube, TikTok, Bluesky, Hacker News, Mastodon, Lemmy, GitHub, Product Hunt, Stack Overflow, any RSS feed, Vinted, and AI answers from ChatGPT, Gemini and Perplexity. Every mention arrives already read, with its sentiment and intent, so an agent can answer plain questions: which complaints came in since Friday, what Reddit said about us this week. The source is an argument, not a tool, so one call reads every source you watch. Sign-in is OAuth in the browser: no API key to copy. The consent screen has three permissions: read your mentions and Queries, change what is running (pause, resume, retire), and spend credits (semantic search and AI passes), which arrives unticked. Every tool description states its cost, so a model can budget before it spends. The server is on every plan, Free included, and reading your own mentions through it costs nothing.
MCP-native AI SRE. Exposes your production OpenTelemetry problems, traces, and logs over the Model Context Protocol, plus an AI remediation loop that opens a reviewed GitHub fix PR and verifies in production (reopening on regression). Tools include list_problems, get_problem, query_traces, detect_anomalies, and request_problem_remediation. Human-in-the-loop by default — the merge button stays yours.
