Skip to main content
Glama
460,071 tools. Updated 2026-08-17 15:54

"Checking Domain Name Availability" matching MCP tools:

  • Fetch, verify, and render a live host-domain signed VRP stay offer for exact dates and guest count. Verifies Ed25519 JWS against domain JWKS. Call after hemmabo_search_properties returns a host domain, or after verify_vacation_rental_node confirms a domain from outside search, always before quoting final price or a booking link. Read-only: must not lock a quote, create a booking, collect guest details, or start checkout. Route booking only to the signed direct_booking_url; fall back to hemmabo_booking_negotiate/hemmabo_booking_checkout only when this call returns no signed offer, for a configured non-VRP deployment, after explicit user confirmation. The parameters work as a set: pass the same domain, checkIn, checkOut and guests the guest used at search; checkIn must be strictly before checkOut, and the resulting night count — not the dates themselves — drives the signed price and the host capacity check, so changing either date re-prices the offer. Always pass language as the guest's actual conversation language so the rendered widget matches the guest; it never affects the signed price or availability, only formatting.
    Connector
  • Read-only availability and pricing lookup for domain names. No purchase or order is created by this tool; it only returns information. Preferred input: `domains`, 1 to 200 fully-qualified names (e.g. ['acme.com', 'acme.io']); results cover exactly those domains, with no suggestions or expansion. Fallback input: `query`, free text (one or more names, comma- or space-separated); names given without a TLD are expanded to popular TLDs (com/io/ai/co/net). Each result includes whether the domain is available, whether it is a premium name, the registration price and the renewal price. Both prices are totals for one full registration term of that ending, not per-year rates: one year on most endings, but two years on .ai, whose registry mandates a two-year term. Do not divide or multiply a returned price by a number of years. Available non-premium results also carry a `checkout_url` the user can open in a browser to register the domain on justdomain.ai if they choose to. Premium names cannot be registered through Just Domain yet and carry no `checkout_url`.
    Connector
  • Show which countries, frameworks, and legal domains are available. Use this BEFORE calling `search` when the user's topic doesn't name a jurisdiction (e.g., 'what does the law say about consumer protection'); then present the returned jurisdictions to the user or ask which applies. Examples: • 'Which countries do you cover?' → list_coverage() • 'Do you have German law?' → list_coverage(jurisdiction='DE') • 'What jurisdictions for NIS2?' → list_coverage(domain='cybersecurity') • 'Which countries have drone law?' → list_coverage(domain='aviation') (also accepts 'drone' / 'uas') Returns a `jurisdictions` array (each with `code`, `name`, `region`, `laws`, `provisions`, `domains`) plus framework and source listings. NOTE: `laws`/`provisions` are WHOLE-JURISDICTION corpus totals — the response's `count_scope` is `whole_jurisdiction`. Under a `domain` filter the jurisdiction list is narrowed to that domain but the counts are NOT domain-scoped; do not report them as a per-domain count. The domain-specific signal is the (domain-filtered) `sources`/`frameworks`.
    Connector
  • Get the link where the USER buys a domain. This tool does NOT purchase or register anything, and it never will -- no tool here can. project_id is OPTIONAL -- omit it to buy a domain on its own, exactly like the dashboard's domain-search page does; pass it only when the user wants the purchase pre-linked to a specific site (either way the domain connects to a site later via publish_website). Availability is re-verified with an exact registrar check before the link is issued: a taken domain returns byoa_domain_not_available instead of a link, and a successful response includes the live price, renewal_price, and premium flag -- repeat those to the user next to the link (premium first-year prices can be thousands; renewal cliffs are common). If warnings contains availability_unverified, the registrar check was unreachable: pass the link along but tell the user the domain may already be taken. Domain purchases cost real money and require payment and registrant details, so they happen only in the user's own logged-in Orivox dashboard session: give the user the purchase_url and tell them to complete the purchase in their browser. After they buy it, the domain appears in list_domains and can be connected to their site via publish_website(domain_guid=...).
    Connector
  • Search available vacation rental properties by location and travel dates. Use when the user wants to find or browse places to stay. Discovery only — call get_verified_stay_offer with the host domain and same dates before the final answer so the client can render the verified stay offer widget; never quote a final price or booking link from search alone. Do NOT use when the user already has a propertyId or host domain. Returns propertyId, host domain, live availability, host-source pricing, and capacity. Parameters combine as one filter: give at least one of region or country to scope location, plus guests and the checkIn/checkOut range (checkIn strictly before checkOut) — results drop any property below the guest capacity or unavailable for that exact range.
    Connector
  • Check whether ONE specific, fully-spelled domain is available, taken, or a premium listing. Use whenever a user names a specific domain (e.g. "is acme.com available?", "who owns x.io?", "can I get nova.ai?"). For open-ended "suggest names for my idea" requests use search_brandable_domains instead. If the user wants to PURCHASE a domain they already know is an Atom marketplace listing, use get_domain_details or get_domain_purchase_pay_link instead — this tool checks fresh-registration availability, which will misleadingly report an already-listed/owned domain as "taken." Returns: status ("available" = registrable now | "taken" = registered/unavailable | "premium" = for sale on Atom), registrable (bool), price + currency when applicable, estimated_value (rough appraisal, optional), and alternatives[] — when the domain is taken or premium, the closest available premium names from Atom (each with domain, price, url) so the user always has a buyable path. Ends with an Atom url.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Bulk domain checking for AI chats: availability, aftermarket prices, archive.org history, buy links

  • Check if a brand name is free across domains, GitHub, npm and PyPI, and suggest available names.

  • Write to somebody, as you. A username reaches them on this instance and is free; a full email address leaves over SMTP under this instance's domain, so a reply comes back to your inbox, and is charged. Resolve a name with contacts_find first. Mail that leaves needs a mail domain configured — without one use email_send, which sends from this instance's own sending domain and expects no reply
    Connector
  • Search real-time domain availability and prices (via Name.com). Pass a keyword for suggestions, or include ONE full domain name anywhere in the query ("orivox.ai", "www.orivox.ai", even inside a short phrase) to also get that exact domain availability-checked and returned as the FIRST result marked exact:true. Response markers: exact_domain = the exact answer is in the list; exact_check_unavailable = the exact check failed, the list is keyword suggestions only (relay the included note); NEITHER marker = no single domain was recognized (bare keyword, or two+ domains in one query) and NO exact check ran -- if the user asked about specific domains, use check_domain per domain. Returns suggestions as {domain, available, price, premium, renewal_price} sorted purchasable-first (exact match first when present), plus registrar_env ("production" or "sandbox"). ALWAYS mention two pricing traps when recommending: premium=true is an aftermarket domain (first-year price can be thousands, renewal differs), and renewal_price much higher than price is a first-year-discount cliff (e.g. $3.99 year one, $48.99/year after) -- quote both numbers. If the response carries sandbox=true, relay the included caveat to the user in their language and do not present results as real availability. This is a READ: searching never reserves, registers, or charges anything. To buy, call get_domain_purchase_link and hand the user the returned link -- you cannot complete a purchase yourself.
    Connector
  • Authoritative availability check for ONE exact domain (e.g. "is orivox.ai free?") -- use this, not search_domains, when the user names a specific domain. Returns {domain, available, price, renewal_price, premium, registrar_env}. premium=true means aftermarket pricing (quote it explicitly); a renewal_price far above price is a first-year-discount cliff -- always tell the user both numbers. This is a READ: it never reserves, registers, or charges anything.
    Connector
  • Check whether a specific property is available for the requested dates. Use this tool after the user has selected a property from hemmabo_search_properties and wants to confirm availability before getting a quote. Do NOT use for general browsing — use hemmabo_search_properties instead. Read-only: checking availability never places a hold or reserves dates. Returns available=true/false with conflict details and same-month alternative date windows when unavailable. Use the propertyId from search with the exact checkIn/checkOut range; omit guests to check dates only, or pass it to get host-source totals for that party size in the returned alternative windows.
    Connector
  • Update domain settings (auto-renew, WHOIS privacy, registrar lock). Only provided (non-None) fields are updated. Requires: API key with write scope. Args: domain_name: Full domain name (e.g. "example.com") auto_renew: Enable/disable automatic renewal whois_privacy: Enable/disable WHOIS privacy protection locked: Enable/disable registrar lock (prevents unauthorized transfers) Returns: {"success": true, "domain": "example.com", "auto_renew": true, "whois_privacy": true, "locked": true} Errors: NOT_FOUND: Domain not found or not owned by account
    Connector
  • Confirms a publisher controls a domain by checking for a DNS TXT record the owner publishes under `_tunnelmind.{domain}`. A DNS record can only be set by whoever controls the zone, so its presence proves control — a stronger signal than ads.txt, which is just a file anything in the request path can serve. Use this tool when: - You want proof a publisher actually owns the domain it claims. - You are distinguishing publishers who have opted into Sigil verification. Inputs: - `domain` (query, required): Publisher domain. `www.` and scheme stripped. Returns: - `verified`: true (record found), false (absent), or null (DNS lookup failed). - `expected`: the exact TXT record the owner must publish to verify. - `found_records`: TXT values currently present at `_tunnelmind.{domain}`. - `checked_at`: ISO 8601 timestamp of the live DNS lookup. Cost: - Counts as one request against the daily rate limit. Latency: - Typical: <300ms (one DNS-over-HTTPS lookup).
    Connector
  • Search OTTASIA's catalog for movies or TV shows by name. Returns multiple candidates with year, type, brief overview, and country-aware OTTASIA link. Use this when a user asks 'find me X' or when a query is ambiguous (e.g. 'joker', 'the office') and you need to clarify which title they meant before checking availability. Use where_to_watch instead when the user has already named a specific title and country and just wants the streaming providers.
    Connector
  • Add policy/reference text to a domain's knowledge base. The text is chunked and embedded; explanations for future decisions in this domain will cite it. Creating a new domain claims it for your account (plan limits apply). The built-in demo domains are read-only — ingest into your own domain instead. On team plans, only the domain admin (the member who created the domain, or the subscription owner) can add documents. Args: domain: Domain to ingest into (existing or new). text: The policy or reference text. source: Optional source name shown in the document list.
    Connector
  • Verify that a vacation-rental host domain is a valid Vacation Rental Protocol (VRP) node before trusting it. Reads the domain's .well-known/vacation-rental.json and JWKS. Read-only trust check: no availability, pricing, booking, or payment — do NOT use it to answer those questions. Use when a host domain arrives from outside search (user-typed or third-party); domains returned by hemmabo_search_properties can go straight to get_verified_stay_offer. On success, call get_verified_stay_offer with the same domain and stay dates. The single input is the host domain as a bare hostname (no scheme or path); verification reads that domain's own .well-known and JWKS, so the result is only as trustworthy as the exact domain you pass.
    Connector
  • Search the talent graph. Returns ANONYMOUS match cards — headline, skills (with skills_matched showing which of YOUR terms hit), seniority, location, availability, salary range, and a short snippet — but NO name, full resume, or contact. Call get_candidate (a metered reveal) for the deeper anonymous profile. Filter by skills, location, seniority, salary, experience, availability, and more; sort by recency (default) or skill_match. Always paginated (max 25 per page).
    Connector
  • <tool_description> Get detailed product information by ID from the Nexbid marketplace. Returns full product details including price, availability, description, and purchase link. </tool_description> <when_to_use> When you have a specific product UUID from a previous nexbid_search result. Do NOT use for browsing — use nexbid_search instead. </when_to_use> <combination_hints> Typically called after nexbid_search to get full details on a specific product. If user wants to buy → follow with nexbid_purchase. </combination_hints> <output_format> Full product details: name, description, price, currency, availability, brand, category, purchase link. </output_format>
    Connector
  • Place a backorder on a domain that is currently registered to someone else. We watch it and automatically register it for the user when it becomes available (drops) - availability is polled every few minutes. The user is charged only if the catch succeeds - no upfront fee. Requires a card on file or payment_method 'balance'. Confirm the domain with the user first. Best-effort: a contested drop may be taken by a specialized drop-catcher first.
    Connector
  • List all DNS records for a domain. Returns DNS records at the domain level (independent of site-level manage_dns). Use this for domains that may not be linked to a site. Requires: API key with read scope. Args: domain_name: Full domain name (e.g. "example.com") Returns: [{"id": "record-id", "type": "A", "subdomain": "www", "value": "1.2.3.4", "ttl": 3600}] Errors: NOT_FOUND: Domain not found or not owned by account
    Connector
  • Check if a domain is available for purchase and get its price. Always call this before buying. After showing the price, ask the user two things before proceeding: 1. Confirm they want to purchase at that price. 2. Which payment method they prefer: - "card" / "Stripe" → call buy_domain (opens Stripe checkout in browser) - "crypto" / "USDC" / "x402" → call buy_domain_crypto (autonomous USDC payment, no browser; requires Coinbase Payments MCP or another x402 wallet) - "MPP" / "agent pay" → call buy_domain_mpp (Stripe agent payments via Shared Payment Token, no browser) If the user has Coinbase Payments MCP configured in their session, suggest crypto as the default. Otherwise default to buy_domain (Stripe). Args: domain: The full domain name to check (e.g. "coolstartup.com"). Returns: Dict with availability status, price in cents, and formatted price.
    Connector