"Merchant Category Code (MCC) data lookup" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Rudow's mcp server lets your AI assistant — Claude, Cursor, Windsurf, VS Code and others — query your Rudow projects directly: logs, metrics, incidents and semantic search.
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, SSL, domain, and Core Web Vitals monitoring for websites and APIs. List, create, update, and pause monitors; read incident history with AI-generated diagnosis; pull Lighthouse and CrUX page speed data. OAuth 2.0 with dynamic client registration — works out of the box with Claude Desktop connectors. Free plan: 20 monitors, read-only MCP.
Read-only MCP for AI usage profiles, leaderboards, stats, and docs; no writes or private data.
Public MCP digital twin with synthetic systems and an agent firewall. No customer data.
DriftOracle - 15 tools for model/data drift monitoring: PSI, KS-test, alerts, evidence packs.
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.
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
An MCP server giving access to Grafana dashboards, data and more.
Website performance monitoring: scans, Core Web Vitals, RUM data and alerts.
- SquaredUp (EU)OAuth via extensioncom.squaredup
Query and manage SquaredUp dashboards, data streams, the knowledge graph, and KPIs (EU region).
Scout Monitoring data for AI assistants: slow endpoints, traces, N+1 queries, and errors.
Connect AI assistants to AppAmbit — the command center for your mobile & desktop apps. Query real-time analytics, sessions, and crash reports; read and push remote config; send push notifications, provision and query managed per-app SQLite databases, deploy serverless Cloud Code functions; and manage a headless CMS. Also generates SDK setup snippets and runs integration diagnostics. Supports .NET MAUI, Swift, Objective-C, Android and more. Built for indie devs, mobile teams, and agencies.
Brazilian hosting operated end to end by the coding agent: create an app, provision PostgreSQL, Redis and object storage, deploy from GitHub Actions, read container logs, measure memory and CPU, and see the cost in BRL before spending it. Irreversible operations require a human approval code that the agent never sees. Prepaid credit, paid by Pix.
API and website monitoring that validates the JSON a response returns, not just its status code. Create endpoint checks, pull incident reports carrying the actual failed payload, and read health scores from your editor.
High-performance array aggregation and metrics clearing engine. Cleans and bucket-groups noisy metric streams via an $O(N)$ single-pass data sweep. Operates natively with the pay-per-call x402 micropayment framework.
The Polar Signals MCP server enables AI assistants to connect directly with performance profiling data, allowing users to analyze application performance through natural language queries. Key capabilities include querying CPU performance and memory usage, exploring profiling metadata like profile types and labels, and providing AI-driven code optimization suggestions directly within development environments like Claude Code or Cursor.
The Buildkite MCP server exposes Buildkite product data (pipelines, builds, jobs, and test data) to AI tools, editors, and agents through the Model Context Protocol. It provides capabilities including pipeline creation and management, build monitoring with specialized tools like 'wait_for_build', efficient log querying using Apache Parquet conversion and caching, and OAuth-based authentication for both read-write and read-only access to Buildkite's REST API.
Query real user session replay data: tapes, transcripts, error/rage-click filters, alerts.
API monitoring from your editor. Checks the JSON your endpoints return, not just the status code.
