Atom.com — Premium Domains

REMOTE · MCP.ATOM.COM · SCANNED AUG 3

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

Available components

+5 this week 68 68 Trust /100

Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →

Endpoint Security66

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability64

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 1461 tokens (~208/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass
Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.atom.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# ~/.codex/config.toml

[mcp_servers.com-atom-premium-domains]
url = "https://mcp.atom.com/mcp"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-atom-premium-domains": {
      "type": "remote",
      "url": "https://mcp.atom.com/mcp",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-atom-premium-domains --url https://mcp.atom.com/mcp --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-atom-premium-domains:
    url: "https://mcp.atom.com/mcp"

// mcp.json

{
  "mcpServers": {
    "com-atom-premium-domains": {
      "type": "http",
      "url": "https://mcp.atom.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 63

First indexed and scored.

Show 5 earlier entries Hide earlier entries

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Probed https://mcp.atom.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject	Issuer	Valid from	Valid until	Key	Signature	Serial
CN=mcp.atom.com	CN=YR1,O=Let's Encrypt,C=US	3 Jul 2026	1 Oct 2026	RSA 2048	SHA256-RSA	50ab85a9387484f49d5ae355bcf836152eb
SANs: mcp.atom.com
CN=YR1,O=Let's Encrypt,C=US (CA)	CN=Root YR,O=ISRG,C=US	3 Sept 2025	2 Sept 2028	RSA 2048	SHA256-RSA	a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA)	CN=ISRG Root X1,O=Internet Security Research Group,C=US	13 May 2026	2 Sept 2032	RSA 4096	SHA256-RSA	f24b6d17f9d9ad7cb1c9fea78782699f

DNSSEC secure

Validation of mcp.atom.com. — Secure

Zone	DS	Keys	Algorithms	Outcome
.	trust_anchor	20326, 38696	8, 8	Verified
com.	present	19718	13	Verified
atom.com.	present	2371	13	Verified
mcp.atom.com.				Verified address RRset verified with the apex keys

Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result	No authorisation required
HTTP status	200

Header	Value
strict-transport-security	max-age=63072000
x-content-type-options	nosniff

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://mcp.atom.com/mcp	Verified	200
http (plaintext)	http://mcp.atom.com/mcp	HTTPS enforced	308	https://mcp.atom.com/mcp

MCP tools — 7 exposed · ~1,461 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens

appraise_domain ~250

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	Full domain to appraise, including the extension, e.g. 'example.com'. Works for any domain, not just Atom listings.

Name	Type	Req	Description
comparable_sales	array	—	Recent comparable sales (best-effort; .com only).
currency	string	—	—
disclaimer	string	—	—
domain	string	yes	—
domain_score	number\|null	yes	0–10 quality rating of the NAME (NOT a confidence level).
domain_score_label	string	—	Human label for domain_score.
domain_score_max	integer	—	—
estimated_value	number\|null	yes	Atom's estimated market value in USD (an estimate, not a quote).
estimated_value_meaning	string	—	How to interpret estimated_value.
factors	array	—	Signals behind the estimate.
score_meaning	string	—	Explains domain_score is a quality rating, not confidence.
success	boolean	yes	—
url	string	yes	—

No examples provided.

check_domain_availability ~192

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. 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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	The domain to check, including extension, e.g. 'example.com'.

Name	Type	Req	Description
alternatives	array	—	Closest available Atom premium names when the domain is taken/premium.
currency	string	—	—
domain	string	yes	—
estimated_value	number	—	Rough appraisal in USD (optional).
price	number\|null	—	Price in USD when applicable.
registrable	boolean	yes	Whether the domain can be registered now.
status	string	yes	available = registrable now; taken = registered/unavailable; premium = for sale on Atom.
success	boolean	yes	—
url	string	yes	Atom URL for this domain.

No examples provided.

generate_domain_names ~220

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.

Input Output Examples

Name	Type	Req	Description
concept	string	yes	The idea, product, or business to generate names for.
count	integer	—	Number of candidates to return (capped server-side).
extensions	array	—	Optional preferred extensions.
industry	string	—	Optional industry or category.
style	array	—	Optional stylistic preferences.

Name	Type	Req	Description
concept	string	—	—
count	integer	—	Number of candidates returned.
results	array	yes	Invented candidates, each grounded against live availability/inventory.
success	boolean	yes	—
url	string	yes	Atom marketplace search URL for the concept.

No examples provided.

get_checkout_link ~162

Generate a pre-filled, authenticated Atom checkout URL for a chosen domain so the user can pay on Atom. Use when a user wants to BUY a domain but is not using balance registration, lacks sufficient balance, or prefers to pay per purchase (card/PayPal). This is the no-debit alternative to register_domain. IMPORTANT: this tool only returns a link — it does NOT charge anything or complete a purchase. Returns: domain, price + currency, checkout_url (give this to the user to finish payment), and expires_at. Present the price and the checkout link; tell the user payment completes on Atom.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	The domain to purchase, including extension.
term_years	integer	—	Registration term in years, where applicable.

Name	Type	Req	Description
checkout_url	string	yes	Pre-filled Atom checkout URL — give this to the user to pay.
currency	string	—	—
domain	string	yes	—
expires_at	string\|null	—	When the checkout link expires.
price	number\|null	—	Price in USD.
success	boolean	yes	—
url	string	yes	—

No examples provided.

get_domain_details ~144

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.

Input Output Examples

Name	Type	Req	Description
domain	string	yes	The domain to look up, including extension.

Name	Type	Req	Description
age	number\|string\|null	—	—
category	string\|null	—	—
currency	string	—	—
description	string\|null	—	—
details_url	string	—	Atom details page.
domain	string	yes	—
extension_options	array	—	Other TLDs of the name for sale, with prices.
price	number\|null	—	Listing price in USD.
purchase_url	string	—	Direct purchase link.
status	string\|null	—	—
success	boolean	yes	—
traffic	number\|string\|null	—	—
url	string	yes	—

No examples provided.

screen_trademark_conflicts ~204

Run a PRELIMINARY screen for existing trademark conflicts on a brand or domain name against public USPTO records. Use when a user asks whether a name is trademarked, already taken as a trademark, or safe to use as a brand. Returns preliminary exact/close matches with status and owner — this is a screen, not legal advice or a clearance opinion.

Input Output Examples

Name	Type	Req	Description
limit	integer	—	Max results (capped server-side).
mode	string	—	Match strictness. exact = identical mark; phrase = close; broad = widest.
name	string	yes	The brand or domain name to screen (extension is ignored, e.g. "acme" or "acme.com").
status	string	—	Filing status filter. active = live registered marks.
trademark_class	integer	—	Optional Nice/USPTO international class to filter by (1–45, e.g. 9 = software, 35 = business services).

Name	Type	Req	Description
count	integer	—	Number of matches returned.
disclaimer	string	yes	Preliminary screen, not legal advice.
matches	array	yes	Preliminary exact/close trademark matches from public USPTO records.
name	string	yes	The normalized name that was screened.
success	boolean	yes	—
total	integer	—	Total matching records upstream.
url	string	yes	—

No examples provided.

search_brandable_domains ~289

Search Atom's curated marketplace of premium, brandable domains by concept, industry, or style. THE primary tool for naming a startup, product, or company when the user wants real, buyable names (not just ideas). Use whenever a user asks for brandable/business/domain name suggestions for an idea, or wants names they can actually purchase. 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, register_domain or get_checkout_link. Present results as a ranked list with names, prices, and the buy links.

Input Output Examples

Name	Type	Req	Description
concept	string	yes	The idea, product, or business to find names for.
extensions	array	—	Optional preferred extensions, e.g. ['.com', '.io'].
industry	string	—	Optional industry or category, e.g. 'fintech', 'wellness'.
limit	integer	—	Number of results to return (capped server-side).
max_price	number	—	Optional maximum price filter (USD).
style	array	—	Optional stylistic preferences.

Name	Type	Req	Description
concept	string	—	The concept that was searched.
count	integer	—	Number of results returned.
results	array	yes	Currently-available premium listings, ranked.
success	boolean	yes	—
url	string	yes	Atom marketplace search URL for the concept.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	63
27 Jul	63
28 Jul	64
29 Jul	65
30 Jul	65
31 Jul	67
1 Aug	67
2 Aug	68
3 Aug	68