"Agent Dilemma - Concept or Topic Search" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Read your team's hosted journal from an AI agent: every machine's streams, in hub order.
Query your AI agents' traces, errors, cost and alerts in Rius, the agent observability platform.
A record of every action your agent takes for each person: what, for whom, when, with what result.
Agent observability via OpenTelemetry: drift, loop and hijack alerts, e.g. after a prompt injection.
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.
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.
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.
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Now part of GAIP Witness: verifies GAIP receipts; evidence packs and incident bundles.
Exception tracking for .NET. Let your AI coding agent search and triage errors and stack traces.
Agent collaboration and Pulse. Public read-only MCP; local connector for participation.
Production errors your coding agent can read: search, stack traces, context, trends, resolve.
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).
Replay, verify and audit AI agent decisions with signed evidence. Public demo running on the fictional Acme Mutual insurance environment; a full integration is required to use Forge with real systems.
Meter, cap, and block AI agent spend before the provider is charged.
Know when a job stops or a site goes down after the agent exits. Free monitors; paid extra coverage.
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.
Propagation breaker: egress quarantine + fingerprint outbreak telemetry for fleets.
Read-only server insight: why a Linux server or K8s cluster is slow, failing or changed.
Read a tool-call log from an AI agent run and see which calls failed, looped or were slow.
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.
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.
Trace-store secret census of stored agent traces. Verdict $0.01, census $4.99, passes $9.99/$19.99.
Cookieless web analytics your AI agent can read: traffic, spikes and what caused them, funnels.
Is GitHub, npm, Cloudflare or your AI provider down right now? 20 status pages, one call.
Salvageability triage for agent fleets in a declared mass-failure mode.
Free-trial AI fleet spend meter. Quote agent fleet spend from token usage. 100 calls or 14 days. No auth. Official MCP Registry: io.github.mtardy90-sudo/bootlace-ai-spendmap.
Your team's shipping standards, org map and delivery metrics, inside your coding agent.
Read-only Amazon SES observability: search events, inspect bounces, pull delivery stats.
Is an AI tool, agent or MCP server alive, and since when? Checks from the outside, with proof.
AI-agent web fetch, text extraction, API checks and DNS. x402 Base USDC payments per call.
The record of what the agent relied on: a signed, chained receipt per cleared read. Verify by id.
Identify who calls your MCP server or A2A agent: declared identity vs observed behaviour.
Free hosted notary: make any AI agent's actions provable in one call. Verify signed agent logs.
Run AI evaluations, record agent traces and gate releases on evidence, with scoped org access.
Check if a site or service like Stripe is down, and monitor your sites, cron jobs and status pages.
Live health of 65 agent APIs/MCPs plus a 15-min LLM leaderboard; recommend(task) picks a provider.
Live status and 30-day reliability of public MCP servers, from independent hourly probes.