MCP documentation menu

Tool reference

Your AI assistant chooses and calls these tools for you. You don’t call them yourself, but knowing what exists helps you ask for the right thing. Each page shows the description the server gives your assistant, the parameters it accepts, and the OAuth scope it needs.

Other

datapulse_agbRetrieve chapters from the ICANN 2026 Round Applicant Guidebook (AGB).no scope
datapulse_agb_searchFind the passages of the ICANN 2026 Round Applicant Guidebook (AGB V2-2026.04.24) that answer a question, by meaning.no scope
datapulse_disputedb_lookupLooks up UDRP decisions by exactly ONE of case_number (one decision in full), domain (disputes brought AGAINST that domain; exact match, a …datapulse:dns
datapulse_disputedb_searchSemantic search over UDRP case law and reference documents: ~118,000 WIPO and Forum decisions (1999 to date) in ~947K chunks, the WIPO …datapulse:dns
datapulse_disputedb_statsOutcome counts and the complainant win rate for the whole UDRP corpus (~118,000 WIPO and Forum decisions, 1999 to date), overall, per …datapulse:dns
datapulse_dns_dphistoryHosting and nameserver history for a name from the DataPulse names corpus: the dated versions of its web-hosting ASN (AW), mail exchangers …datapulse:dns
datapulse_dns_dptechsimFind domains whose DNS infrastructure is similar to a seed domain’s, by vector similarity over nameservers, MX, hosting ASNs, TLD, registrar …datapulse:dns
datapulse_dns_neighborhoodLooks up the DNS infrastructure cluster (HDBSCAN over the similarity embedding) a domain belongs to, or a cluster by ID. Every indexed …datapulse:dns
datapulse_dns_rdap_historyThe RDAP observations DataPulse has taken of a domain over time: registrar (ianaid), abuse contacts, EPP status, nameservers and …datapulse:dns
datapulse_dns_regclustersFind registrars that registered many domains on one UTC day, from the corpus’s RDAP registration records: bulk campaigns, parking inventory, …datapulse:dns
datapulse_dns_registrarLooks up a registrar in the IANA registrar list by IANA ID, or searches registrar names. Registrars sell and manage registrations; this does …datapulse:dns
datapulse_dns_searchlabelsSearch the corpus for registrable (PSL+1) labels like a search term, with every TLD where each label is listed: the starting point for …datapulse:dns
datapulse_domain_overviewDomain research in one call: the root URL’s web scrape, a live DNS lookup and RDAP registration data, combined. The starting point for …datapulse:scrape
datapulse_gtld_applicationsLooks up applications in the ICANN 2026 Round of new gTLDs in ICANN’s public application listing (published at Reveal Day, 7 October 2026; …no scope
datapulse_helpRetrieve DataPulse documentation: the reference for each tool family, the conventions every tool shares (name canonicalization, hashes, …no scope
datapulse_idn_variantsGenerate the IDN variant set of a label under the ICANN Root Zone Label Generation Rules (RZ-LGR 6), the rules that decide which variants of …no scope
datapulse_live_dnsLive DNS lookup of one name, synchronous, through a DNSSEC-validating resolver that drops answers in private, link-local and unique-local …datapulse:dns
datapulse_live_dns_bulkSubmit up to 150 DNS lookups per request. Asynchronous: the answer is a receipt, not records.datapulse:dns
datapulse_live_domain_healthLive domain health probe: one call checks a domain’s DNS, DNSSEC, delegation, nameservers, web (TCP 80/443, TLS chain, HTTP, QUIC), mail …datapulse:dns
datapulse_live_rdapLive RDAP registration lookup of one domain or IP address (v4 or v6), synchronous.datapulse:dns
datapulse_live_rdap_bulkSubmit up to 150 RDAP lookups per request, domains and IP addresses mixed. Asynchronous: the answer is a receipt, not registration data.datapulse:dns
datapulse_scrape_bulkSubmit up to 250 URLs for scraping per request. Asynchronous: the answer is a receipt, not scrape results.datapulse:scrape
datapulse_scrape_bulk_resultsReads up to 250 stored scrapes by url_hash in one call, such as every sent[].url_hash of a datapulse_scrape_bulk receipt.datapulse:scrape
datapulse_scrape_resultReads one stored scrape by url_hash: poll an asynchronous submission, or fetch the page’s DOM or full links array. A bulk submission’s …datapulse:scrape
datapulse_scrape_submitScrape one URL: render it in a headless browser and extract entity data with an LLM.datapulse:scrape