Skip to content

Atom.com — Premium Domains MCP server

com.atom/premium-domainsatom.comstreamable-httpv2.0.7Scanned

Search, appraise, trademark-check, and buy premium brandable domain names from Atom.com.

25 tools: 5 can delete or cancel things, 8 change things and 12 only read.

Tools: 5 delete, 0 irreversible, 8 write, 12 read.
  • Reads private data · 0
  • Reads text others write · 13
  • Can send data out · 1
  • 7 findings, 1 high

Tools listed without sign-in. Remote posture

With Anlyon

5 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Atom.com — Premium Domains MCP server can do

The Atom.com — Premium Domains MCP server is published by atom.com, a domain the MCP Registry verified. It has 25 tools. It can delete or cancel things (5 tools: register_domain, purchase_domain, register_domain_spt, buy_ai_tokens and 1 more) and create or change data (8 tools: brainstorm_names, check_domain_availability, generate_domain_names, appraise_domain and 4 more). 12 tools only read.

13 tools bring in text other people can write (get_checkout_link, register_domain, purchase_domain and 10 more); 1 tool can send data out of your system (create_registrant_contact).

The fixed checks matched 7 findings, 1 of them high severity (long-description, annotation-conflict and model-directed-text). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 2.0.7.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

25 tools

Deletes or cancels 5Claude Code: deny
  • buy_ai_tokensPurchase AI Tokens ($0.10 per token) by charging a Stripe Shared Payment Token (SPT) — for users with no Atom balance.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "purchase": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • High

      The description contains "do not tell the user", an instruction to keep something from the user.

      Matched text

      description: "...ically — the result says so explicitly; do not tell the user a refund is coming."

      What this check looks for
    Description, as the server wrote it
    Purchase AI Tokens ($0.10 per token) by charging a Stripe Shared Payment Token (SPT) — for users with no Atom balance. This SPENDS REAL MONEY and requires the 'domains:register' scope. MANDATORY three-step flow — never skip a step: 1) Call with confirm=false to get a QUOTE: price is entirely server-authoritative ($0.10 x token_count) — never assume or pass a price. 2) Call again with confirm=true, the SAME idempotency_key, and NO payment_token: returns a structured payment_required challenge (amount, currency). 3) Once a Shared Payment Token is obtained for that exact amount, call a third time with confirm=true, the SAME idempotency_key, and payment_token set. Payment is captured FIRST; tokens are only credited after that succeeds. PAYMENT PRIORITY for AI Tokens: this tool is priority 1 — try it first, using whatever payment method your own platform can already supply for the payment_token. Only if you have no way to obtain a payment_token here, fall back to priority 2: get_ai_tokens_pay_link, paid via link-cli's tools (e.g. mpp_pay), if those are present in this session. There is no checkout-link fallback for AI Tokens. Rules: never assume or pass a price. Reuse one idempotency_key across all calls for the same intent. If crediting fails AFTER payment succeeds, no refund is issued automatically — the result says so explicitly; do not tell the user a refund is coming.

    Annotations the server declares

    • title: Buy AI Tokens via Stripe SPT
    • destructiveHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • create_websiteBuild a real website, with a logo, for a business on a domain in the user's Atom account, and optionally put it live.Reads text others writeNo findings

    Why it is in this group

    • The name "create_website" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Build a real website, with a logo, for a business on a domain in the user's Atom account, and optionally put it live. Use when the user wants to launch a website, including right after registering a domain. MANDATORY flow: 1) BEFORE any payment, call with confirm=false and the description (no domain needed). This costs nothing. It refuses sites Atom won't build (error content_not_allowed: tell the user the message and do NOT register a domain for it) and returns questions[] for details still missing, such as address and opening hours for a business people visit. 2) Ask the user those questions ONCE, in one message, together with any registrant contact details the registration needs. If they skip something, carry on: that section is left out. Never invent answers. 3) Register the domain and wait until it completes (for USDC: get_coinbase_payment_status reports completed). 4) Call with confirm=true, the domain, business_name exactly as the user wrote it (domains lose their capitals and spaces, and this is the text on the logo), and answers{} keyed by the question ids. Set publish=true only if the user asked for the site to go live; otherwise it stays a private preview. 5) Keep calling get_website_status until stop_polling is true, then give the user the live_url or preview_url, the edit_url, and show the logo_url. If this reports error 'listed_for_sale', ask the user, because going live removes the listing; if they agree, retry with confirm_delist=true. Only the owner can open preview_url. Do not describe the logo as unique or safe to trademark: screen_trademark_conflicts checks a name, not artwork.

    Annotations the server declares

    • title: Create website
    • destructiveHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • purchase_domainPurchase an ALREADY-LISTED Atom marketplace domain.Reads text others write1 finding

    Why it is in this group

    • The name "purchase_domain" says "purchase": a word that usually means money moves, which cannot be taken back.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,293 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...t with those, then retry with confirm=true — this is expected and not a dead end."

      What this check looks for
    Description, as the server wrote it
    Purchase an ALREADY-LISTED Atom marketplace domain. This SPENDS REAL MONEY and requires the 'domains:register' scope. Use this ONLY when check_domain_availability reported status 'premium' or 'taken' (a curated Atom listing) for this exact domain, or get_domain_details confirmed it's a listing. If the domain is instead fresh/never-listed (status 'available'), use register_domain instead — never this tool; it will reject a fresh domain with error 'not_a_marketplace_listing'. MANDATORY two-step flow — never skip the quote: 1) Call with confirm=false (default) to get a QUOTE: returns the authoritative price, its breakdown (sale_price, registration_fee, vat_amount), the user's current balance, sufficient_funds, whether a saved card exists (has_saved_card / saved_card), and expires_at. 2) SHOW THE USER: the exact price breakdown, and state plainly which payment method you are about to use and how much it will charge — e.g. "$1,250.00 (listing price $1,200 + $50 registration fee) from your Atom balance" or "...from your saved Visa ending 4242". Get explicit confirmation before proceeding. 3) Call again with confirm=true, the SAME idempotency_key, and payment_method set to exactly 'balance' or 'saved_card' (REQUIRED at this step — never omit it or guess): commits the charge and the purchase. Returns status='purchased', amount_charged, payment_method, order_id, and order_url. Rules: never assume or pass a price. Reuse one client-generated idempotency_key across both calls (and any retry) to prevent double-charging. If payment_method='balance' and funds are insufficient, error 'insufficient_funds' reports required/available/top_up_url and whether a saved card exists as an alternative — tell the user both options plainly, do not silently retry with the other method. If payment_method='saved_card' and the charge fails, error 'card_payment_failed' reports why (including if it needs 3D Secure authentication, which cannot be completed here — offer balance or a different card instead). If it reports error 'registrant_contact_required' (a marketplace-domain transfer needs this to complete), ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry with confirm=true — this is expected and not a dead end.

    Annotations the server declares

    • title: Purchase a marketplace domain
    • destructiveHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • register_domainRegister a FRESH domain — an available domain that is NOT an existing Atom marketplace listing — directly at the registrar.Reads text others write1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description is 2,370 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...ion, which cannot be completed here — offer balance or a different card instead)."

      What this check looks for
    Description, as the server wrote it
    Register a FRESH domain — an available domain that is NOT an existing Atom marketplace listing — directly at the registrar. This SPENDS REAL MONEY and requires the 'domains:register' scope. Use this ONLY when check_domain_availability reported status 'available' for this exact domain. If the domain is instead an Atom marketplace listing (status 'premium'/'taken'), use purchase_domain instead — never this tool; it will reject a marketplace domain with error 'is_marketplace_listing'. MANDATORY two-step flow — never skip the quote: 1) Call with confirm=false (default) to get a QUOTE: returns the authoritative price, its breakdown (unit_price, icann_total, vat_amount), term_years (server-derived from the TLD — never assume or pass one), the user's current balance, sufficient_funds, whether a saved card exists (has_saved_card / saved_card), and expires_at. 2) SHOW THE USER: the exact price breakdown, and state plainly which payment method you are about to use and how much it will charge — e.g. "$19.98 (domain $17.99 + ICANN fee $1.99) from your Atom balance" or "...from your saved Visa ending 4242". Get explicit confirmation before proceeding. 3) Call again with confirm=true, the SAME idempotency_key, and payment_method set to exactly 'balance' or 'saved_card' (REQUIRED at this step — never omit it or guess): commits the charge and the registration. Returns status='registered', amount_charged, payment_method, and registrar_domain_id — the domain now shows up in the user's Atom account (dashboard → My Domains). Rules: never assume or pass a price. Reuse one client-generated idempotency_key across both calls (and any retry) to prevent double-charging. If it reports error 'registrant_contact_required' (a registry needs this to complete registration), call create_registrant_contact with the user's name, phone, address, city, zip, and country, then retry with confirm=true. If payment_method='balance' and funds are insufficient, error 'insufficient_funds' reports required/available/top_up_url and whether a saved card exists as an alternative — tell the user both options plainly, do not silently retry with the other method. If payment_method='saved_card' and the charge fails, error 'card_payment_failed' reports why (including if it needs 3D Secure authentication, which cannot be completed here — offer balance or a different card instead).

    Annotations the server declares

    • title: Register a fresh domain
    • destructiveHint: true
    • openWorldHint: true
    • readOnlyHint: false
  • register_domain_sptRegister a FRESH domain (an available domain that is NOT a curated Atom marketplace listing) by charging a Stripe Shared Payment Token (SPT) — for users with no Atom balance.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Register a FRESH domain (an available domain that is NOT a curated Atom marketplace listing) by charging a Stripe Shared Payment Token (SPT) — for users with no Atom balance. This SPENDS REAL MONEY and requires the 'domains:register' scope. For already-listed marketplace domains paid from an Atom balance, use register_domain instead. MANDATORY three-step flow — never skip a step: 1) Call with confirm=false to get a QUOTE: price and term_years, both entirely server-authoritative (term_years is derived from the TLD; there is no such input — never invent one). 2) Call again with confirm=true, the SAME idempotency_key, and NO payment_token: returns a structured payment_required challenge (amount, currency). 3) Once a Shared Payment Token is obtained for that exact amount, call a third time with confirm=true, the SAME idempotency_key, and payment_token set. Payment is captured FIRST; registration only starts after that succeeds. PAYMENT PRIORITY for a fresh registration: this tool is priority 1 — try it first, using whatever payment method your own platform can already supply for the payment_token (no external tool needed). Only if you have no way to obtain a payment_token here, fall back to priority 2: get_domain_register_pay_link, paid via link-cli's tools (e.g. mpp_pay), if those are present in this session. There is no checkout-link fallback for a fresh registration — get_checkout_link only works for an already-listed marketplace domain. Rules: never assume or pass a price or term_years. Reuse one idempotency_key across all calls for the same intent. If registration fails AFTER payment succeeds, the registrar submission itself attempts a real refund of the charge — the result reports whether that happened. If it reports error 'registrant_contact_required', ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry from step 1 — this is expected and not a dead end.

    Annotations the server declares

    • title: Register domain via Stripe SPT
    • destructiveHint: true
    • openWorldHint: true
    • readOnlyHint: false
