"Understanding File Reading in Programming" matching MCP connectors:
GET /v1/connectors – MCP directory API referenceMatching Connector Tools:
Secure P2P File Transfer, Encrypted Chat & Communication | Decentralized P2P & AES-256-GCM encryption | Zero cloud logs. Zero registration. For humans and autonomous AI agents / MCP servers.
An MCP server that allows an agent to find the vendor that a network interface MAC address is registered under and other information about the block like it's registered country, the registry type it is in, how many addresses are in it's block and a link with more information. Stateless MCP 2026-07-28 version support only.
Find the organization behind a MAC address or OUI prefix in the IEEE registries. No auth, no key.
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.
Free anonymous website, DNS, email and TLS checks, plus monitor read and opt-in write access.
Use when email lands in spam: audits SPF, DKIM, DMARC, MX and returns the DNS records to fix it.
Normalized JSON for any domain across 1,200+ TLDs, reading WHOIS where no RDAP server exists.
Claim a working subdomain in one call — A, CNAME and TXT records. No domain to buy, no account.
Outside-in DNS, email security, SEO, GEO and app-link checks plus developer utilities.
Complete domain email-auth audit in one call: SPF with RFC 7208 lookup counting, DKIM selector pr...
Buy and manage residential, mobile and datacenter proxies in 170+ countries, prepaid per GB
Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.
hosts file token count, line discarded
Manage your Webshare proxies, usage, plans and billing. Sign in with OAuth, no API key.
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
Site crawl + tech stack + DNS + SSL + WHOIS — five web-intel layers in one MCP.
Registration date, expiry, domain age, registrar and nameservers for every domain in an Apify...
DomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record.
DomainDNA: a domain's tech stack, email security (MX/SPF/DMARC), TLS expiry and age in one record.
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.
