"How to integrate with Azure DevOps" 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.
Domain security reconnaissance tools for AI agents via Model Context Protocol. 13 security tools — DNS, SSL, HTTP headers, email auth, port scan, propagation, reverse DNS, ASN/BGP, RDAP/WHOIS, subnet calc, and comprehensive security scan — callable from Claude Desktop and any MCP-compatible AI agent. Part of DechoNet. Every tool here is also a free web tool at dechonet.com — no sign-up, no API key — backed by error-fix guides. This package brings the same checks to AI agents.
Live DNS lookups for agents: A/MX/TXT/SPF/CNAME/PTR with TTLs and DNSSEC, via Google Public DNS.
Control Plane (controlplane.com): deploy and operate workloads across AWS, GCP, Azure, and more.
Vendor status pages, TLS cert inspection, DNS propagation checks, and incident-response playbooks.
DNS and email security scanner with 80 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand audits.
Claim a working subdomain in one call — A, CNAME and TXT records. No domain to buy, no account.
Register, renew, transfer, and manage domains, DNS, VPS, and email with 102 tools. By OSIR.
Proxy guides, tested configurations and error diagnostics, with an optional local route check.
23 x402 agent utilities with free routing and an AveDaris machine Discovery Beacon.
Stateful WebSocket session registry with per-connection Shannon entropy delta tracking for schema di
Domain availability across 1,200+ TLDs, with renewal price, minimum term and eligibility
Domain attribution and correlation for AI agents, with confidence and per-signal evidence.
Validate whether an IP address belongs to Bingbot. Remote MCP server exposing a validate_ip tool.
Validate whether an IP address belongs to Applebot. Remote MCP server exposing a validate_ip tool.
Validate whether an IP address belongs to YandexBot. Remote MCP server exposing a validate_ip tool.
Validate whether an IP address belongs to Googlebot. Remote MCP server exposing a validate_ip tool.
Unlock the power of DNS lookups with our DNS Lookup service using Google DNS-over-HTTPS. Whether
Domain registration for AI agents via Stripe or x402 crypto with Cloudflare DNS.
The internet's largest queryable infrastructure graph — 7.39 billion nodes, 39 billion edges, 5.6 million threat-intelligence relationships. Pivot from any IP, domain, or ASN across DNS, BGP, WHOIS, GeoIP, and threat intel in a single Cypher query. Most threat-intel and OSINT APIs are point lookups: you ask about one indicator, you get one record. Investigations don't work that way — you start from one suspicious domain and need to trace its hosting, its sibling domains, its registrar, its email
