MCP servers observed by Lowdown
ai.aetherya/mcp MCP server: daily status and tool changes
No successful response on the latest check (2026-11-17) (Lowdown checks this server every 3 days). Checked from one network location. 1 of 3 checks in the last 30 days had this result. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 1 compared days; 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:ai.aetherya/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.aetherya/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server did not respond.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 2
- Required authentication: 0
- No response: 1
- 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?
No change in tool schemas, descriptions or names across 1 compared days.
What tools does it list?
27 tools on 2026-11-14:
aetherya_ask_audienceaetherya_audit_siteaetherya_cancelaetherya_compare_creativesaetherya_confirm_studyaetherya_create_audienceaetherya_create_intake_linkaetherya_estimateaetherya_get_audit_resultaetherya_get_briefaetherya_get_resultaetherya_list_audiencesaetherya_list_capabilitiesaetherya_list_intake_filesaetherya_list_runsaetherya_plan_studyaetherya_pretest_reportaetherya_pretest_videoaetherya_readaetherya_record_outcomeaetherya_run_studyaetherya_seal_predictionaetherya_share_resultaetherya_simulate_postaetherya_test_copyaetherya_test_flowaetherya_verify_prediction
MCP Registry declaration
- Registry name:
ai.aetherya/mcp - Declared version: 1.0.5
- Status: active
- Declared hosts:
mcp.aetherya.ai
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:ai.aetherya/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:ai.aetherya/mcp?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:ai.aetherya/mcp -- npx -y @aetherya/mcp
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).