"GitHub code repository platform" matching MCP connectors:
GET /v1/connectors ā MCP directory API referenceMatching Connector Tools:
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Fixter's MCP provides a stream-lined agentic way to onboard, setup and use the Fixter monitoring and observability platform. Check out more at https://fixter.dev/
Oviond brings data from 100+ marketing platforms into one reporting platform. Through the Oviond MCP server, AI assistants can securely access and work with Oviond clients, projects, reports, dashboards, widgets, and marketing data. Ask questions about your reporting data, analyze marketing performance, and manage reporting workflows directly through your AI assistant.
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
Correlate GitHub releases with Sentry issues and PagerDuty incidents.
Agent payments ecosystem intelligence. Scans GitHub/HN/npm across AP2, ACP, x402, MPP, UCP.
Tracks Claude Code usage-limit resets announced by @ClaudeDevs and Claude Code team members, plus Codex resets from codex-resets.com. Not affiliated with Anthropic. Records announced resets and does not predict the next one. Read-only, no API key. Tools: get_last_reset, list_resets, get_reset_stats.
Deterministic webpage change detection, hashes and text diffs for recurring monitoring via x402 MCP.
Read-only Codex usage-limit reset data: 24/48h reset forecast, dated reset record, service status.
Read-only OpenAI Codex usage-limit reset data from codex-reset.com: the reset probability for the next 24 and 48 hours, the dated record of verified resets with source links, and Codex service status to tell an outage apart from a usage limit. No auth, no API key.
Physical-world evidence and operability checks with provenance and explicit data gaps.
npm releases: Node package versions, daily. $0.01/query. Register in-session ā free testnet funds.
Pre-execution governance for AI agents. Deterministic PASS/FAIL/REVIEW verdicts, replayable proof.
B2A2H platform ā tracks GA4, Vercel deployments, GitHub workflows with AI-powered ROI analytics.
RUM platform for web performance analytics, Core Web Vitals, and third-party script monitoring.
Scores code against a repo's own incident history, rolled into an 8 index Production Reliability Index (PRI). Exposes suggest_code, save_recommendation, and get_scan_report as tools.
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.
MCP-native AI SRE: ask what's broken in production, get a reviewed GitHub fix PR.
Mezmo MCP is a remote Model Context Protocol (MCP) server that lets AI assistants and IDE chat agents interact with the Mezmo observability platform via the Model Context Protocol. Use it for streamlined observability, log analysis, and root-cause analysis in your favorite tools. Add Mezmo MCP and you can: šµļø Run advanced Root-cause analysis over recent logs š¦ List and describe Pipelines š¤ Export and filter Logs with powerful query syntax