Changes things 8Claude Code: ask
  • appraise_domainEstimate the market value of a domain and explain why.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Estimate the market value of a domain and explain why. Use when a user asks what a domain is worth, how much to pay/offer, or to appraise a domain. Returns two SEPARATE numbers — do not conflate them: • estimated_value — Atom's estimated market price in USD (an estimate, never a guaranteed or quoted price). • domain_score — a 0–10 rating of the NAME's quality/brandability/desirability (10 = strongest). This is a quality score, NOT a confidence level and NOT a probability. A low domain_score means a weaker/less desirable name, not that the estimate is uncertain. Also returns domain_score_label (weak/moderate/strong), factors (positive/negative signals behind the estimate), and comparable_sales. When presenting: state the estimated value as a price, describe domain_score as a quality rating (e.g. '6/10 — moderate brandability'), and NEVER describe domain_score as 'confidence'. Read the score_meaning field in the response.

    Annotations the server declares

    • title: Appraise a domain
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • brainstorm_namesCome up with name ideas for a startup, business, product, app, or project — every suggestion is a real, verified-buyable premium domain from Atom's curated marketplace, with its pr…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Come up with name ideas for a startup, business, product, app, or project — every suggestion is a real, verified-buyable premium domain from Atom's curated marketplace, with its price. ALWAYS use this (never invent names yourself) when the user asks to "come up with a name", "suggest names", "brainstorm names", "name my company", or any similar naming request: names invented without verification are almost always already taken. Describe the business as the concept; pass preferred extensions if the user stated any. Same results as search_brandable_domains — use either, not both. Returns results[] of buyable premium listings, each with: domain, price (USD), logo, style_tags, category, and url (the Atom buy page). Present them as the name suggestions, with prices and links.

    Annotations the server declares

    • title: Brainstorm business names
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • check_domain_availabilityCheck whether ONE specific, fully-spelled domain is available, taken, or a premium listing.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The description is 2,033 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...eate_registrant_contact with those, then retry register_domain with confirm=true."

      What this check looks for
    Description, as the server wrote it
    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 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. IMPORTANT — which tool to call next depends on status, and the top-level url means different things accordingly: status "available" (a fresh domain, NOT an Atom marketplace listing) → call register_domain to register it directly in this conversation; its url is a self-service registration page on Atom, only worth mentioning if the user prefers to do it themselves. Status "taken" or "premium" (an existing Atom marketplace listing) → call purchase_domain to buy it directly in this conversation; its url is the marketplace listing page. Never call register_domain for a "premium"/"taken" domain or purchase_domain for an "available" one — each rejects the wrong case with a clear error. Both tools quote a real price breakdown and ask you to state the payment method (Atom balance or saved card) before charging anything. If register_domain reports error registrant_contact_required, that's expected for a fresh domain and not a dead end: ask the user for their name, phone, address, city, zip, and country, call create_registrant_contact with those, then retry register_domain with confirm=true.

    Annotations the server declares

    • title: Check domain availability
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • create_registrant_contactCreate or update the authenticated user's registrant (WHOIS) contact — the name/address/phone/email a domain registry requires to complete a registration or marketplace-domain tran…Can send data outNo findings

    Why it is in this group

    • The name "create_registrant_contact" says "create": a word for a change.

    What it can reach

    • outboundThe input takes a destination (input.phone): what the tool writes goes there.
    Description, as the server wrote it
    Create or update the authenticated user's registrant (WHOIS) contact — the name/address/phone/email a domain registry requires to complete a registration or marketplace-domain transfer. Call this when a tool reports error 'registrant_contact_required'. All fields are required except state and organization (state only where applicable). This does NOT charge anything. If a contact already exists, this UPDATES it with the fields you pass — always send the full current set of fields, not just the ones that changed.

    Annotations the server declares

    • title: Create registrant contact
    • readOnlyHint: false
    • destructiveHint: false
    • openWorldHint: false
  • generate_domain_namesInvent NEW brandable domain name candidates for a concept, then ground each against live availability and Atom premium inventory — so every returned name is actually obtainable.1 finding

    Why it is in this group

    • The name "generate_domain_names" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_domain_names" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "generate_domain_names" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Invent NEW brandable domain name candidates for a concept, then ground each against live availability and Atom premium inventory — so every returned name is actually obtainable. Use when search_brandable_domains' curated results aren't enough, or the user explicitly wants fresh/invented/made-up names they can register. (For existing curated listings, prefer search_brandable_domains.) Returns results[], each with: domain (full name incl. extension), status ('available' = registrable now | 'premium' = an Atom listing), price + currency when known, style_tags, and url. Only names with availability/price attached are returned — never ungrounded ideas. Present as a list noting which are register-now vs Atom premium listings.

    Annotations the server declares

    • title: Generate domain names
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • screen_trademark_conflictsRun a PRELIMINARY screen for existing trademark conflicts on a brand or domain name against public USPTO records.1 finding

    Why it is in this group

    • The description's first verb is "run": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "screen_trademark_conflicts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

      What this check looks for
    Description, as the server wrote it
    Run a PRELIMINARY screen for existing trademark conflicts on a brand or domain name against public USPTO records. ALWAYS use this for ANY trademark question about a name — "any trademark issues?", "is this trademarked?", "is it safe to use as a brand?" — including follow-ups about a name discussed earlier in the conversation. Do NOT answer trademark questions from web search or memory; this tool queries the actual USPTO register. Returns preliminary exact/close matches with status and owner — this is a screen, not legal advice or a clearance opinion.

    Annotations the server declares

    • title: Screen trademark conflicts
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
Only reads 12Show 12 read-only tools
  • get_coinbase_payment_statusCheck a Coinbase (USDC) payment created by get_domain_purchase_coinbase_pay_link, get_domain_register_coinbase_pay_link or get_add_funds_coinbase_pay_link, and complete the purchas…No findings

    Why it is in this group

    • The name "get_coinbase_payment_status" says "get": a word for reading.
    Description, as the server wrote it
    Check a Coinbase (USDC) payment created by get_domain_purchase_coinbase_pay_link, get_domain_register_coinbase_pay_link or get_add_funds_coinbase_pay_link, and complete the purchase / registration / funds credit once it is paid. Each call waits up to ~10 seconds server-side and re-checks before answering, so it is safe to call back-to-back. POLLING: right after handing over the pay link (or after an x402 wallet pays it), keep calling this while status is 'pending' and stop_polling is false — no need to wait between calls. When stop_polling is true (about 15 minutes after the link was created), STOP polling and show the returned user_message to the user exactly as given (it is a highlighted warning). When the user later says they have paid, call this again. status is one of: 'pending' (not confirmed yet), 'completed' (domain purchased / funds credited — tell the user), 'failed' (checkout expired or failed, nothing captured — offer a new link), 'refunded' (paid, but the registry rejected the registration — the amount was credited to the Atom account balance), or 'needs_support' (paid but could not be applied automatically — give the user the message as-is).

    Annotations the server declares

    • title: Get Coinbase payment status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • destructiveHint: false
  • get_domain_detailsGet the full detail record for ONE specific Atom domain listing — the deep-dive after a user picks a name from search_brandable_domains or generate_domain_names, or asks to know mo…No findings

    Why it is in this group

    • The name "get_domain_details" says "get": a word for reading.
    Description, as the server wrote it
    Get the full detail record for ONE specific Atom domain listing — the deep-dive after a user picks a name from search_brandable_domains or generate_domain_names, or asks to know more about a particular domain. Returns: status, price + currency, extension_options[] (other TLDs of the name for sale, with prices), category, description, age/traffic when available, and purchase_url/details_url. If the domain is not an Atom listing, returns error "not_found" (then use check_domain_availability for registry status). Present price, key attributes, and the purchase link. IMPORTANT: when price_on_request is true, price is null on purpose — this listing's price is deliberately undisclosed (make-offer/price-on-request). Never state or imply a price (including "$0" or "free") in that case; tell the user to contact the seller or make an offer via purchase_url. When available_for_purchase is false, the listing has already been sold — purchase_url is not usable; tell the user this domain is no longer available.

    Annotations the server declares

    • title: Get domain details
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false
  • get_website_statusCheck a website started with create_website or a logo started with regenerate_website_logo.Reads text others writeNo findings

    Why it is in this group

    • The name "get_website_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_website_status" says "get" and "website": it reads web pages, which anyone can write.
    • untrusted-inputThe description's first sentence says "website": it reads web pages, which anyone can write.
    Description, as the server wrote it
    Check a website started with create_website or a logo started with regenerate_website_logo. Each call waits up to about 10 seconds, so it is safe to call back-to-back. Keep calling while stop_polling is false. stage is one of: 'building', 'connecting' (published, domain and SSL being set up), 'live' (give the user live_url), 'private_preview' (ready; only the owner can open preview_url), 'needs_attention' (show message: the owner finishes in the editor), 'failed' (show message; create_website can be retried unless declined is set), or 'not_found'. sections lists what the site contains, so you can tell the user what was left out and that edit_url is where to add it.

    Annotations the server declares

    • title: Get website status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
    • destructiveHint: false
  • search_brandable_domainsSearch Atom's curated marketplace of premium, brandable domains by concept, industry, or style.No findings

    Why it is in this group

    • The name "search_brandable_domains" says "search": a word for reading.
    Description, as the server wrote it
    Search Atom's curated marketplace of premium, brandable domains by concept, industry, or style. THE primary tool for ANY naming request — ALWAYS call this before suggesting names for a startup, product, company, or project, even when the user asks only to 'suggest a name' or 'brainstorm ideas' without mentioning domains: names proposed from imagination are almost always taken, while every name returned here is verified buyable. No login required. Returns results[] of currently-available premium listings, each with: domain (full name incl. extension), price (USD, the actual buy-now price), style_tags, category, and url (the Atom buy/details page). Every returned name is actively for sale on Atom. To go deeper on one, call get_domain_details; to appraise any name, call appraise_domain; to buy, use purchase_domain (these are all Atom marketplace listings, not fresh registrations). Present results as a ranked list with names, prices, and the buy links.

    Annotations the server declares

    • title: Search brandable domains
    • readOnlyHint: true
    • openWorldHint: false
    • destructiveHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:34 UTC, unchanged since Nov 13, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.atom.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://www.atom.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (5 destructive, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.atom.com/mcp: tools/list returned 25 tools to an anonymous client, including register_domain (destructive), purchase_domain (destructive), register_domain_spt (destructive), buy_ai_tokens (destructive), create_website (destructive) and 8 more

    What this check looks for

