"Transcribing Voice Conversations into Structured Meeting Notes" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Your agent needs to know what a site is built on and who owns it — or to find every site running a given technology. **What you can ask for** • "What is this site built on — CMS, analytics, payments, CDN?" • "Find every domain running Shopify in Germany." • "Who owns this domain, and when does it expire?" • "How many sites use this technology, and is that growing?" • "Find domains whose HTML contains this snippet." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-domains/mcp and sign in with OAuth — there is no key to create or paste. 12 tools: technology detection for one domain, domains by technology, domains by HTML term, technology stats and aggregations, plus whois overview and its filters. **Why this rather than the source** Prospecting by tech stack and ownership lookup in the same call shape. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the stack here, then ask the same agent for that company's traffic and the people to contact — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/sales/mcp turns a technology list into a contactable pipeline. https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Search and retrieve reviewed proxy documentation, generate tested configuration examples, and diagnose structured proxy errors. No API key is required.
Fibre optics, OTDR, network design and data centre notes from SPLIDIA, plus its service catalogue.
Live demo of Frisian-MCP, a Django/DRF package that exposes ViewSets as MCP tools through grouped dispatchers — ~1,800 endpoints collapsed into ~16 tools, with DRF permission classes enforced in-process before ORM access. Connect to try the dispatcher pattern against a realistic network-automation surface.