MCP servers observed by Lowdown
app.naulon/naulon MCP server: daily status and tool changes
Answered initialize and tools/list on all 2 checks recorded in the last 30 days (2026-11-13 to 2026-11-16) (Lowdown checks this server every 3 days); 11 tools listed. On 2026-11-16 a tool description with a URL appeared. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-13; tool definitions last changed on 2026-11-16 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:app.naulon/naulon
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.naulon/naulon?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-16: the server answered initialize and tools/list.
- Observed days in the last 30: 2
- Answered initialize and tools/list: 2
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 2 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 1 compared days.
- 2026-11-16: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 8 → 11; a tool description with a URL appeared
What tools does it list?
11 tools on 2026-11-16:
naulon_appraisenaulon_check_answernaulon_check_citationsnaulon_check_claimnaulon_check_referencesnaulon_discovernaulon_lookupnaulon_quotenaulon_retrievenaulon_searchnaulon_trace_passage
MCP Registry declaration
- Registry name:
app.naulon/naulon - Declared version: 1.0.2
- Status: active
- Declared hosts:
gate.naulon.app
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:app.naulon/naulon", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.naulon/naulon?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:app.naulon/naulon -- npx -y @naulon/wayfarer-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).