MCP servers observed by Lowdown
domains.unique/mcp-server MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 51 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-17 after 3 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:domains.unique/mcp-server
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:domains.unique/mcp-server?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 2 of 2 compared days.
- 2026-11-17: input or output schemas changed, descriptions changed, server version changed
- 2026-11-14: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 53 → 51
What tools does it list?
51 tools on 2026-11-17:
ud_get_agendaud_get_catalog_statsud_get_domain_dropsud_get_editionud_get_eventud_get_iana_registrarud_get_latest_editionud_get_market_auctionsud_get_market_salesud_get_market_sales_lengthsud_get_meta_enumsud_get_meta_providersud_get_nameud_get_name_auctionud_get_name_compsud_get_name_dnsud_get_name_registryud_get_tldud_get_tld_application_stringud_get_tld_statsud_get_trendud_get_venueud_get_word_endingsud_get_word_notabilityud_list_domain_hacksud_list_domainsud_list_eventsud_list_iana_registrarsud_list_market_auction_venuesud_list_market_auctions_sampleud_list_market_sales_endingsud_list_market_sales_moversud_list_market_sales_seriesud_list_meta_datasetsud_list_meta_trademark_classesud_list_price_changesud_list_price_trapsud_list_registrar_changesud_list_registrar_pricesud_list_registrarsud_list_tld_application_changesud_list_tld_applicationsud_list_tld_changesud_list_tld_keywordsud_list_tld_phasesud_list_tldsud_list_trend_categoriesud_list_trendsud_list_venuesud_list_word_categoriesud_resolve_word
MCP Registry declaration
- Registry name:
domains.unique/mcp-server - Declared version: 0.1.9
- Status: active
- Declared hosts:
mcp.unique.domains
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:domains.unique/mcp-server", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:domains.unique/mcp-server?menu=install-check
When running its declared package, wrap it with the stdio proxy. Since lowdown-proxy 0.1.22 the proxy adds this record (install-check) to the server's initialize response; it changes no tool result and blocks nothing:
npx -y lowdown-proxy --target mcp:domains.unique/mcp-server -- npx -y @uniquedomains/mcp-server
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).