"Methods for performing web search without using an API" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Self-hostable uptime monitoring: create checks, read incidents, manage status pages.
Read-only web analytics from Pulse: your sites, totals, trends, breakdowns and realtime visitors.
Uptime monitoring, status pages and on-call in one place. Create and tune monitors for HTTP, TCP, DNS, ping, TLS certificates, domain expiry, heartbeats and scripted browser logins. Run a check on demand, read uptime and response-time history, acknowledge and resolve incidents, post incident updates, schedule maintenance windows and edit public status pages. Read-only until you grant write access.
Lets AI agents analyze API metrics, request logs, and traces, and manage apps and alerts.
Hundreds of pay-per-call tools for agents: company records, screening, validation, web reading.
Production errors your coding agent can read: search, stack traces, releases, resolve, setup.
A record of every action your agent takes for each person: what, for whom, when, with what result.
Live health leaderboard of x402 paid endpoints, plus an MCP server readiness check
Pingstack monitors cron jobs and scheduled tasks with heartbeat checks, and checks websites, TCP ports, DNS records, SSL certificates and domain expiry. This MCP server lets your agent create, update, pause and delete checks, build dashboards and publish them as status pages, manage notification groups, and read incidents with their causes, uptime, run history and latency. Pause, delete and unpublish stay off until you turn them on. Browser sign-in, no API key needed.
Document operations audit, delivered per API call as an atom service on Conduit Atoms.
Errors, logs and AI-call costs for apps on Node.js, Next.js, Cloudflare Workers or the browser. Ask your AI what’s broken, why, and how to fix it, right inside Cursor or Claude.
Connect AI assistants to PingRelay to monitor websites and APIs, investigate incidents, retrieve uptime and response-time metrics, manage maintenance windows, and access status pages through the Model Context Protocol. Access: Requires a PingRelay paid plan with MCP access and an authorized API key.
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.
Search your mobile, web and server app logs session by session, and read grouped errors, daily stats, releases and alerts.
Let AI agents list, read and resolve Bugsly error-tracking issues and check monitors.
Project context, backlog tasks, and controlled workflows for coding agents. OAuth sign-in.
Uptime monitoring: monitors, incidents, alerts, maintenance, on-call, status pages and telemetry.
Exception tracking for .NET. Let your AI coding agent search and triage errors and stack traces.
Hear it from nimo, not your customers. Monitoring that tells you the fix, not just the alert: uptime, Core Web Vitals, cron check-ins, plus Journey Watch for your signup and checkout flows. Free one-off checks, no account needed.
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
AI-native observability and security for engineering teams and coding agents. Search production logs in plain language, investigate issues and root causes, and create or edit live dashboards in your Sazabi workspace. Requires a Sazabi account (OAuth, or a secret key via the X-Sazabi-Secret-Key header).
Agent collaboration and Pulse. Public read-only MCP; local connector for participation.
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.
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.
Read-only outage intelligence: live service status, report history, geography and spikes
Read-only server insight: why a Linux server or K8s cluster is slow, failing or changed.
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.
Signed, append-only receipts of an AI agent's decisions and outcomes, with public proof links.
Propagation breaker: egress quarantine + fingerprint outbreak telemetry for fleets.
Read a tool-call log from an AI agent run and see which calls failed, looped or were slow.
Read your Condux issues, events and stack traces (deminified with source maps). Triage optional.
Bounded authorization and independently verifiable execution evidence for agents.
Manage Cronitor monitors, issues, status pages, and metrics for jobs, uptime, and sites.
Understand who uses your MCP servers, what they’re trying to accomplish, and where workflows get stuck. Analyze tool adoption, user journeys, reported outcomes, and business signals directly from your AI assistant, with evidence from individual sessions.
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.
Where apps write their log files on Windows, macOS and Linux, as exact copyable paths.
Fork-replay one recorded span from a failed agent run and get an attribution verdict.
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.
Warm CDN and reverse-proxy caches: manage sites, run warms, read cache-hit stats.
Cookieless web analytics your AI agent can read: traffic, spikes and what caused them, funnels.
Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Witness for MCP calls rejected pre-dispatch: hash-chained ledger, enum differ, signed receipts.
Scan/purge hidden text & score web domains: TLS, DNS, headers, speed. Free scans, $0.01 actions.
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.
Error-actionability translation for MCP tool failures. $0.002/check.
Status pages and uptime monitoring: read status, monitors, incidents and error budgets, and with a write key create monitors, open incidents, post updates, schedule maintenance and record deploys.
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.
Salvageability triage for agent fleets in a declared mass-failure mode.
Website traffic, human vs bot split, realtime visitors, breakdowns and site health for your DevDome sites. Hosted remote MCP server (streamable HTTP), authenticated with a DevDome API key.
Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.
Read AFMR failure modes and discover scoped attestation and lift-evidence contracts.
Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof.
EU AI Act Art. 50 URL & C2PA checks, Art. 12/14 snippets, HMAC receipts, DPO questionnaire answers.
Measured latency, time to first token and uptime for ~45 AI inference APIs, by region.
MCP server for 0001SENSATIONS: 107-level textual descent; only leave_trace writes (public, append)
X-Forwarded-For comma count, value discarded
AI-agent web fetch, text extraction, API checks and DNS. x402 Base USDC payments per call.
Transparent public utilities for agents. Requests are counted without storing identifiers.