MCP servers observed by Lowdown
com.tamingdns/mcp 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); 19 tools listed. On 2026-11-14 a tool description with a URL appeared. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; tool definitions last changed on 2026-11-14 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:com.tamingdns/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:com.tamingdns/mcp?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 1 of 2 compared days.
- 2026-11-17: server version changed
- 2026-11-14: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 13 → 19; a tool description with a URL appeared
What tools does it list?
19 tools on 2026-11-17:
analyze_dmarc_reportanalyze_email_headerscheck_bimicheck_danecheck_dkimcheck_dmarccheck_dns_propagationcheck_dnsseccheck_google_workspacecheck_m365check_mcp_keyscheck_mta_stscheck_mxcheck_spfcheck_tls_rptcheck_txtcheck_websitedecode_bouncediscover_dkim
MCP Registry declaration
- Registry name:
com.tamingdns/mcp - Declared version: 2.2.2
- Status: active
- Declared hosts:
tamingdns.com
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:com.tamingdns/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:com.tamingdns/mcp?menu=install-check
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).