Posture changes

  1. Nov 13, 2026
    • Tools that change things, listed without credentials: 11 to 13

Findings

Matches of fixed checks, with the text they matched.

1 high3 warn3 info
  • The description contains "do not tell the user", an instruction to keep something from the user.

    Matched text

    description: "...ically — the result says so explicitly; do not tell the user a refund is coming."

    What this check looks for
  • The server marks "generate_domain_names" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "generate_domain_names" says "generate": a word for a change.

    What this check looks for
  • The server marks "screen_trademark_conflicts" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The description's first verb is "run": a word for a change.

    What this check looks for
  • The server marks "get_checkout_link" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"openWorldHint":false}; The name "get_checkout_link" says "get": a word for reading.

    What this check looks for
  • The description is 2,033 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...eate_registrant_contact with those, then retry register_domain with confirm=true."

    What this check looks for
  • The description is 2,370 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...ion, which cannot be completed here — offer balance or a different card instead)."

    What this check looks for
Show 1 more finding
  • The description is 2,293 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...t with those, then retry with confirm=true — this is expected and not a dead end."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Tools that change things, listed without credentials: 11 -> 13.View diff
    • Tools that change things, listed without credentials: 11 to 13
  2. Tools3 added.+3 addedView diff
  3. Tools22 changed.~22 changedView diff

