"Information about theHarvester tool" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Ask your AI about your product's events, delivery health and usage
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.
Trust layer for AI agents. Privi Guard checks web pages, emails and tool results for prompt injection and outgoing text for leaked API keys and card numbers, with signed on-chain receipts (1,000 free checks a month). Privi Scan grades any MCP server for tool poisoning and rug pulls. Plus tamper-evident audit logs, agent passports, spending mandates and a live kill switch.
Read a tool-call log from an AI agent run and see which calls failed, looped or were slow.
Combined Server-Surface Census: identity, tool contract + skill digests in one signed snapshot.
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.
Error-actionability translation for MCP tool failures. $0.002/check.
Cost per run, tool, model and day for AI agents, from one call or an OpenTelemetry export.
Observed facts on public MCP servers: protocol checks, tool changes, signed evidence. No verdicts.
Track cost, latency, and usage of every MCP tool call from any client (Claude, Cursor, Windsurf). Free 25K calls/month — open-source proxy, EU-hosted.
Free spend report from an agent log, no key. Hosted proxies: caps, audit export, buy calls.
EU-hosted website monitoring + 17-framework compliance MCP. One anonymous tool, four authenticated.
MCP tool observatory: do registry servers answer, and are their answers true? No key.
Zero-trust gateway for AI agents: score tool calls, verify agent cards, enforce policy, audit.
DORA OS EventFabric - 14-tool event stream for DORA compliance signals and pub/sub fabric.
DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.
Analytics for MCP servers. Query your tool calls, first-call success, retries and schema cost.
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.
Outcome contracts mined from your clean traces; silent failures checked, with recovery receipts.
Every AI tool call runs as the person who asked, under your rules, fully audited.
Hash-chained HMAC-signed audit log MCP for A2A (agent-to-agent) calls. Every tool-call, agent-ha...
MCP for retrieving information about recorded session replays.
The Cortex MCP server provides read-only access to real-time engineering context from the Cortex developer portal, allowing AI coding assistants to answer natural language questions about your organization's catalog (microservices, libraries, domains, teams, infrastructure), scorecards (engineering standards and best practices), initiatives (goals and deadlines), and Engineering Intelligence metrics. It includes tools for querying documentation, tracking personal entities, and accessing AI-assisted insights across the entire Cortex ecosystem.
Ask your agent about your MCP servers: failing tools, releases, clients, sessions.
Ask about Vercel Web Analytics and Speed Insights across all your projects and boards.
Research honeypot. Logs connections and tool arguments; injects instructions. Read README first.
One OAuth connector for your team's remote MCP servers, with Tool Packs, guardrails and logs.
PII scanning and redaction receipts for LLM traces and tool payloads.
