MCP servers observed by Lowdown
io.github.khaledmoayad/3ammiya MCP server: daily status and tool changes
No successful response on the last 2 consecutive checks (2026-11-14 to 2026-11-17) (Lowdown checks this server every 3 days). Checked from one network location. 2 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 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:io.github.khaledmoayad/3ammiya
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.khaledmoayad/3ammiya?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: 1
- Required authentication: 0
- No response: 2
- 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?
Fewer than two days with a complete tools/list observation from the same remote, so nothing was compared.
What tools does it list?
8 tools on 2026-11-11:
get_latest_wordsget_related_wordsget_trending_wordsget_word_of_daylist_regionslist_tagslookup_wordsearch_words
MCP Registry declaration
- Registry name:
io.github.khaledmoayad/3ammiya - Declared version: 1.0.0
- Status: active
- Declared hosts:
3ammiya.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:io.github.khaledmoayad/3ammiya", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.khaledmoayad/3ammiya?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).