Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.nameshift/marketplace

REMOTE · API.NAMESHIFT.COM

Search domains for sale on Nameshift, check pricing, and buy one via a hosted checkout link.

0 this week 24 Trust /100

Last scanned (8 hours ago)

Scores higher than 10% of remote servers

Reachable. Last reached 5 Nov 2026.

Category E-commerce

Trust breakdown (7 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 → Why this is hard to score →

Endpoint Security60
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

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.

  • 28 Sept 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
  • 25 Sept 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 Aug 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
  • 21 Aug 26 0
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 20 Aug 26 0

    First indexed and scored.

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 5 Nov 2026 · Probed https://api.nameshift.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.nameshift.com CN=YE2,O=Let's Encrypt,C=US 6 Oct 2026 4 Jan 2027 ECDSA 256 ECDSA-SHA384 5a4d041f38a942099fd1c8354ef665daf98
SANs: api.nameshift.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of api.nameshift.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
nameshift.com. present 37775 13 Verified
api.nameshift.com. Verified address RRset verified with the apex keys
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive
HTTP status 404

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.nameshift.com/mcp HTTP error 404
http (plaintext) http://api.nameshift.com/mcp HTTPS enforced 301 https://api.nameshift.com/mcp
MCP tools · 3 exposed · ~782 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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
buy_domain ~346

Creates a real purchase order for a domain with a buy-now price and returns a checkout URL where the buyer completes billing details and payment in a browser. Nothing is charged until the buyer pays there. Only the email is required; name, address and company details are optional and prefill the checkout page — pass only details the buyer explicitly provided or confirmed, never guessed ones. Always confirm the exact domain name, its price (see get_domain_details) and the buyer email address with the user before calling this tool.

NameTypeReqDescription
addressCitystring–City of the billing address.
addressCountryCodestring–ISO 3166-1 alpha-2 country code of the billing address, e.g. "NL". This drives tax calculation and available payment methods.
addressLine1string–First line of the billing address.
addressLine2string–Second line of the billing address.
addressPostalCodestring–Postal or ZIP code of the billing address.
addressStateCodestring–State or province code of the billing address, when applicable.
companyobject–Company billing details when the buyer purchases as a business. Omit entirely for private buyers.
domainNamestringyesFull domain name including the TLD, e.g. "example.com".
emailstringyesEmail address of the buyer. Order updates and the payment confirmation are sent here.
firstNamestring–Buyer first name.
lastNamestring–Buyer last name.
localestring–Locale for the checkout page and buyer emails, e.g. "en" or "nl-nl".

No output schema declared.

No examples provided.

get_domain_details ~85

Returns sale details for one domain listed on the Nameshift marketplace: pricing, availability and whether it can be bought instantly with buy_domain.

NameTypeReqDescription
domainNamestringyesFull domain name including the TLD, e.g. "example.com".
localestring–Locale used for the returned landing-page URL, e.g. "en" or "nl-nl".

No output schema declared.

No examples provided.

search_domains ~351

Searches domains listed for sale on the Nameshift marketplace. Returns a page of matching domains with pricing, plus pagination cursors and TLD facet counts on the first page.

NameTypeReqDescription
buyNowOnlyboolean–When true (default), only return domains with a buy-now price — the ones buy_domain can purchase.
cursorstring–Opaque pagination cursor from a previous response (nextCursor or previousCursor). Pass it back unchanged to fetch that page.
limitinteger–Results per page (max 25).
localestring–Locale used for the returned landing-page URLs, e.g. "en" or "nl-nl".
maxLengthinteger–Maximum domain name length, excluding the TLD.
maxPriceinteger–Maximum buy-now price in major currency units (each seller's own currency).
minPriceinteger–Minimum buy-now price in major currency units (each seller's own currency).
noDigitsboolean–Exclude domains containing digits.
noHyphensboolean–Exclude domains containing hyphens.
querystring–Free-text search over domain names and descriptions. A full domain name (e.g. "coffee.com") boosts exact matches.
semanticboolean–When true, also matches the query semantically against domain descriptions (e.g. "a name for a coffee brand"). Only useful together with query.
sortstring–Sort order. "relevance" uses the search score, or domain authority when no query is given.
tldsarray–Only include these TLDs, e.g. ["com", "io"].

No output schema declared.

No examples provided.

Install

How do I install the com.nameshift/marketplace MCP server?

com.nameshift/marketplace is a hosted endpoint at https://api.nameshift.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.nameshift.com

# add to Claude Code
claude mcp add --transport http com-nameshift-marketplace 'https://api.nameshift.com/mcp'
Common questions

What is the com.nameshift/marketplace MCP server?

com.nameshift/marketplace is an MCP server listed in the public MCP registry as com.nameshift/marketplace. Search domains for sale on Nameshift, check pricing, and buy one via a hosted checkout link. This page covers its hosted endpoint (https://api.nameshift.com/mcp).

Is the com.nameshift/marketplace MCP server safe to use?

com.nameshift/marketplace scores 24 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.nameshift/marketplace MCP server expose?

com.nameshift/marketplace exposes 3 tools: search_domains, get_domain_details, buy_domain. Their descriptions and schemas cost roughly 782 tokens of context every time the server is loaded.

Does the com.nameshift/marketplace MCP server require authentication?

Its publisher declares no required credentials for com.nameshift/marketplace. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the com.nameshift/marketplace MCP server still maintained?

com.nameshift/marketplace is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.