"Multi-Agent Systems with Shared Memory Storage" 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.
Monitoring that agents set up for themselves — cron jobs, CI/CD pipelines and AI agent runs.
Audit MCP configs and skill files for over-broad scope and injection risk. 6 of 8 free.
The elmah.io MCP server allows AI assistants to interact directly with your error logs, deployments, and organization statistics. Debug production issues faster than ever before.
Website QA for your coding agent: audit SEO, performance, security, accessibility over MCP.
Delivery Assurance: records delivery checks, witnesses results and checks cited quotes.
Watch dependencies, verify facts, inspect coverage, and catch up on changes with durable cursors.
Seller-side analytics for AI-agent discovery, settled revenue, delivery, and repeat use.
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.
Diagnose why an AI agent failed and get the verified fix instantly. Free, no token.
A benchmarked market for AI agents: what runs on your GPU, trust checks, encrypted agent rooms.
Nephia is a brand monitoring service, and this is its remote MCP server. Claude, Cursor, ChatGPT or any MCP client can read the mentions your brand gets on 14 sources: X, Reddit (posts and comments), YouTube, TikTok, Bluesky, Hacker News, Mastodon, Lemmy, GitHub, Product Hunt, Stack Overflow, any RSS feed, Vinted, and AI answers from ChatGPT, Gemini and Perplexity. Every mention arrives already read, with its sentiment and intent, so an agent can answer plain questions: which complaints came in since Friday, what Reddit said about us this week. The source is an argument, not a tool, so one call reads every source you watch. Sign-in is OAuth in the browser: no API key to copy. The consent screen has three permissions: read your mentions and Queries, change what is running (pause, resume, retire), and spend credits (semantic search and AI passes), which arrives unticked. Every tool description states its cost, so a model can budget before it spends. The server is on every plan, Free included, and reading your own mentions through it costs nothing.
Scores a business's online presence 0–100 and names the top issues to fix — search visibility, whether AI assistants can read and recommend it, speed and first impression, trust, and how easy the business is to reach. Give the scan_website tool a URL and it returns the score with the top issues, in chat. English and Arabic. By BottleTech (bottletech.net).
Find your AI agent's likely failure mode, get runtime settings, and clarify ambiguous prompts.
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.
Live-checks whether a WordPress site is ready to be safely operated by AI agents.
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.
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
Monitor public pages with source URLs, timestamps, hashes, text diffs and signed webhooks. One daily monitor is free for 30 days; the $9, 30-day pass adds five monitors at a 15-minute minimum interval, 15,000 checks and change history. No auto-renewal. Public connection supports preflight and offer tools; obtain a key on the website (POST /v1/keys/free for the free tier) and pass api_key to monitor tools. Public text/HTML/JSON/XML up to 3 MB; no browser rendering or login bypass. Hosted commercial service; engine and source remain private.
Evidence-bearing public webpage monitoring with hashes, diffs, signed webhooks, REST, and MCP.
