MCP servers observed by Lowdown

app.usewrit/writ-cloud MCP server: daily status and tool changes

Answered initialize and tools/list on all 30 daily checks recorded in the last 30 days (2026-10-20 to 2026-11-18); 41 tools listed. MCP Registry declaration recorded; observed daily by Lowdown Scanner since 2026-10-19; tool definitions last changed on 2026-11-10 after 9 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.usewrit/writ-cloud

Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.usewrit/writ-cloud?menu=install-check · other questions: menu

Does it respond?

Latest daily check: 2026-11-18: the server answered initialize and tools/list.

Does it require authentication?

It did not return HTTP 401/403 on any of the 30 observed days. Lowdown checks without credentials.

Did its tools change recently?

Tool definitions changed on 6 of 30 compared days.

What tools does it list?

41 tools on 2026-11-18:

MCP Registry declaration

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.usewrit/writ-cloud", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:app.usewrit/writ-cloud?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:

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).