Atom — Premium Domains MCP Server

https://mcp.atom.com/mcp Remote v2.0.0

Published by mcp.atom.com — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Search, value, screen, and buy premium brandable domains from Atom's curated marketplace.

Trust grade
F
50/100
Last scanned get badge →
Trust
F · 50/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Live
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
F Why this grade threat 53 − adoption risk = 50/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 46.9 = 53. What the published surface and source actually contain:

PointsWhat was foundCategory
−31.5 Compound tool-poisoning pattern MTC-INJ-POISON injection
−15.4 Secrecy directive MTC-INJ-SECRECY-1 injection

2. Client adoption risk — 53 − 3 = 50. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Grade capped: a critical finding is present → grade capped at D. A hard gate overrides the point total — no amount of clean surface buys back a confirmed catastrophe.

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 2

critical Compound tool-poisoning patternMTC-INJ-POISON

Multiple tool-poisoning signals co-occur in a single field (authority, secrecy), including a concealment / override / sensitive-target directive. Together they form an instruction aimed at the model — the canonical tool-poisoning shape, not ordinary documentation.

Evidence: 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 thre

Fix: Do not install this server; the metadata is engineered to manipulate the assistant.

Location: tool buy_ai_tokens · description

high Secrecy directive (conceal action from the user)MTC-INJ-SECRECY-1

Secrecy directive (conceal action from the user) detected in the description of tool "buy_ai_tokens". Instruction-like content in tool metadata is executed by the model, not the human, and is the primary tool-poisoning vector.

Evidence: do not tell the user

Fix: Tool descriptions should describe behavior, not instruct the assistant. Treat imperative / secrecy / sequencing language in metadata as hostile.

Location: tool buy_ai_tokens · description

Tools 16

Each tool and what it can reach — enumerated from the running server.

  • screen_trademark_conflictsingests untrusted input
  • appraise_domainno sensitive capability
  • brainstorm_namesno sensitive capability
  • buy_ai_tokensno sensitive capability
  • check_domain_availabilityno sensitive capability
  • create_registrant_contactno sensitive capability
  • generate_domain_namesno sensitive capability
  • get_ai_tokens_pay_linkno sensitive capability
  • get_checkout_linkno sensitive capability
  • get_domain_detailsno sensitive capability
Show 6 more tools ↓
  • get_domain_purchase_pay_linkno sensitive capability
  • get_domain_register_pay_linkno sensitive capability
  • purchase_domainno sensitive capability
  • register_domainno sensitive capability
  • register_domain_sptno sensitive capability
  • search_brandable_domainsno sensitive capability

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v2.0.0 latest F 50/100 2 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: F · 50/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-atom-com/badge.svg)](https://mcptrustchecker.com/registry/mcp-atom-com)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-atom-com"><img src="https://mcptrustchecker.com/registry/mcp-atom-com/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-atom-com/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan https://mcp.atom.com/mcp --online

Use the free API → How scoring works

More in Web, Search & Scraping