MCP servers observed by Lowdown
net.fatstack/registry MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-10 to 2026-11-16) (Lowdown checks this server every 3 days); 15 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-10; no tool definition change in 2 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:net.fatstack/registry
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.fatstack/registry?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: 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?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
15 tools on 2026-11-16:
askzephy-quick-scan__google_news_feedaskzephy-quick-scan__sol_auditaskzephy-quick-scan__sol_quick_scancron-explain__cron_explaincsv-to-json__csv_to_jsonecho__echo_jsonfatstack__free_demohtml-to-markdown__html_to_markdownjson-schema-validate__json_schema_validatemarkdown-lint__markdown_lintregex-test__regex_testtext-language-detect__text_language_detectunit-convert__unit_converturl-metadata__url_metadatauuid-batch__uuid_batch
MCP Registry declaration
- Registry name:
net.fatstack/registry - Declared version: 1.0.0
- Status: active
- Declared hosts:
www.fatstack.net
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:net.fatstack/registry", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:net.fatstack/registry?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).