"Pro Tools" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Live vendor incidents in your AI assistant. Hundreds of status pages, one feed. Free active-outage checks with no signup; sign in for history, watchlists, and monitoring tools. Setup: https://www.huntertech.io/vendor-mcp
Hundreds of pay-per-call tools for agents: company records, screening, validation, web reading.
Read-only MCP server for diagnosing any WordPress site — security, performance, forms, logs, downtime — with evidence. The connector exposes no write operations and your AI never sees the site's credentials (secrets are redacted before output). Built for agencies managing many client WordPress sites. Free for 1 site.
Live behavioral security verifier, schema auditor, and trust oracle for A2A, MCP & x402 agents.
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.
Read a tool-call log from an AI agent run and see which calls failed, looped or were slow.
Read-only access to an ET Ducky organization's Windows and Linux agents, alerts, and fleet summary. Four tools list agents, get one agent with its latest health sample, list alerts, and summarize the fleet. Hosted Streamable HTTP endpoint, authenticated with an organization API token sent as a Bearer header.
Witness for MCP calls rejected pre-dispatch: hash-chained ledger, enum differ, signed receipts.
Error-actionability translation for MCP tool failures. $0.002/check.
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.
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.
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.
8,900+ services' status, and your Stackpulse dashboards and URL monitors. Needs Pro.
Operation-level risk guidance for consolidated MCP tools, including schema drift and retry signals.
Four x402 tools: endpoint checks, extraction, evidence verification, domain intelligence.
Search + patterns, maturity assessment, context pricing, redaction checks - a practice as tools.
Agent cost, latency and quality analysis, report delivery and order status. Crypto payments paused.
Vouch — independently measured reliability scores for MCP tools, not self-reported claims.
Public read-only demo of Netmon's network monitoring tools over a recorded snapshot.
Free spend report from an agent log, no key. Hosted proxies: caps, audit export, buy calls.
Monitoring for agencies — uptime, SSL, DNS, blocklists, AI visibility, MCP health. 8 no-auth tools.
Discover Frontier inference capabilities and read sanitized usage through read-only tools.
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"whoami","arguments":{}}} free no key
Diagnose AI workflows for failure, security, and handoff risks — RED/AMBER/GREEN per node.
Live reliability for AI agent tools: is it working right now, and how do I call it correctly?
Observatory operated and funded by devlo: real tools on frozen tasks; intervals, cost, limits.
syslog PRI band, line discarded
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.
ResilienceOracle - 10 operational resilience tools: BIA, RTO/RPO, scenario testing.