Install

Pinned to version 2.0.7. Values in angle brackets are yours to fill in.

claude mcp add --transport http premium-domains https://mcp.atom.com/mcp
claude mcp add --transport http premium-domains https://mcp.atom.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__premium-domains__search_brandable_domains",
      "mcp__premium-domains__get_domain_details",
      "mcp__premium-domains__get_ai_tokens_pay_link",
      "mcp__premium-domains__get_domain_register_pay_link",
      "mcp__premium-domains__get_domain_purchase_pay_link",
      "mcp__premium-domains__get_domain_register_pay_link_guest",
      "mcp__premium-domains__get_domain_purchase_pay_link_guest",
      "mcp__premium-domains__get_domain_purchase_coinbase_pay_link",
      "mcp__premium-domains__get_add_funds_coinbase_pay_link",
      "mcp__premium-domains__get_domain_register_coinbase_pay_link",
      "mcp__premium-domains__get_coinbase_payment_status",
      "mcp__premium-domains__get_website_status"
    ],
    "ask": [
      "mcp__premium-domains__brainstorm_names",
      "mcp__premium-domains__check_domain_availability",
      "mcp__premium-domains__generate_domain_names",
      "mcp__premium-domains__appraise_domain",
      "mcp__premium-domains__screen_trademark_conflicts",
      "mcp__premium-domains__get_checkout_link",
      "mcp__premium-domains__create_registrant_contact",
      "mcp__premium-domains__regenerate_website_logo"
    ],
    "deny": [
      "mcp__premium-domains__register_domain",
      "mcp__premium-domains__purchase_domain",
      "mcp__premium-domains__register_domain_spt",
      "mcp__premium-domains__buy_ai_tokens",
      "mcp__premium-domains__create_website"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as premium-domains. Review it before you use it.

Capability tags behind 14 rules
  • mcp__premium-domains__get_checkout_link untrusted-input
  • mcp__premium-domains__register_domain untrusted-input
  • mcp__premium-domains__purchase_domain untrusted-input
  • mcp__premium-domains__register_domain_spt untrusted-input
  • mcp__premium-domains__buy_ai_tokens untrusted-input
  • mcp__premium-domains__get_ai_tokens_pay_link untrusted-input
  • mcp__premium-domains__get_domain_register_pay_link untrusted-input
  • mcp__premium-domains__get_domain_purchase_pay_link untrusted-input
  • mcp__premium-domains__get_domain_register_pay_link_guest untrusted-input
  • mcp__premium-domains__get_domain_purchase_pay_link_guest untrusted-input
  • mcp__premium-domains__create_registrant_contact outbound
  • mcp__premium-domains__create_website untrusted-input
  • mcp__premium-domains__get_website_status untrusted-input
  • mcp__premium-domains__regenerate_website_logo untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.atom/premium-domains/verify?hash=99d4cfa6cca9ccf9e44761af713d180e91c50f5cd29d08e0f0ca7b634e6c07b5" | jq -e '.changed == false'

Pinned hash 99d4cfa6cca9, from Nov 10, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.atom/premium-domains/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.atom/premium-domains
[![Anlyon Radar](https://radar.anlyon.com/badge/com.atom/premium-domains.svg)](https://radar.anlyon.com/servers/com.atom/premium-domains)

Source: MCP Registry · repository. Synced Oct 21, 2026, 17:51 UTC.

Atom.com — Premium Domains MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Atom.com — Premium Domains MCP server safe?

No scan can promise that. What its definitions show: 25 tools, 13 of which can change, send or delete something, and 7 findings (1 high) from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Atom.com — Premium Domains MCP server delete data?

Yes. 5 tools can delete, cancel or revoke something: register_domain, purchase_domain, register_domain_spt, buy_ai_tokens and create_website.

Can the Atom.com — Premium Domains MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Atom.com — Premium Domains MCP server have?

25 tools: 5 destructive, 8 write, 12 read. register_domain, purchase_domain, register_domain_spt, buy_ai_tokens, create_website, brainstorm_names, check_domain_availability, generate_domain_names and 17 more.

Does the Atom.com — Premium Domains MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Atom.com — Premium Domains MCP server send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): create_registrant_contact.

Has the Atom.com — Premium Domains MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.